Various X errors (difficult to see)

2008-03-21 Thread Luca Presotto
Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is correctly loaded etc.. My system starts without X and then I use startx to start X

Re: Various X errors (difficult to see)

2008-03-21 Thread Giorgos Keramidas
On Fri, 21 Mar 2008 15:18:45 +0100, Luca Presotto [EMAIL PROTECTED] wrote: Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is

Re: Various X errors (difficult to see)

2008-03-21 Thread Derek Ragona
At 09:18 AM 3/21/2008, Luca Presotto wrote: Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is correctly loaded etc.. My system

RE: Various X errors (difficult to see)

2008-03-21 Thread Luca Presotto
You should run startx and redirect the output to a file and check the errors and then try to fix them. To do this try: startx /tmp/somexerrorlogfile 21 Done that! Here-s the first error(s): DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal.

RE: Various X errors (difficult to see)

2008-03-21 Thread Derek Ragona
At 11:14 AM 3/21/2008, Luca Presotto wrote: You should run startx and redirect the output to a file and check the errors and then try to fix them. To do this try: startx /tmp/somexerrorlogfile 21 Done that! Here-s the first error(s): DCOPClient::attachInternal. Attach failed Could not open

R: Various X errors (difficult to see)

2008-03-21 Thread Luca Presotto
Is it something wrong in /etc/hosts?? It could be your /etc/hosts or /etc/hosts.allow or you may need to add:  -listen_tcp to your startx commandline. I supposed the problem was there! I'll look at -listen_tcp and at hosts.allow. I have doubts about setting hosts. X used to give me errors about

RE: Various X errors (difficult to see)

2008-03-21 Thread Luca Presotto
This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: ps -ax|grep -i art and see if the artsd daemon is running or not. If it is not, you may need to force it to start. I'll try that later! If I do ps

RE: Various X errors (difficult to see)

2008-03-21 Thread Derek Ragona
At 01:07 PM 3/21/2008, Luca Presotto wrote: This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: ps -ax|grep -i art and see if the artsd daemon is running or not. If it is not, you may need to force it