DebuggingProcedures

Differences between revisions 120 and 125 (spanning 5 versions)
Revision 120 as of 2015-09-27 21:54:49
Size: 4575
Editor: penalvch
Comment: Added libmtp article as I'm facing an mtp issue and couldn't find here.
Revision 125 as of 2019-07-19 13:37:58
Size: 4513
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
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 [email protected] . Or in #ubuntu-bugs on irc.ubuntu.com . 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 [[[email protected]]], or in #ubuntu-bugs on [[irc.ubuntu.com]].
Line 18: Line 18:
 * [[Unity/FilingBugs|Unity]]
Line 20: Line 19:
 * [[Chromium/Debugging|Chromium]]
Line 21: Line 21:
 * [[DebuggingEmpathy|Empathy]]
Line 22: Line 23:
 * [[DebuggingGNOME|GNOME applications - Applets, Banshee, Cheese, Evince, Evolution, Gconf, Network Manager, Power Manager, Screensaver (screen locking), System Tools]]  * [[DebuggingGnash|Gnash Flash plugin]]
 * [[DebuggingG
NOME|GNOME applications - Applets, Banshee, Cheese, Evince, Evolution, Gconf, Nautilus, Network Manager, Power Manager, Screensaver (screen locking), System Tools]]
Line 24: Line 26:
 * [[DebuggingJava|Java]]
Line 26: Line 29:
 * [[DebuggingGnash|Gnash Flash plugin]]
Line 28: Line 30:
 * [[DebuggingNetworkManager|Network Manager]]
Line 29: Line 32:
 * [[DebuggingJava|Java]]
 * [[DebuggingEmpathy|Empathy]]
Line 32: Line 33:
 * [[Chromium/Debugging|Chromium]]  * [[Unity/FilingBugs|Unity]]
Line 43: Line 44:
= Application Debugging Tools =

 * [[Backtrace]]
 * [[MemoryTest|Memory test]]
 * [[Strace]]
 * [[Valgrind]]
Line 45: Line 53:
 * [[DebuggingBluetooth|Bluetooth]]
Line 46: Line 55:
 * [[DebuggingUdev|Udev (device hotplugging)]]
 * [[DebuggingIRQProblems|IRQ problems]]
 * [[DebuggingACPI|ACPI (power-saving etc.)]]
 * [[DebuggingSoundProblems|Sound problems]]
 * [[DebuggingKeyboardDetection|Keyboard detection]]
 * [[DebuggingMouseDetection|Mouse detection]]
Line 51: Line 58:
 * [[DebuggingMouseDetection|Mouse detection]]
Line 54: Line 60:
 * [[DebuggingKeyboardDetection|Keyboard detection]]
 * [[https://wiki.ubuntu.com/Kernel/Debugging/USB|USB problems]]
 * [[DebuggingUdev|Udev (device hotplugging)]]
Line 57: Line 62:
= Storage devices = == Storage devices ==
Line 67: Line 72:
## please add any new debugging pages to the Kernel/Debugging page in the Debugging Scenarios section and they will appear here and all other appropriate places together.
<<Include(Kernel/Debugging, , from="== Debugging Scenarios ==$", to="==")>>
## please add any new debugging pages to the page https://wiki.ubuntu.com/Kernel/Debugging in the Debugging Scenarios section and they will appear here and all other appropriate places together.
<<Include(Kernel/Debugging, , from="== Introduction ==$", to="== Links ==$")>>
Line 72: Line 77:
 * [[DebuggingInstallationIssues|Installing and updating packages (General issues)]]
Line 75: Line 81:
 * [[DebuggingInstallationIssues|Installing and updating packages (General issues)]]

= Debugging Tools =

 * [[MemoryTest|Memory test]]
 * [[Backtrace]]
 * [[Strace]]
 * [[Valgrind]]
Line 99: Line 97:
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. 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.

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 to this page on how to debug a package, 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 [email protected], or in #ubuntu-bugs on irc.ubuntu.com.

Desktop Applications

Server Applications

Application Debugging Tools

Hardware

Storage devices

Kernel

To determine which guides are relevant to your problem see the symptom based debugging guide.

Kernel Debugging Scenarios

Kernel Debugging Guides

  • ACPI -- debugging ACPI (Advanced Configuration and Power Interface)

  • BIOS -- Debugging BIOS issues on Ubuntu (DSDT, Reboot, Suspend/Resume)

  • IRQ -- debugging interrupt related issues

  • Sound -- Basic troubleshooting tips for debugging sound problems

  • System Crash -- Tips for gather information regarding system crashes and lockups

Kernel Debugging Tools/Information

Installation and Upgrades

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)