Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down at the end of May, and its replacement, statalist.org is already up and running.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: A may be a bug when one save a Boxplot by right click on it


From   Orvalho Augusto <orvaquim@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   st: A may be a bug when one save a Boxplot by right click on it
Date   Sun, 8 May 2011 08:35:32 +0200

I am using Ubuntu Linux 10.04 32bit on a lenovo R61 laptop with 3.5 GB
of RAM. My screen is extended to two screens (so a have a lot screen
to work).

I have stata 11 updated to the latest (version 11.2) as shown by:
. update query
(contacting http://www.stata.com)

Stata executable
    folder:               /usr/local/stata11/
    name of file:         xstata-se
    currently installed:  30 Mar 2011
    latest available:     30 Mar 2011

Ado-file updates
    folder:               /usr/local/stata11/ado/
updates/
    names of files:       (various)
    currently installed:  30 Mar 2011
    latest available:     30 Mar 2011

Utilities updates
    folder:               /usr/local/stata11/utilities
    names of files:       (various)
    currently installed:  01 Sep 2010
    latest available:     01 Sep 2010

Recommendation
    Do nothing; all files up to date.
==============================================

I read my data with
xstata-se use resistencias_20110505

I do a simple boxplot with:
graph box age, over(resiste12)

When I right click on the plot and then choose save as. Stata goes
away. With error below:

orvaquim@cavemanpc:/mnt/disco/data/dedia2/work/vermelhosdenovo/dados$
Xlib:  extension "RANDR" missing on display ":0.0".
The program 'xstata-se' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 102032 error_code 8 request_code 151 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Thank you
Orvalho J Augusto

*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index