Changes between Version 11 and Version 12 of ReportingBugs


Ignore:
Timestamp:
Jul 20, 2016, 3:57:38 PM (8 years ago)
Author:
humdinger
Comment:

Added "save-report" command to "Server Bugs"

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v11 v12  
    2525
    2626When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen. Save for everything being more ugly and inconvenient basically the same applies as for [#ApplicationBugs application bugs]. Most importantly procure a back trace (`bt` command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.
     27Depending on what exactly crashed, you can try to save a crash report on the Desktop with `save-report` and then press the power button once to try shutting cleanly down. If that worked, you should find the crash report on the Desktop after the next boot-up.
    2728
    2829 == Kernel Bugs ==