Introduction

TBD.

Debugging procedure

In Ubuntu we have disabled the feature that makes applications crash on critical warnings. To debug problems it's sometimes good to have this happening.

This will make it crash:

G_DEBUG=fatal_criticals <program>

If you additionally run the program under gdb or valgrind, it will help you to figure out, what led to the critical warning.

This will make a program stop on warnings:

<program> --g-fatal-warnings

There's also a useful information on how to run your program under gdb at the DebuggingProgramCrash page

Debugging Menus

If you should ever have to debug GNOME menus, you might want to use this

MENU_VERBOSE=1 <program>

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Non-bugs

TBD.

Also see:

• [http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines Some useful information from the GNOME team]

• [http://www.gnome.org/projects/evolution/bugs.shtml More info on evolution]

• DebuggingProcedures

• DebuggingGconf

• [https://wiki.ubuntu.com/DebuggingGNOMEApplets DebuggingGNOMEApplets]

• [https://wiki.ubuntu.com/DebuggingGNOMEPowerManager DebuggingGNOMEPowerManager]

CategoryBugSquad CategoryDesktopTeam CategoryDebugging