Bug 748237

Summary:	pekwm not configured with harbour or menu options
Product:	[Fedora] Fedora	Reporter:	Ranjan Maitra <itsme_410>
Component:	pekwm	Assignee:	Germán Racca <gracca>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	gracca
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-04 02:28:38 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 Ranjan Maitra 2011-10-23 14:05:07 UTC

Description of problem:

It appears that pekwm is not configured with harbour or menu options.


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

0.13.1

How reproducible:

always

Steps to Reproduce:
1. % pekwm --info
2. there is no no harbour or menu feature in the list
3.
  
Actual results:

pekwm --info
pekwm: version 0.1.13 Built on Fri Aug 12 01:35:30 UTC 2011
features:  XShape Xinerama Xft image-xpm image-jpeg image-png Xrandr

Expected results:

The list should also include Harbour and Menu.

Additional info:

./configure --enable-harbour --enable-menu should fix this problem.


(Note that harbour is supposed to be enabled by default as per 
http://www.pekwm.org/files/pekwm/doc/0.1.10/html/overview/compiling.html#overview-compiling-configure

Many thanks for looking into this!

Comment 1 Germán Racca 2012-01-20 17:45:37 UTC

I'm compiling the new version, 0.1.14, and the configure options for menu and harbour are unrecognized. Please try to run the new version and then let me know what happens. If those options are not present, I'm going to contact upstream.

Comment 2 Ranjan Maitra 2012-03-04 02:28:28 UTC

It turns out that the documentation is not up to date (I asked the pekwm developers). Harbour and menus are now enabled by default and can not be disabled. So this bug is meaningless and should be closed. Thanks, though for looking into it!