[dapper] x-windows broken again

[Frank McCormick]

On Fri, 27 Jan 2006 10:21:05 +1100
James Gray <james at grayonline.id.au> wrote:

> On Fri, 27 Jan 2006 03:14, fmccormick at videotron.ca wrote:
> > Sorry but this stupid web interface my ISP provides is brain-dead! Have
> > to top post.I already have that symlink in place from the last time X
> > broke. This time it was after a GDM and Kernel update...as I said no
> > error messages...just a cli. 
> 
> If there was a kernel update, are you using ATi or nVidia's binary drivers?  
> If so you may need to recompile the kernel module associated with them.  I 
> had this problem recently in Breezy on my ATi lappy AND my AMD64 nVidia 
> desktop machine.
> 
> Kinda throws you when you go off to make a coffee, come back and instead of 
> the login screen, you've got a command line :P
> 
> BTW - unless X is *really* broken, you should have /something/ logged 
> to /var/log/Xorg.log.0.  If not, try creating a extra entry (with sudo) 
> in /etc/syslog.conf to log EVERYTHING (warning - this will generate a LOT 
> of info):
> 
> # Log *everything* - for debugging weird errors
> *.*                             /var/log/everything.log
> 
> then, "sudo /etc/init.d/sysklogd restart".
> 
> Now try and restart GDM: "sudo /etc/init.d/gdm restart".  If it doesn't come 
> up, you should get something useful in /var/log/everything.log and 
> possibly /var/log/Xorg.log.0.  You may even get some messages dumped to the 
> console too.
> 
> After the debugging is finished, you might want to change that syslog.conf 
> line to this instead:
> 
> # Log *everything* to tty12
> *.*                             /dev/tty12
> 
> ...now if you want a screenful of the most recent messages, "CTL+ALT+F12" 
> and voila!  Handy for a lot things :)  (ALT+F7 to get back to X, or 
> ALT+F[1-6] for the terminal sessions)
> 
   
   Tried it...but got nothing which might solve the problem. Just
a bunch of Pam error messages...and the X keeps crashing script
being run. It also doesn't provide anything..except a blank screen
Here's the log:

Jan 26 19:57:44 localhost syslogd 1.4.1#17ubuntu4: restart.
Jan 26 19:58:08 localhost sudo:    frank : TTY=tty1 ;
PWD=/home/frank ;USER=root ; COMMAND=/etc/init.d/gdm restart 
Jan 26
19:58:08 localhostsudo: PAM unable to dlopen
(/lib/security/pam_foreground.so) Jan 26 19:58:08 localhost sudo: PAM
[dlerror: /lib/security/pam_foreground.so: cannot open shared object
file: No such file or directory] Jan 26 19:58:08 localhost sudo: PAM
addng faulty module: /lib/security/pam_foreground.so Jan 26 19:58:08
localhost gdm[4288]: PAM unable to dlopen
(/lib/security/pam_foreground.so) Jan 26 19:58:08 localhost gdm[4288]:
PAM [dlerror: /lib/security/pam_foreground.so: cannot open shared object
file: No such file or directory] 
Jan 26 19:58:08 localhost gdm[4288]:
PAM adding faulty module: /lib/security/pam_foreground.so 
Jan 26
19:58:48 localhost gdm[4290]: deal_with_x_crashes: Running
theXKeepsCrashing script 
Jan 26 19:58:55 localhost gdm[4290]: Failed to
start X server several times in a short time period; disabling
display :0 
Jan 26 20:03:55 localhost sudo:    frank : TTY=tty1 ;
PWD=/home/frank ; USER=root ; COMMAND=/sbin/reboot Jan 26 20:03:55
localhost sudo: PAM unable to dlopen(/lib/security/pam_foreground.so)
Jan 26 20:03:55 localhost sudo: PAM
[dlerror: /lib/security/pam_foreground.so: cannot open shared object
file: No such file or directory] Jan 26 20:03:55 localhost sudo: PAM
adding faulty module: /lib/security/pam_foreground.so Jan 26 20:03:55
localhost shutdown[4391]: shutting down for system reboot Jan 26
20:03:55 localhost init: Switching to runlevel: 6 Jan 26 20:03:58
localhost postfix/master[3976]: terminating on signal 15 Jan 26
20:04:01 localhost kernel: Kernel logging (proc) stopped. Jan 26
20:04:01 localhost kernel: Kernel log daemon terminating. Jan 26
20:04:02 localhost exiting on signal 15



-- 


Frank McCormick
   Montreal