51287 – fvwm can't get list of xlock modes

Bug 51287 - fvwm can't get list of xlock modes

Summary: fvwm can't get list of xlock modes

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Tavis Ormandy (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-05-17 07:25 UTC by Honza
Modified:	2004-05-24 04:42 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Honza 2004-05-17 07:25:52 UTC

fvwm (x11-wm/fvwm-2.5.8-r6) can't get list of xlock (x11-misc/xlockmore-5.11.1) modes.
In fvwm-menu-xlock (perl script), it tried to run 'xlock -h' to get list of modes.
But xlock -h normally lock Xserver.

Corect behaviour have 'xlock -help'.


Reproducible: Always
Steps to Reproduce:
1. emerge xlockmore
2. emerge fvwm
3. fvwm-menu-xlock -n MenuSSaver -t "Screensaver" -icon-item mini.bball.xpm -- -nice 19 -nolock (this line is from default fvwm config files)

Actual Results:  
X server is locked with random screensaver.

Expected Results:  
Print part of configuration for including to config files.

Also, instead of -nolock, line should say +nolock.
(I repeat - that line is from default fvwm config files).

Of course, I don't know if there is any other xlock with different behaviour.

Comment 1 Tavis Ormandy (RETIRED) gentoo-dev

2004-05-24 04:42:08 UTC

Thanks Honza, I've committed a patch included with fvwm-2.5.10-r3 (which I'll mark stable this week).

Thanks for the good bug report.