| Summary: | afterstep config changes not saved | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | deivu |
| Component: | AfterStep | Assignee: | Cristian Gafton <gafton> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1998-12-14 18:21:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
deivu
1998-12-14 07:33:19 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. 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. |