Bug 2005
Summary: | no fvwm2 with xosview | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | rsciurba |
Component: | fvwm2 | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | ||
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: | 1999-06-21 15:11:51 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
rsciurba
1999-04-05 19:10:55 UTC
what do you mean 'does not get attached'. Please be more descriptive. 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. 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. |