DebuggingProcedures

Differences between revisions 102 and 109 (spanning 7 versions)
Revision 102 as of 2010-07-09 22:34:05
Size: 4433
Editor: pool-71-252-251-234
Comment:
Revision 109 as of 2011-03-30 19:05:17
Size: 4682
Editor: cs181003192
Comment: Add entry for DebuggingEmacs -- about to create this page
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
 * [[DebuggingFirefox|Firefox Web Browser]]  * [[Unity/FilingBugs|Unity]]
 * [[DebuggingAyatana|Ayatana project]]
 * [[DebuggingBanshee|Banshee]]
 * [[DebuggingEmacs|Emacs]]
Line 21: Line 24:
 * [[DebuggingFirefox|Firefox Web Browser]]
Line 27: Line 31:
 * [[DebuggingGwibber|Gwibber]]
Line 59: Line 64:
 * [[Bugs/KnownHardwareIssues/10.10|Known hardware specific issues on Maverick]]

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

If you want to add information on how to debug a package to this page, use this template.

As part of triaging bug reports about specific packages or subsystems, bug triagers and developers have been writing debugging procedures for them. These include information about how to troubleshoot issues, gather the proper log files and common bug reports. If you find one missing, and if no one else can help, e-mail the Bug Squad! You can find them at ubuntu-bugsquad@lists.ubuntu.com . Or in #ubuntu-bugs on irc.ubuntu.com .

Desktop Applications

Server Applications

Hardware

Storage devices

Kernel

Include: Nothing found for "== Debugging Scenarios ==$"!

Installation and Upgrades

Debugging Tools

Miscellaneous

Template

We've created a template file for debugging procedure pages if you want to write a new one. The template provides a similar look and feel for all pages and ensures that they cover common subjects.


CategoryBugSquad CategoryDebugging

DebuggingProcedures (last edited 2019-07-19 13:37:58 by till-kamppeter)