Bug 2005 – no fvwm2 with xosview

Bug 2005 - no fvwm2 with xosview

Summary:	no fvwm2 with xosview

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	fvwm2 (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-04-05 15:10 EDT by rsciurba
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-06-21 11:11:51 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description rsciurba 1999-04-05 15:10:55 EDT

When running the default fvwm2 (version 2.0.46 with options
SHAPE XPM and M4), the xosview utility does not get attached
to the fvwm2.

Comment 1 Preston Brown 1999-04-06 12:21:59 EDT

what do you mean 'does not get attached'.  Please be more descriptive.

Comment 2 rsciurba 1999-04-07 14:07:59 EDT

xosview does not run with the fvwm2 attached to the xosview process.
Cannot manipulate window (resize, move, etc...).

To reproduce:

1)  startx using the fvwm2
2)  Insert cdrom disk 1 in cdrom drive;
3)  run glint; install the xosview utility
4)  run xosview. xosview does not run with the fvwm2.  cannot
manipulate xosview window.  can only kill the process at the command
line.

Comment 3 Preston Brown 1999-06-21 11:11:59 EDT

AnotherLevel (our default fvwm2 setup) makes xosview have no border or
window.  You need to select "move window" from the "window operations"
menu in order to move windows like xeyes or xosview.  This is a
feature, not a bug.

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