[SOLVED] I can't run X window without network connectivity...

Yaakov Ben-Avraham · 05-20-2013, 01:52 PM

I can't run X window without network connectivity in Slackware 14.0
Previous versions allowed me to run X window without the internet being up and running. Is this by design? Is there a work-around to allow me to run X without requiring internet connectivity?

ButterflyMelissa · 05-20-2013, 02:04 PM

Who claims that it is X that needs Internet? Could it be something that needs X, that needs the Internet? I'd sniff tru the applications that run in your X session and check which ones need the Internet.

By the way, is there a profound reason NOT to connect to the Net? Security can be enforced by other means...

Just thinking-n-typing out loud...

Thor

Didier Spaier · 05-20-2013, 02:05 PM

Assuming you start Slackware at run level 3, what happens when you type "startx"?

Please at least attach /var/log/Xorg.0.log to your next post, otherwise it will be very difficult to diagnose your problem.

As far as I know there is no relation between an internet connection and X.

ButterflyMelissa · 05-20-2013, 02:20 PM

Quote:

As far as I know there is no relation between an internet connection and X

(hence my own confusion"...)

Yaakov Ben-Avraham · 05-20-2013, 03:58 PM

Quote:

Originally Posted by Didier Spaier

Assuming you start Slackware at run level 3, what happens when you type "startx"?

Please at least attach /var/log/X0.log to your next post, otherwise it will be very difficult to diagnose your problem.

As far as I know there is no relation between an internet connection and X.

The command "startx" will not run unless the Internet is connected.
The file /var/log/x0.log is not created if "startx" is typed
and the internet is not connected. Slackware 14.0 just
hangs the console until ^C is typed if this is tried.

BroX · 05-20-2013, 04:08 PM

Quote:

Originally Posted by Yaakov Ben-Avraham

The file /var/log/x0.log is not created if "startx" is typed

Just in case: log file is /var/log/Xorg.0.log without typo

ttk · 05-20-2013, 04:14 PM

I ran into a similar problem a while back, and it was because I had DISPLAY=localhost:0 set in my environment. Changing this to DISPLAY=:0 fixed it. I don't know if that's your problem, but perhaps you could check.

Yaakov Ben-Avraham · 05-20-2013, 04:57 PM

Quote:

Originally Posted by ttk

I ran into a similar problem a while back, and it was because I had DISPLAY=localhost:0 set in my environment. Changing this to DISPLAY=:0 fixed it. I don't know if that's your problem, but perhaps you could check.

I can find no references to Display or Localhost in my environment table.

mrclisdue · 05-20-2013, 05:29 PM

Which wm are you running? Is there anything in your .xinitrc that may yield any clues?

cheers,

TommyC7 · 05-20-2013, 05:31 PM

Are you booting into runlevel 3 or runlevel 4?

Also, how is the connection being made? rc.inet1, NetworkManager or wicd?

gsl · 05-20-2013, 05:38 PM

Does startx hang forever or does X start eventually (after 10+ seconds)? If you run 'hostname -f' does it take a while to complete while plain 'hostname' completes immediately? That was the cause of the problem for me when I found X would not start promptly when the network was down. I just edited /usr/bin/startx to replace 'hostname -f' with 'hostname'.

Geoff.

Yaakov Ben-Avraham · 05-20-2013, 06:13 PM

Quote:

Originally Posted by gsl

Does startx hang forever or does X start eventually (after 10+ seconds)? If you run 'hostname -f' does it take a while to complete while plain 'hostname' completes immediately? That was the cause of the problem for me when I found X would not start promptly when the network was down. I just edited /usr/bin/startx to replace 'hostname -f' with 'hostname'.

Geoff.

That was indeed the work-around. Remove the -f from `hostname -f` in startx

This begs the question "Why does `hostname -f` complete instantly in Slackware 13.37 and hang for so long in Slackware 14.0?"

gsl · 05-20-2013, 07:20 PM

Quote:

Originally Posted by Yaakov Ben-Avraham

This begs the question "Why does `hostname -f` complete instantly in Slackware 13.37 and hang for so long in Slackware 14.0?"

This news thread suggests it might be because hostname on 14.0 supports IPv6 whereas 13.37 and before doesn't? As my /etc/hosts doesn't have an IPv6 entry for localhost, hostname was doing a DNS lookup.

Geoff.