More various ximtool 2.0beta reports
Jason Quinn wrote on Dec 22, 2008
Clicking and then unclicking (right after starting ximtool) the V or H buttons for vertical or horizontal plots results in problems.
Most seriously, I can get crashes by simply clicking and unclicking H or V. The crash is reproducible but the number of clicks is usually between 7 and 11 and is not a set number. I've been doing it immediately after starting up ximtool without any image displayed. The crash gives the following error:
In addition, upon unclicking H or V, there's frequently a bunch of terminal output.
On a different note, two less severe things... I usually use ximtool or ds9 maximized on a second monitor. I frequently display an image but then need the toolbars "T" and "C". Often upon the first clicking of "T" or "C" the program's GUI "flickers" for a second. Thereafter everything is perfectly smooth. There's probably a way to eliminate this. It's unclear if it is at the program or toolkit layer. Also if you click "H" or "V" when the program is maximized, perhaps ximtool should keep the total GUI area the same and make the image smaller when introducing the graphs. (When you unclick "H" or "V", it makes the image bigger so it stands to reason...)
Jason
Most seriously, I can get crashes by simply clicking and unclicking H or V. The crash is reproducible but the number of clicks is usually between 7 and 11 and is not a set number. I've been doing it immediately after starting up ximtool without any image displayed. The crash gives the following error:
ERROR (733, "Illegal file descriptor (bad fd or file not open)")
In addition, upon unclicking H or V, there's frequently a bunch of terminal output.
ximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial numbximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 17139
Current serial number in output stream: 17141
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 70 (X_PolyFillRectangle)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17140
Current serial number in output stream: 17141
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17143
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17145
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 17148
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 17150
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17599
Current serial number in output stream: 17786
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17603
Current serial number in output stream: 17786
er of failed request: 17139
Current serial number in output stream: 17141
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 70 (X_PolyFillRectangle)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17140
Current serial number in output stream: 17141
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17143
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17145
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 17148
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 53 (X_CreatePixmap)
Serial number of failed request: 17150
Current serial number in output stream: 17155
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17599
Current serial number in output stream: 17786
ximtool: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 62 (X_CopyArea)
Resource id in failed request: 0x4e00d2e
Serial number of failed request: 17603
Current serial number in output stream: 17786
On a different note, two less severe things... I usually use ximtool or ds9 maximized on a second monitor. I frequently display an image but then need the toolbars "T" and "C". Often upon the first clicking of "T" or "C" the program's GUI "flickers" for a second. Thereafter everything is perfectly smooth. There's probably a way to eliminate this. It's unclear if it is at the program or toolkit layer. Also if you click "H" or "V" when the program is maximized, perhaps ximtool should keep the total GUI area the same and make the image smaller when introducing the graphs. (When you unclick "H" or "V", it makes the image bigger so it stands to reason...)
Jason
Mike Fitzpatrick wrote on Dec 22, 2008
Hi Jason,
Thanks for the reports. Most of what you describe is already known and being worked on. Be sure you've got the latest binary which is supposed to fix the BadAlloc problem, although this was usually a startup issue. I'll try to reproduce the crash as that is something new, but it will probably depend on the machine and the amount of X server memory (i.e. the earlier problem was an uninitialized variable causing a huge pixmap to be created that exceeded the server's capability). It may be that as you open/close the H/V plots something isn't being freed and reallocated properly.
Otherwise, there are known issues with resizing the window that cause the flicker and other strange behaviors (e.g. open 'H' before 'V' and it appears normal, do the reverse and the size gets weird).
Cheers,
-Mike
Thanks for the reports. Most of what you describe is already known and being worked on. Be sure you've got the latest binary which is supposed to fix the BadAlloc problem, although this was usually a startup issue. I'll try to reproduce the crash as that is something new, but it will probably depend on the machine and the amount of X server memory (i.e. the earlier problem was an uninitialized variable causing a huge pixmap to be created that exceeded the server's capability). It may be that as you open/close the H/V plots something isn't being freed and reallocated properly.
Otherwise, there are known issues with resizing the window that cause the flicker and other strange behaviors (e.g. open 'H' before 'V' and it appears normal, do the reverse and the size gets weird).
Cheers,
-Mike
James Turner wrote on Dec 22, 2008
Hi Mike,
I am getting this error when trying to start the latest ximtool 2beta on RedHat Enterprise 5 with a 16-bit display (which I think must be a requirement for our control screens on this ops machine). Do you expect this to work?
The xdpyinfo is the following:
Thanks,
James.
I am getting this error when trying to start the latest ximtool 2beta on RedHat Enterprise 5 with a 16-bit display (which I think must be a requirement for our control screens on this ops machine). Do you expect this to work?
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 91 (X_QueryColors)
Value in failed request: 0xffffff
Serial number of failed request: 272
Current serial number in output stream: 272
The xdpyinfo is the following:
name of display: :0.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 70101000
X.Org version: 7.1.1
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x1a00007, revert to PointerRoot
number of extensions: 30
BIG-REQUESTS
DAMAGE
DPMS
Extended-Visual-Information
GLX
MIT-SCREEN-SAVER
MIT-SHM
MIT-SUNDRY-NONSTANDARD
NV-CONTROL
NV-GLX
RECORD
RENDER
SECURITY
SHAPE
SYNC
TOG-CUP
X-Resource
XC-APPGROUP
XC-MISC
XFIXES
XFree86-Bigfont
XFree86-DGA
XFree86-Misc
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
XVideo-MotionCompensation
default screen number: 0
number of screens: 1
screen #0:
dimensions: 4800x2400 pixels (1296x642 millimeters)
resolution: 94x95 dots per inch
depths (7): 16, 1, 4, 8, 15, 24, 32
root window id: 0x4ea
depth of root window: 16 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x20
default number of colormap cells: 64
preallocated pixels: black 0, white 65535
options: backing-store NO, save-unders NO
largest cursor: 64x64
current input event mask: 0xfa4031
KeyPressMask EnterWindowMask LeaveWindowMask
KeymapStateMask StructureNotifyMask SubstructureNotifyMask
SubstructureRedirectMask FocusChangeMask PropertyChangeMask
ColormapChangeMask
number of visuals: 40
default visual id: 0x21
visual:
visual id: 0x21
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x22
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x23
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x24
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x25
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x26
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x27
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x28
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x29
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2a
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2b
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2c
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2d
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2e
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x2f
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x30
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x31
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x32
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x33
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x34
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x35
class: TrueColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x36
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x37
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x38
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x39
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3a
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3b
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3c
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3d
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3e
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x3f
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x40
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x41
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x42
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x43
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x44
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x45
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x46
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x47
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
visual:
visual id: 0x48
class: DirectColor
depth: 16 planes
available colormap entries: 64 per subfield
red, green, blue masks: 0xf800, 0x7e0, 0x1f
significant bits in color specification: 8 bits
Thanks,
James.
Mike Fitzpatrick wrote on Dec 22, 2008
Hi James,
16-bit displays aren't yet supported, just stubbed out in the code and put off to the 'final' work (whenever I get back to doing that). It requires some small changes in the rendering code to map the pixel RGB values, but for now I'm not surprised there is an error when there are no 24 (or 32)-bit TrueColor visuals available. Sorry.
-Mike
16-bit displays aren't yet supported, just stubbed out in the code and put off to the 'final' work (whenever I get back to doing that). It requires some small changes in the rendering code to map the pixel RGB values, but for now I'm not surprised there is an error when there are no 24 (or 32)-bit TrueColor visuals available. Sorry.
-Mike
James Turner wrote on Dec 22, 2008
OK, thanks for the info. That's useful to know about. Though I fear it might mean observing with just DS9 for a while after all :-(.
James.
James.
Mike Fitzpatrick wrote on Dec 22, 2008
Hopefully not too much longer. It shouldn't be hard and I'll try to squeeze it into the next release (this week or next maybe?), it's just been inconvenient to setup a test environment till now and I didn't think 16-bit was still being routinely used.
Cheers,
-Mike
Cheers,
-Mike
Mike Reed wrote on Dec 22, 2008
Hi,
I just downloaded the beta x11iraf (the Redhat binary version, just for the xgterm and ecl, I use ds9) and am having a problem with xgterm. When I first started it, I got this message:xgterm: error while loading shared libraries: libXmu.so.6: cannot open shared object file: No such file or directory
And so I made a link in /usr/lib to /usr/lib to /usr/lib64/libXmu.so.6,
But now I get the following error message:
xgterm: error while loading shared libraries: libXmu.so.6: wrong ELF class: ELFCLASS64
Any thoughts on how to fix this?
Thanks,
Mike Reed
I just downloaded the beta x11iraf (the Redhat binary version, just for the xgterm and ecl, I use ds9) and am having a problem with xgterm. When I first started it, I got this message:xgterm: error while loading shared libraries: libXmu.so.6: cannot open shared object file: No such file or directory
And so I made a link in /usr/lib to /usr/lib to /usr/lib64/libXmu.so.6,
But now I get the following error message:
xgterm: error while loading shared libraries: libXmu.so.6: wrong ELF class: ELFCLASS64
Any thoughts on how to fix this?
Thanks,
Mike Reed
James Turner wrote on Dec 22, 2008
fitz
Hopefully not too much longer. It shouldn't be hard and I'll try to squeeze it into the next release (this week or next maybe?), it's just been inconvenient to setup a test environment till now and I didn't think 16-bit was still being routinely used.
Let me know if you want something testing...
As for 16-bit being used routinely, I was surprised too and will check on why, but I'm sure there must be a good reason.
James.
James Turner wrote on Dec 22, 2008
mikesdbv
And so I made a link in /usr/lib to /usr/lib to /usr/lib64/libXmu.so.6,
But now I get the following error message:
xgterm: error while loading shared libraries: libXmu.so.6: wrong ELF class: ELFCLASS64
I'm guessing here, but I think the problem is that xgterm was built as a 32-bit binary and you are running it on a 64-bit OS. You probably need to look for a 32-bit version of libXmu.so.6 in another directory on your system that contains 32-bit compatiblity libraries. I don't have enough experience yet to tell you where to look, but I bet Google has...
Cheers,
James.
Mike Reed wrote on Dec 22, 2008
Thanks James, however I have not had any luck. I can't seem to find any such 32-bit files on my system. I found a website (from 2006, so predating FC10) that says to do "yum install xorg-x11-libs.i386" but when I do that, it claims there is no package available. When I do an rpm search, I only find an i386 version for FC9 (and it shows a lot of dependencies).
Any other suggestions or help would be much appreciated. Hopefully someone has xgterm working on an FC10 system.
Mike
Any other suggestions or help would be much appreciated. Hopefully someone has xgterm working on an FC10 system.
Mike
Mike Fitzpatrick wrote on Dec 22, 2008
Try http://iraf.net/ftp/pub/xgterm.LNUX.STATIC
It may avoid the shared library problems for 64-bit systems.
-Mike
It may avoid the shared library problems for 64-bit systems.
-Mike
James Turner wrote on Dec 22, 2008
Just in case you have problems with other binaries than xgterm, rpmfind.net seems to suggest that you can use the FC9 package on FC10, if I understood correctly (I haven't tried it -- not running FC10):
http://rpmfind.net//linux/RPM/fedora/9/x86_64/libXmu-1.0.4-1.fc9.i386.html
http://rpmfind.net//linux/RPM/fedora/9/x86_64/libXmu-1.0.4-1.fc9.i386.html
Mike Reed wrote on Dec 22, 2008
Thanks for the help. The static version worked.... at least to start xgterm. No I can start using IRAF on FC10 to see if I can uncover any more bugs. Hopefully not.
Thanks again,
Mike
Thanks again,
Mike
James Turner wrote on Dec 22, 2008
fitz
Hopefully not too much longer. It shouldn't be hard and I'll try to squeeze it into the next release (this week or next maybe?), it's just been inconvenient to setup a test environment till now and I didn't think 16-bit was still being routinely used.
Just FYI, we were able to get the relevant display changed to 24 bits, so this is currently no longer a problem (though it would of course be nice for ximool to support 16 bits as and when there's a moment for it).
James.
PS. I see you have a new release, but it sounds like it just affects Cygwin.
Last post on Dec 22, 2008