After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546290 - Sessions Preferences help is inaccurate and incomplete
Sessions Preferences help is inaccurate and incomplete
Status: RESOLVED DUPLICATE of bug 502018
Product: gnome-user-docs
Classification: Core
Component: user-guide
2.14.x
Other Linux
: Normal minor
: ---
Assigned To: Maintainers of Gnome user documentation
Maintainers of Gnome user documentation
Depends on:
Blocks:
 
 
Reported: 2008-08-04 17:59 UTC by Charles
Modified: 2009-02-12 04:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Charles 2008-08-04 17:59:00 UTC
1. The help variously refers to "session preferences" and "sessions preference" instead of the dialog 's title "sessions preferences".

2. Table 8.20 describes "Show splash screen on login", "Prompt on logout", "Automatically save changes to session" and "Sessions" but the dialog box displays "Automatically remember current applications when logging out" and "Remember Currently Running Applications".

3. There is no advice on how to undo "Remember Currently Running Applications".

4. Table 8.21 describes Order, Style, Remove and Apply but the dialog box also displays State.  There is no description (or picture) of the icons used in the State column and their significance.

5. Section 8.5.2.3. variously refers to applications and to programs.  The dialog itself only shows programs.

6. Table 8.22, in the first bullet point refers to a Priority spin box.  There is no priority spin box on the pertinent tab of the dialog.
Comment 1 Charles 2008-08-04 18:02:45 UTC
This may not apply in Gnome 2.23.  See Vincent Untz's comment at http://bugzilla.gnome.org/show_bug.cgi?id=351086#c4
Comment 2 Matthias Clasen 2009-02-12 04:09:59 UTC
This is fixed in the patch attached to bug 502018

*** This bug has been marked as a duplicate of 502018 ***