Re: gdm killed by mozilla
On Sat, 29 Dec 2001 01:21:30 +0100, Thomas Deselaers <thomas@deselaers.de> wrote:
> On Sat, Dec 29, 2001 at 12:56:55AM +0100, Thomas Deselaers wrote:
>
> I think I found something important about this problem.
>
> It is the /var/log/gdm/:0.log of a crashed session.
>
> But it is 29kiB large, thus I won't put it onto this mailing list.
>
> It is available as http://www.deselaers.de/gdmlog
>
> Here just the last few lines:
>
> (II) Unloading /usr/X11R6/lib/modules/codeconv/libGB2312.a
> (II) Loading /usr/X11R6/lib/modules/codeconv/libGBK.a
> (II) Module GBK: vendor="X-TrueType Server Project"
> compiled for 4.1.0.1, module version = 1.3.0
> (II) Unloading /usr/X11R6/lib/modules/codeconv/libGBK.a
> (II) Loading /usr/X11R6/lib/modules/codeconv/libGEORGIAN.a
> (II) Module GEORGIAN: vendor="X-TrueType Server Project"
> compiled for 4.1.0.1, module version = 1.3.0
> (II) Unloading /usr/X11R6/lib/modules/codeconv/libGEORGIAN.a
>
> Fatal server error:
> Caught signal 11. Server aborting
>
>
> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages.
> This can be found in the log file "/var/log/XFree86.0.log".
> Please report problems to submit@bugs.debian.org.
>
> What does this error mean to me?
Well, something caused a segment violation in X. I'm a little
baffled by all of the repeated loading/unloading of code conversion
modules (seems suspect). But, since you're using a third-party
driver, I'd suggest making sure you have the latest version compatible
with your X server and check any errata that might be listed.
I still don't see the connection from mozilla to GDM. Once GDM hands
off control to the X session startup, it shouldn't be doing anything
until that process exits.
--
Eric G. Miller <egm2@jps.net>
Reply to: