Hi Ansley and All, I have looked a bit more into my X-display problem. Yes, I use nx to connect to a remote machine. Everything was fine until they upgraded the system last December… The nx version is the NoMachine Enterprise client 5.0.47 and the system runs the window system MATE (not Gnome any more, what we had before the upgrade). The DISPLAY variable is set and I can start an xclock. That even works when I spawn a shell in ferret and call the xclock from that subshell. Just to make sure I exported the DISPLAY variable. Does not help. I run ferret from an xterm – thinking that maybe the MATE window is the problem – did not help. My DISPLAY variable looks like this: declare -x DISPLAY=":1058" The error is: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 I guess. that says that the command X_ConfigureWindow got a 0x0 – so a zero – and it did not like that. The man page for that says that it uses the XWindowChanges structure and that says: “The width and height members are used to set the inside size of the window, not including the border, and must be nonzero, or a BadValue error results.” I cannot understand what is wrong unless there is somehow the option to specify 0 for window size for a default and the system here does not like it. Or somehow the DISPLAY variable is modified to a zero – maybe you take the part before the : But surely many people would have had these problems if anything of that was the case… If I run ferret in batch mode and then convert the metafile to a postscript and that to a jpeg with gs, it works. In this case all colour information is run through the metafile and gs…
Anybody any insights? Our system folks don’t know either… THank you very much! Kind regards Joerg Jörg Kaduk Associate Professor http://www.geog.le.ac.uk/staff/jk61/ ORCID:
http://orcid.org/0000-0003-4051-3081
e: jk61@xxxxxxxx t: +44 (0)116 252 3848 Department of Geography, University of Leicester, University Road, Leicester LE1 7RH, UK Elite Without Being Elitist Follow us on
Twitter or visit our
Facebook page and the Departmental
Twitter and
Facebook page From: owner-ferret_users@xxxxxxxx [mailto:owner-ferret_users@xxxxxxxx]
On Behalf Of Ansley C. Manke Hi Joerg, Is your DISPLAY environment variable set? Are you perhaps running Ferret on a machine other than your desktop machine? If so you'll need to make sure that the display forwarding is set up correctly. A test for this is whether a Unix command such as
xclock works. This issue does comes up from time to time; search for "display" in the Users List Archives for a few more discussions.
Another option might be for you to use PyFerret. Ansley On 4/10/2017 8:37 AM, Kaduk, Jorg D. (Dr.) wrote:
No virus found in this message. |