On 12 Jun 2013 22:53, "Schaaf, Jonathan P (GE Healthcare)" < [email protected]> wrote: > > Hello everyone - have any of you seen this exit of FVWM? > > #0 0x0083d066 in exit (status=1) at exit.c:99 > #1 0x0808e768 in CatchFatal (dpy=0x8315740) at fvwm.c:1482 > #2 0x00b1f797 in _XIOError (dpy=0x8315740) at XlibInt.c:1618 > #3 0x00b1e055 in _XReply (dpy=0x8315740, rep=0xffa515f0, extra=0, discard=1) > at xcb_io.c:707 > #4 0x00b1982d in XSync (dpy=0x8315740, discard=0) at Sync.c:44 > #5 0x080ec3ef in MyXUngrabServer (disp=0x8315740) at Grab.c:51 > #6 0x0807062a in HandleMapNotify (ea=0xffa516e8) at events.c:2849 > #7 0x0806ca2c in dispatch_event (e=0xffa5172c) at events.c:4124 > #8 0x0806d208 in HandleEvents () at events.c:4168 > #9 0x08091c2b in main (argc=<value optimized out>, argv=0xffa520c4) > at fvwm.c:2591 > > I have a feeling this is actually an issue buried deep within libX11 or the X-server itself, but I thought I'd ask to see if anyone else had seen it.
Give more information about what you were doing, and how to reproduce the crash, etc. Thomas
