Re: DISPLAY troubles...

2007-06-18 Thread Gary Kline
On Sun, Jun 17, 2007 at 09:56:33PM -0700, Gary Kline wrote:
 On Mon, Jun 18, 2007 at 12:45:59AM -0400, Joe Marcus Clarke wrote:
  Gary Kline wrote:
 This is a strange one.  Last time I ran my broswer it worked.  
 Also, I *finally* had Gnome auto-booting.  Just now, terminal
 fails to come up ; likewise with firefox.  I rebooted twice but
 don't see anything unusual.
   
 I'm rerunning portupgrade -a for the umpteent time.  If anybody
 knows why the DISPLAY fails, I'd like a clue.  env shows the
 display as :0.0, but nothing works.
  
  You can try ktracing the simplest non-working X application from the
  command line.  See if anything obvious shows up.
  
 
 
   I can even get X working.  Not kdm, not gdm, not even xdm.
   I'll check the /tmp/.X11* file
 
   gary
 
   PS:  I'm upgrading ports right this sec, but ought to be ble to 
   go in thru F3 or the like.
 
 
FWIW: lots more of things likee theses in /var/log/debug.log:

Jun  5 00:04:39 tao2 su: NSSWITCH(nss_method_lookup): nis, group_compat,
endgrent, not found

But  in /etc/make.conf is NO_NIS=YES; so I don't no where the nis
yelps are coming from  any ideas??  Also, lot of -aP packages
cming over via portupgrade.  

Also I /usr is

X11R6 - /usr/local/

It's gone from working to (!working) and back. And back... . HM.
this is interesting, aabout kdm-bin in messages and gdm also:

Jun 17 21:45:27 tao2 syslogd: exiting on signal 15
Jun 17 21:45:53 tao2 syslogd: kernel boot file is /boot/kernel/kernel
Jun 17 21:45:55 tao2 rpcbind: cannot create socket for udp6
Jun 17 21:45:55 tao2 root: /etc/rc: WARNING: /etc/ntp.conf is not
readable.
Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: can't create server SMTP socket: Protocol
not supported
Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: optional socket disabled
Jun 17 21:46:11 tao2 login: ROOT LOGIN (root) ON ttyv0
Jun 17 21:46:18 tao2 kdm-bin[21947]: X server for display :0 terminated
unexpectedly
Jun 17 21:46:18 tao2 kdm-bin[21947]: Unable to fire up local display :0;
disabling.
Jun 17 21:58:30 tao2 login: ROOT LOGIN (root) ON ttyv2
Jun 17 22:02:28 tao2 gdm[22133]: Failed to start X server several times
in a short time period; disabling display :0
Jun 17 22:10:53 tao2 kdm-bin[24594]: X server for display :0 terminated
unexpectedly
Jun 17 22:10:53 tao2 kdm-bin[24594]: Unable to fire up local display :0;
disabling.
Jun 17 22:43:34 tao2 kdm-bin[90030]: X server for display :0 terminated
unexpectedly
Jun 17 22:43:34 tao2 kdm-bin[90030]: Unable to fire up local display :0;
disabling.


Any X11/GUI type wizards know what this means?  This is exactly 
what happened when I trried to lanuch GGUI stuff: couldn't deal
with the display.   I'm stumped.



gary



-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: DISPLAY troubles...

2007-06-18 Thread Sam Fourman Jr.

fuck off

On 6/18/07, Gary Kline [EMAIL PROTECTED] wrote:


On Sun, Jun 17, 2007 at 09:56:33PM -0700, Gary Kline wrote:
 On Mon, Jun 18, 2007 at 12:45:59AM -0400, Joe Marcus Clarke wrote:
  Gary Kline wrote:
 This is a strange one.  Last time I ran my broswer it worked.
 Also, I *finally* had Gnome auto-booting.  Just now, terminal
 fails to come up ; likewise with firefox.  I rebooted twice but
 don't see anything unusual.
  
 I'm rerunning portupgrade -a for the umpteent time.  If anybody
 knows why the DISPLAY fails, I'd like a clue.  env shows the
 display as :0.0, but nothing works.
 
  You can try ktracing the simplest non-working X application from the
  command line.  See if anything obvious shows up.
 


   I can even get X working.  Not kdm, not gdm, not even xdm.
   I'll check the /tmp/.X11* file

   gary

   PS:  I'm upgrading ports right this sec, but ought to be ble to
   go in thru F3 or the like.


