Re: gdm killed by mozilla
On Sat, 29 Dec 2001 00:56:55 +0100, Thomas Deselaers <thomas@deselaers.de> wrote:
> On Fri, Dec 28, 2001 at 02:15:24PM -0800, Eric G. Miller wrote:
> > On Fri, 28 Dec 2001 21:12:15 +0100, Thomas Deselaers <thomas@deselaers.de> wrote:
> >
> > > Hello,
> > > I have a strange problem, for which today I figured out how to repeat.
> > >
> > > Logging in over gdm into gnome-session and then starting mozilla and going
> > > to a site which requires a login (e.g. www.sms.de) kills X and gives me a
> > > new gdm login. Same happens with netscape, too.
> > >
> > > Can anyone tell me how I can stop this strange behaving?
> >
> > No idea. But, check the X logs which may be more informative.
> > /var/log/XFree86.?.log, ~/.xsession-errors
>
> Though they are not very interesting I think I attached one. I am not sure
> if this amount of module-loading/-unloading is really fine.
It's typical...
> > Note, check ~/.xsession-errors via a console login after this happens
> > (it is overwritten at the start of a new X session).
>
> There is no ~/.xession-errors or anything like this.
Hmm, no help there... ;-(
> > By chance, using direct rendering and/or any third party video card
> > drivers? Maybe a connection? Using Java?
>
> direct rendering: yes, 3rd party video-card drivers: yes, the nvidia thing
> using java: no
>
> Well but I cannot see a connection there because I have absolutely no
> problems if I do not login over gdm.
> Another thing where I experience problems at the moment is font-aa and
> truetype fonts, but I get the same results with AA disabled.
Well, I dunno...?
> > Also, try launching mozilla from the command line and directing its
> > output to a file (it may give a clue)...
>
> mozilla > out.txt 2>&1
> results in an empty file out.txt, thus no clue at all
Guess mozilla doesn't have debugging output turned on anymore, it used
to spit out a bunch of info to stdout/stderr...
> Thanks for your advice,
> any other ideas?
Not really. The only thing I've found that consistently kills my X sessions,
is some aspect of DPMS via X. I turn off X's idea of DPMS and all is well.
I don't see the connection between logging into a website via a browser and
a local X login. The only noteworthy thing in the X log, is that very last
line about the rejected X connection... But it's not clear where it comes
from...
--
Eric G. Miller <egm2@jps.net>
Reply to: