[Thread Prev][Thread Next][Index]

Re: [ferret_users] ferret7.1: segfault in vnc when quitting ferret



Thanks Karl,

 

I just gave it (pyFerret) a go and got the following error:

 

***

(uvcdatNightly) duro@ocean:[tmp]:[4933]> pyferret

        NOAA/PMEL TMAP

        PyFerret v7.1 (optimized)

        Linux 3.13.0-107-generic - 03/28/17

        24-Apr-17 10:43

 

yes? use "/usr/local/anaconda2/envs/v2.8-2-g42af3f9/share/uvcdat/sample_data/clt.nc"

           *** NOTE: Units on axis "plev" are not recognized: hPa

           *** NOTE: They will not be convertible:

           *** NOTE: cannot parse "units since date", date= "1978-12"; leaving units string

           *** NOTE: Units on axis "plev1" are not recognized: hPa

           *** NOTE: They will not be convertible:

           *** NOTE: cannot parse "units since date", date= "1978-12"; leaving units string

yes? sh da

     currently SET data sets:

    1> /usr/local/anaconda2/envs/v2.8-2-g42af3f9/share/uvcdat/sample_data/clt.nc  (default)

name     title                             I         J         K         L

CLT      Total cloudiness                 1:72      1:46      ...       1:120

U                                         1:97      1:80      1:2       1:1

V                                         1:97      1:80      1:2       1:1

 

yes? sha clt[l=1]

yes? frame/file='ferret.gif'

**ERROR: invalid command: grdelWindowSave: error when calling the Python binding's saveWindow method: **ERROR <type 'exceptions.ValueError'>: Unable to save the plot as 'ferret.gif'

***

 

Any tips as to how to solve this?

 

From: Karl Smith - NOAA Affiliate <karl.smith@xxxxxxxx>
Date: Friday, April 21, 2017 at 11:59 AM
To: "Durack, Paul J." <durack1@xxxxxxxx>
Cc: ferret_users <ferret_users@xxxxxxxx>
Subject: Re: [ferret_users] ferret7.1: segfault in vnc when quitting ferret

 

Hi Paul,

 

The issues arose because of changes in the operating system software, not because of any change in the ferret code.  However there are my changes to work around those issues that arose (which just change what X events are caught by ferret, but also some trivial changes for the Mac build).  However, all those were made after the 6.9.3 release.

 

Karl

 

 

On Thu, Apr 20, 2017 at 6:36 PM, Durack, Paul J. <durack1@xxxxxxxx> wrote:

Thanks for responding Karl,

 

I haven’t tried pyFerret – I’ll take a look at it.

 

I just confirmed that my same segfault error also occurs with the 6.9.3 release, so how far would I have to go back to attempt to get around these X11 triggering issues?

 

Cheers,

 

P

 

From: Karl Smith - NOAA Affiliate <karl.smith@xxxxxxxx>
Date: Thursday, April 20, 2017 at 3:12 PM
To: "Durack, Paul J." <durack1@xxxxxxxx>
Cc: ferret_users <ferret_users@xxxxxxxx>
Subject: Re: [ferret_users] ferret7.1: segfault in vnc when quitting ferret

 

Hi Paul,

 

Have you tried using PyFerret?  It should be a drop-in replacement for Ferret as far as using working from the ferret prompt and running ferret scripts.  It will be somewhat slower plotting, but will give much better graphics and will allow you to save plots directly as PDF's.

 

Why I mention this is traditional Ferret uses some rather old X11 code for displaying plots, and has recently started having some issues we have had to work around.  (Primarily changes in the X11 events that are generated when things happen with the window.)  My gut feeling is that this old X11 code might be related to the VNC viewer error.  PyFerret uses Qt (via PyQt) to display plots and does not have any of the old X11 code in it.

 

Best regards,

Karl

 

 

On Thu, Apr 20, 2017 at 2:02 PM, Durack, Paul J. <durack1@xxxxxxxx> wrote:

Hi folks,

 

I’m getting a segfault in my vnc instance when quitting ferret (whilst using a VNC session: tigervnc 1.7.1) on a RHEL6.9 machine (Xorg 1.17.4). I have raised this issue on the tigervnc issue list (https://github.com/TigerVNC/tigervnc/issues/439) and also have opened a bug report on the RHEL6 support site (https://bugzilla.redhat.com/show_bug.cgi?id=1438898) but I’m not expecting a quick response.

 

Has anyone else hit similar errors with ferret v7.1 or earlier releases? I’d very much like to attempt to fix my error so I can get myself up and working again

 

Cheers,

 

P



 

--

Karl M. Smith, Ph.D.
JISAO Univ. Wash. and PMEL NOAA
"The contents of this message are mine personally and do
not necessarily reflect any position of the Government
or the National Oceanic and Atmospheric Administration."



 

--

Karl M. Smith, Ph.D.
JISAO Univ. Wash. and PMEL NOAA
"The contents of this message are mine personally and do
not necessarily reflect any position of the Government
or the National Oceanic and Atmospheric Administration."


[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce / NOAA / OAR / PMEL / Ferret

Privacy Policy | Disclaimer | Accessibility Statement