Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 90913 - workspace switcher loses info when logging out
workspace switcher loses info when logging out
Status: CLOSED DUPLICATE of bug 76406
Product: Red Hat Linux
Classification: Retired
Component: gnome-panel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Depends On:
  Show dependency treegraph
Reported: 2003-05-15 05:42 EDT by Joachim Backes
Modified: 2007-04-18 12:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:53:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joachim Backes 2003-05-15 05:42:54 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Changing the workspace names in the workspace switcher and then logging produces
lost workspace names, that means when logging in again, the workspace names in
the workspace switcher are reset to 'Workspace 1' aso.
But somewhere seems some info to be kept, because in a windows menu (upper left
corner) I can use "Move to <workspace>" with the lost workspace names. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Change a workspace name in the workspace switcher
2. Log out
3. Log in

Actual Results:  Workspace names are reset

Expected Results:  Workspace names are kept

Additional info:

I dont use gdm, but log in by using startx from a console.
Comment 1 phostetl 2003-07-08 11:18:41 EDT
This bug is a duplicate of 76406.
Comment 2 Havoc Pennington 2003-08-07 16:35:20 EDT

*** This bug has been marked as a duplicate of 76406 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:53:02 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.