Bug 15144

Summary:	Some kind of menu format change is complicating preference-changing
Product:	[Retired] Red Hat Linux	Reporter:	Telsa Gwynne <hobbit>
Component:	WindowMaker	Assignee:	Crutcher Dunnavant <crutcher>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	hobbit
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:	2000-08-03 20:20:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Telsa Gwynne 2000-08-02 19:00:31 UTC

Spotted on a fresh install (ie no previous files messing things up)
of pinstripe. Was trying to change preferences for WindowMaker.
Used both WPrefs and wmakerconf.  I am not very familiar with
the internals of wmaker so I don't really understand this:

WPrefs says, for the menu configuration section:
"Warning: the menu that is being used now could not be opened"
The message continues about possible typos or unsupported formats.

wmakerconf says, 
"Application menu configuration requires that your menu
file /home/hobbit/GNUstep/Defaults/WMRootMenu is in the new format"

Because this is an install rather than an upgrade, I don't have an
old format. Both programs suggest ways to continue with different
options, but I have little idea which I should be using.

Comment 1 Crutcher Dunnavant 2000-08-03 18:43:22 UTC

Not a bug.
This is how WM works. It's default menu is not a libProplist menu,
and as such, cannot be parsed by WPrefs or wmakerconf.
And that is in all its documentation, as well as in WPrefs error message.

If you want to use WPrefs or wmakerconf to edit your menu, tell them that it is
okay to copy over the default plmenu.

Closing this.

Comment 2 Alan Cox 2000-08-03 18:52:34 UTC

So maybe we should ship it with a libproplist root menu, since that appears to
be how it work on
6.x. Save a lot of tech support calls in the process.

Comment 3 Crutcher Dunnavant 2000-08-03 20:20:54 UTC

I personally use Window Maker. It has always acted like this. the default menu
has some capabilities that do not exist in the libproplist menu. The error
dialog tells you this, tells you where to get more info, and asks you if you
want to use the libproplist menu anyway.

It never worked differently from this.
So the question is, do we get a lot of support calls NOW about this?

Comment 4 Crutcher Dunnavant 2000-08-03 21:00:35 UTC

Okay,
I went and asked support about this issue.
Crash said that they NEVER get asked about Window Maker,
or about this, and since it has always acted this way,
this is a non-issue (and shipping the other menu as the default
would remove some functionality)

I am closing this bug.

Comment 5 Crutcher Dunnavant 2000-08-07 01:44:49 UTC

*** Bug 15419 has been marked as a duplicate of this bug. ***