DebuggingProcedures

Note: If you wish to report a bug, see ReportingBugs and if you wish to help with bugs, see HelpingWithBugs

Some common procedures for debugging problems, which deserve to be documented once, and properly, rather than hastily repeated again and again in the process of handling bug reports:

• [:Bugs/FindRightPackage:Find the Right Package]

• Installation problems: DebuggingUbiquity

• ["DebuggingACPI"]

• DebuggingFirefox

• DebuggingHardwareDetection

• ["DebuggingIRQProblems"]

• KernelTeamBugPolicies

• DebuggingKernelSuspend

• DebuggingNonEnglishErrors

• DebuggingPrintingProblems

• DebuggingProgramCrash

• DebuggingRemovableDevices

• DebuggingSoundProblems

• DebuggingSystemCrash

• DebuggingTelepathy

• ["DebuggingUSBStorage"]
• ["DebuggingXAutoconfiguration"]

• MemoryTest

• ["Backtrace"]

• DebuggingMemoryLeaks

• ["Strace"]
• ["Valgrind"]

• [:LaptopTestingTeam/HotkeyResearch:Debugging Nonworking Hotkeys]

• DebuggingGnash

• [:DebuggingGNOME]

  • DebuggingGconf

  • [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]

CategoryBugSquad