FWIW: lots more of things likee theses in /var/log/debug.log:

Jun  5 00:04:39 tao2 su: NSSWITCH(nss_method_lookup): nis, group_compat,
endgrent, not found

But  in /etc/make.conf is NO_NIS=YES; so I don't no where the nis
yelps are coming from  any ideas??  Also, lot of -aP packages
cming over via portupgrade.

Also I /usr is

X11R6 - /usr/local/

It's gone from working to (!working) and back. And back... . HM.
this is interesting, aabout kdm-bin in messages and gdm also:

Jun 17 21:45:27 tao2 syslogd: exiting on signal 15
Jun 17 21:45:53 tao2 syslogd: kernel boot file is /boot/kernel/kernel
Jun 17 21:45:55 tao2 rpcbind: cannot create socket for udp6
Jun 17 21:45:55 tao2 root: /etc/rc: WARNING: /etc/ntp.conf is not
readable.
Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: can't create server SMTP socket: Protocol
not supported
Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: optional socket disabled
Jun 17 21:46:11 tao2 login: ROOT LOGIN (root) ON ttyv0
Jun 17 21:46:18 tao2 kdm-bin[21947]: X server for display :0 terminated
unexpectedly
Jun 17 21:46:18 tao2 kdm-bin[21947]: Unable to fire up local display :0;
disabling.
Jun 17 21:58:30 tao2 login: ROOT LOGIN (root) ON ttyv2
Jun 17 22:02:28 tao2 gdm[22133]: Failed to start X server several times
in a short time period; disabling display :0
Jun 17 22:10:53 tao2 kdm-bin[24594]: X server for display :0 terminated
unexpectedly
Jun 17 22:10:53 tao2 kdm-bin[24594]: Unable to fire up local display :0;
disabling.
Jun 17 22:43:34 tao2 kdm-bin[90030]: X server for display :0 terminated
unexpectedly
Jun 17 22:43:34 tao2 kdm-bin[90030]: Unable to fire up local display :0;
disabling.


Any X11/GUI type wizards know what this means?  This is exactly
what happened when I trried to lanuch GGUI stuff: couldn't deal
with the display.   I'm stumped.



gary



--
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: DISPLAY troubles...

2007-06-18 Thread Norberto Meijome
[removing cross posting to -gnome@ ]

On Sun, 17 Jun 2007 23:05:34 -0700
Gary Kline [EMAIL PROTECTED] wrote:

 On Sun, Jun 17, 2007 at 09:56:33PM -0700, Gary Kline wrote:
  On Mon, Jun 18, 2007 at 12:45:59AM -0400, Joe Marcus Clarke wrote:
   Gary Kline wrote:
This is a strange one.  Last time I ran my broswer it worked.  
Also, I *finally* had Gnome auto-booting.  Just now, terminal
fails to come up ; likewise with firefox.  I rebooted twice but
don't see anything unusual.

