Comment # 15 on bug 1094763 from Yifan Jiang

(In reply to Michal Srb from comment #14)
> (In reply to robert Horn from comment #10)
> > The problem looks like it begins with Windowmaker. It starts at 10:15:53. 
> > The first visible symptom was at 10:16:02 when firefox startup failed.  It
> > brought up the profile manager selection list, then with a couple seconds
> > that window vanished.
> 
> The log shows that Window Maker crashed (segfault). Then GDM terminates the
> X server and then all applications go down with IO error.
> 
> This is expected behavior and it is also what I was able to simulate on my
> test machine by killing wmaker manually.
> 
> I do not understand how you were able to see a new window for couple of
> seconds after that. Perhaps the high CPU utilization caused delay between
> the wmaker crash and the X server termination. However in comment 3 you said
> that only individual applications are killed, not the whole X server. I
> don't know how to explain that.
> 
> Nevertheless, whatever is happening, it seems to be triggered by crash in
> Window Manager. We should try to fix that. Can you check if you have any
> wmaker coredump recorded in the output of `coredumpctl`? If yes, please
> export it using `coredumpctl dump <pid>` command and attach it to bugzilla.

Hi Michal,

A couple of seconds before wmaker crashed, it looks firefox complains something
I couldn't understand. Can that be linked to you analysis as well? Thank you!

May 29 10:07:09 quad firefox[3492]: firefox: Fatal IO error 11 (Resource
temporarily unavailable) on X server :1.0.
May 29 10:07:28 quad firefox[3546]: firefox: Fatal IO error 11 (Resource
temporarily unavailable) on X server :1.0.