Comment 50 for bug 914161

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

That means that a config file change between 3.1.0-2.3 and 3.2.0-1.1 caused this bug.

When the bug happens, do you get any output on the screen? It would be very helpful if we could capture a trace or a screen shot of the panic.