I'm rerunning portupgrade -a for the umpteent time.  If anybody
knows why the DISPLAY fails, I'd like a clue.  env shows the
display as :0.0, but nothing works.
   
   You can try ktracing the simplest non-working X application from the
   command line.  See if anything obvious shows up.
   
  
  
  I can even get X working.  Not kdm, not gdm, not even xdm.
  I'll check the /tmp/.X11* file
  
  gary
  
  PS:  I'm upgrading ports right this sec, but ought to be ble to 
  go in thru F3 or the like.
  
  
   FWIW: lots more of things likee theses in /var/log/debug.log:
 
 Jun  5 00:04:39 tao2 su: NSSWITCH(nss_method_lookup): nis, group_compat,
 endgrent, not found
 
   But  in /etc/make.conf is NO_NIS=YES; so I don't no where the nis
   yelps are coming from  any ideas??  Also, lot of -aP packages
   cming over via portupgrade.  
 
   Also I /usr is
 
   X11R6 - /usr/local/
 
   It's gone from working to (!working) and back. And back... . HM.
   this is interesting, aabout kdm-bin in messages and gdm also:
 
 Jun 17 21:45:27 tao2 syslogd: exiting on signal 15
 Jun 17 21:45:53 tao2 syslogd: kernel boot file is /boot/kernel/kernel
 Jun 17 21:45:55 tao2 rpcbind: cannot create socket for udp6
 Jun 17 21:45:55 tao2 root: /etc/rc: WARNING: /etc/ntp.conf is not
 readable.
 Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
 opendaemonsocket: daemon IPv6: can't create server SMTP socket: Protocol
 not supported
 Jun 17 21:45:56 tao2 sm-mta[21870]: NOQUEUE: SYSERR(root):
 opendaemonsocket: daemon IPv6: optional socket disabled
 Jun 17 21:46:11 tao2 login: ROOT LOGIN (root) ON ttyv0
 Jun 17 21:46:18 tao2 kdm-bin[21947]: X server for display :0 terminated
 unexpectedly
 Jun 17 21:46:18 tao2 kdm-bin[21947]: Unable to fire up local display :0;
 disabling.
 Jun 17 21:58:30 tao2 login: ROOT LOGIN (root) ON ttyv2
 Jun 17 22:02:28 tao2 gdm[22133]: Failed to start X server several times
 in a short time period; disabling display :0
 Jun 17 22:10:53 tao2 kdm-bin[24594]: X server for display :0 terminated
 unexpectedly
 Jun 17 22:10:53 tao2 kdm-bin[24594]: Unable to fire up local display :0;
 disabling.
 Jun 17 22:43:34 tao2 kdm-bin[90030]: X server for display :0 terminated
 unexpectedly
 Jun 17 22:43:34 tao2 kdm-bin[90030]: Unable to fire up local display :0;
 disabling.


It seems it's an issue with X, not necessarily with your login manager. 

- Check what X logged in  /var/log/Xorg.0.log - PLEASE dont paste the lot in 
here blindly - errors / problems are usually clearly marked. Send those here 
for help.

- Disable all login managers (gdm,etc), then start X by itself (startx) - it 
may start gnome, or maybe twm. if it doesn't, it would most definitely point to 

- did you upgrade to Xorg 7.2 recently? did you follow the upgrade process to a 
successful completion? 

B


_
{Beto|Norberto|Numard} Meijome

He can compress the most words into the smallest idea of any man I know.
  Abraham Lincoln

I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
Reading disclaimers makes you go blind. Writing them is worse. You have been 
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: DISPLAY troubles...

2007-06-18 Thread Gary Kline
On Mon, Jun 18, 2007 at 09:25:07PM +1000, Norberto Meijome wrote:
 [removing cross posting to -gnome@ ]
 
 On Sun, 17 Jun 2007 23:05:34 -0700
 Gary Kline [EMAIL PROTECTED] wrote:
 
  On Sun, Jun 17, 2007 at 09:56:33PM -0700, Gary Kline wrote:
   On Mon, Jun 18, 2007 at 12:45:59AM -0400, Joe Marcus Clarke wrote:
Gary Kline wrote:
   This is a strange one.  Last time I ran my broswer it worked.  
   Also, I *finally* had Gnome auto-booting.  Just now, terminal
   fails to come up ; likewise with firefox.  I rebooted twice but
   don't see anything unusual.
 
   I'm rerunning portupgrade -a for the umpteent time.  If anybody
   knows why the DISPLAY fails, I'd like a clue.  env shows the
   display as :0.0, but nothing works.

