DebuggingScreenLocking
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Contents |
** This is a work in progress **
Introduction
Bugs relating to screen locking issues typically fall into 4 categories:
- Screensaver failing to start after the inactivity period times out
- Screensaver failing to start when triggered manually
- No password prompt after resuming from suspend/hibernation
- Screensaver not hiding desktop and applications properly
How to file
Screen locking is a complex combination of many different packages, applications, and tools. For detailed information on how screen locking works, see DebuggingScreenLocking/HowScreenLockingWorks.
Important information
- What desktop environment does this problem occur in? (GNOME, XFCE, KDE, etc.)
- Do you use visual effects? (System/Preferences/Appearance/Visual Effects)
- Is this a laptop or a desktop machine?
- How many monitors do you use?
- If it is a laptop, do you use an external screen?
Getting GConf values
The following command will dump all the screen-locking relevant settings that are stored in GConf:
$ gconftool-2 --dump /apps/gnome-screensaver /desktop/gnome/session /desktop/gnome/lockdown > screen-locking-debug.xml
Debugging procedure
to be completed
How to Triage
to be completed
Stock Reply
to be completed
How to Forward
In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker. Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.
Known bugs
Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'.
Open
Bug |
Subject |
Symptom |
The subject from LP |
This bug can be identified by ... |
Closed
Bug |
Subject |
Symptom |
The subject from LP |
This bug can be identified by ... |
Non-bugs
How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.