Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 407 - afterstep config changes not saved
Summary: afterstep config changes not saved
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: AfterStep
Version: 5.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1998-12-14 07:33 UTC by deivu
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1998-12-14 18:21:39 UTC
Embargoed:

Attachments (Terms of Use)

Description deivu 1998-12-14 07:33:19 UTC 
Any changes I make to the ~/GNUstep/Library/Afterstep/start/
hierarchy are erased the next time I start X.
Comment 1 David Lawrence 1998-12-14 17:46:59 UTC 
I have verified this to be a problem. If you make the changes to the
start directory and then startx, the changes are removed and it starts
with a default setup. If you make the changes to the start directory
from an xterm and then just choose 'restart session' the changes are
left intact and the menu behaves properly.
Comment 2 Cristian Gafton 1998-12-14 18:21:59 UTC 
That is because of the wmconfig processing that will take palce in
that directory. The start dir is created/controlled by wmconfig
entirely.

In the 5.2 this problem was fixed by having the ability to create a
"fixed" dir on the same level with the start dir that will include
changes to the menu structure.
Note You need to log in before you can comment on or make changes to this bug.