Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

BadWindow (invalid Window parameter)

Tzvika Faibish
Occasional Advisor

BadWindow (invalid Window parameter)

Hi Guys,
Once a day I get stuck with my CDE windows on my HP-UX 11. on my ".dt" directory I get error file which display this:

ly2005:tzvika {~/.dt} > more errorlog
*** STDERR(1): (/usr/dt/bin/dtexec) /usr/dt/bin/dtstyle: PID 7661: Tue Dec 30 15
:18:34 2003
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 20 (X_GetProperty)
Resource id in failed request: 0x1400010
Serial number of failed request: 81
Current serial number in output stream: 81

*** [340]

Do you know what to do in order to fix this stuck/crach windows?
4 REPLIES
Jim Butler
Valued Contributor

Re: BadWindow (invalid Window parameter)

Rick Beldin
Esteemed Contributor

Re: BadWindow (invalid Window parameter)

The interpretation of this is that dtexec (used to launch apps from the front panel in CDE) reported the error from the program dtstyle.
The error dtstyle reports is that the window ID (a unique id for each X window on the screen) is invalid. This is generally a programming problem but can be caused by some misconfiguration.

What kind of X display device are you using? I could conceive that this might happen with some X configurations, especially PC Xservers that CDE does not know how to handle.

dtstyle is known to work with 8 and 24 bit visuals since that is what HP workstations have delivered. PC Xservers (and Linux) can support depth 16 visuals and I'm not sure that CDE knows how to work well in this environment.

A couple of questions:

- can you duplicate the problem or is this a one time occurrence? how do you duplicate the problem?

- can you supply the output of /usr/contrib/bin/X11/xdpyinfo?

Thanks and Happy New Year...
Necessary questions: Why? What? How? When?
Tzvika Faibish_1
Occasional Contributor

Re: BadWindow (invalid Window parameter)

Rick,
Thanks for your help. Iwant to mention that I'm working with "reflection" (emulator to Unix) and also several users work with the same configuration but don't have this problem.
Here is the for output "/usr/contrib/bin/X11/xdpyinfo":

name of display: 199.203.63.57:0.0
version number: 11.0
vendor string: WRQ, Inc.
vendor release number: 8
maximum request size: 4194300 bytes
motion buffer size: 0
bitmap unit, bit order, padding: 32, MSBFirst, 32
image byte order: MSBFirst
number of supported pixmap formats: 3
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
keycode range: minimum 9, maximum 254
focus: window 0x4c0000e, revert to PointerRoot
number of extensions: 17
BIG-REQUESTS
DEC-XTRAP
Extended-Visual-Information
GLX
LBX
MIT-SUNDRY-NONSTANDARD
Multi-Buffering
SECURITY
SGI-GLX
SHAPE
SYNC
TOG-CUP
WRQ-ADMIN
WRQ_XPrint
XIE
XInputExtension
XTEST
default screen number: 0
number of screens: 1

screen #0:
dimensions: 1272x950 pixels (335x250 millimeters)
resolution: 96x97 dots per inch
depths (3): 1, 24, 8
root window id: 0x28
depth of root window: 24 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x24
default number of colormap cells: 256
preallocated pixels: black 0, white 16777215
options: backing-store YES, save-unders YES
largest cursor: 32x32
current input event mask: 0x70003c
ButtonPressMask ButtonReleaseMask EnterWindowMask
LeaveWindowMask SubstructureRedirectMask FocusChangeMask
PropertyChangeMask
number of visuals: 4
default visual id: 0x20
visual:
visual id: 0x20
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff, 0xff00, 0xff0000
significant bits in color specification: 8 bits
visual:
visual id: 0x21
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff, 0xff00, 0xff0000
significant bits in color specification: 8 bits
visual:
visual id: 0x21
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff, 0xff00, 0xff0000
significant bits in color specification: 8 bits
visual:
visual id: 0x22
class: PseudoColor
depth: 8 planes
available colormap entries: 256
red, green, blue masks: 0x0, 0x0, 0x0
significant bits in color specification: 8 bits
visual:
visual id: 0x23
class: PseudoColor
depth: 8 planes
available colormap entries: 256
red, green, blue masks: 0x0, 0x0, 0x0
significant bits in color specification: 8 bits


Thanks,
Tzvika
Rick Beldin
Esteemed Contributor

Re: BadWindow (invalid Window parameter)

Reflections/X has an interesting feature that might make things difficult for CDE. It has a feature that you can enable that can let you
run in 'rootless' mode, where the X windows are intermixed with the MicroSoft windows. While this is quite useful from a user standpoint, it is quite different from a 'normal' Xserver/workstation environment. X programs expect to be able to write to the 'root' window of the screen. In rootless mode, they can't.
dtstyle expects to read and write attributes to the root window to change the background and so on and in rootless mode you can't do this.

Suggestions:

- enable 'windowed' mode in the Reflections/X options menu

- check the security settings - I have a feeling that security settings in Reflections/X may cause some problems.

Necessary questions: Why? What? How? When?