You can try ktracing the simplest non-working X application from the
command line.  See if anything obvious shows up.

   
   
 I can even get X working.  Not kdm, not gdm, not even xdm.
 I'll check the /tmp/.X11* file
   
 gary
   
 PS:  I'm upgrading ports right this sec, but ought to be ble to 
 go in thru F3 or the like.
   
   
  FWIW: lots more of things likee theses in /var/log/debug.log:
  
  Jun  5 00:04:39 tao2 su: NSSWITCH(nss_method_lookup): nis, group_compat,
  endgrent, not found
  
  But  in /etc/make.conf is NO_NIS=YES; so I don't no where the nis
  yelps are coming from  any ideas??  Also, lot of -aP packages
  cming over via portupgrade.  
  
  Also I /usr is
  
  X11R6 - /usr/local/
  
  It's gone from working to (!working) and back. And back... . HM.
  this is interesting, aabout kdm-bin in messages and gdm also:
  
  Jun 17 22:43:34 tao2 kdm-bin[90030]: X server for display :0 terminated
  unexpectedly
  Jun 17 22:43:34 tao2 kdm-bin[90030]: Unable to fire up local display :0;
  disabling.
 
 
 It seems it's an issue with X, not necessarily with your login manager. 
 
 - Check what X logged in  /var/log/Xorg.0.log - PLEASE dont paste the lot in 
 here blindly - errors / problems are usually clearly marked. Send those here 
 for help.
 
 - Disable all login managers (gdm,etc), then start X by itself (startx) - it 
 may start gnome, or maybe twm. if it doesn't, it would most definitely point 
 to 
 
 - did you upgrade to Xorg 7.2 recently? did you follow the upgrade process to 
 a successful completion? 
 

Yes, this was an X/xorg issue.  There were logs in /var/log/gdm 
that pointed to /etc/X11/xorg.conf; but the errors weren't
traceable.  I created a new /root/xorg.conf.new and launched X.
(twm) There was a substantially longer list of stderrs from
X -configure.  I'm still tracing these.

 B
 
 
 _
 {Beto|Norberto|Numard} Meijome
 
 He can compress the most words into the smallest idea of any man I know.
   Abraham Lincoln
 
 I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
 Reading disclaimers makes you go blind. Writing them is worse. You have been 
 Warned.

-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


DISPLAY troubles...

2007-06-17 Thread Gary Kline
This is a strange one.  Last time I ran my broswer it worked.  
Also, I *finally* had Gnome auto-booting.  Just now, terminal
fails to come up ; likewise with firefox.  I rebooted twice but
don't see anything unusual.

I'm rerunning portupgrade -a for the umpteent time.  If anybody
knows why the DISPLAY fails, I'd like a clue.  env shows the
display as :0.0, but nothing works.

gary

-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: DISPLAY troubles...

2007-06-17 Thread Gary Kline
On Mon, Jun 18, 2007 at 12:45:59AM -0400, Joe Marcus Clarke wrote:
 Gary Kline wrote:
  This is a strange one.  Last time I ran my broswer it worked.  
  Also, I *finally* had Gnome auto-booting.  Just now, terminal
  fails to come up ; likewise with firefox.  I rebooted twice but
  don't see anything unusual.
  
  I'm rerunning portupgrade -a for the umpteent time.  If anybody
  knows why the DISPLAY fails, I'd like a clue.  env shows the
  display as :0.0, but nothing works.
 
 You can try ktracing the simplest non-working X application from the
 command line.  See if anything obvious shows up.
 


I can even get X working.  Noy kdm, not gdm, not even xdm.
I'll check the /tmp/.X11* file

gary

PS:  I'm upgrading ports right this sec, but ought to be ble to 
go in thru F3 or the like.



 Joe
 
 -- 
 Joe Marcus Clarke
 FreeBSD GNOME Team::  [EMAIL PROTECTED]
 FreeNode / #freebsd-gnome
 http://www.FreeBSD.org/gnome

-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: DISPLAY troubles...

2007-06-17 Thread Joe Marcus Clarke
Gary Kline wrote:
   This is a strange one.  Last time I ran my broswer it worked.  
   Also, I *finally* had Gnome auto-booting.  Just now, terminal
   fails to come up ; likewise with firefox.  I rebooted twice but
   don't see anything unusual.
 
   I'm rerunning portupgrade -a for the umpteent time.  If anybody
   knows why the DISPLAY fails, I'd like a clue.  env shows the
   display as :0.0, but nothing works.

You can try ktracing the simplest non-working X application from the
command line.  See if anything obvious shows up.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team  ::  [EMAIL PROTECTED]
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]