[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: X protocol errors
From: |
Mike Miller |
Subject: |
Re: X protocol errors |
Date: |
Tue, 4 Mar 2014 13:55:39 -0500 |
On Tue, Mar 4, 2014 at 13:36:47 -0500, John W. Eaton wrote:
> I've been getting some complaints about X protocol errors that look like
> this:
>
> Warning: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> Major opcode: 62 (X_CopyArea)
> Resource id: 0x0
> Warning: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> Major opcode: 62 (X_CopyArea)
> Resource id: 0x0
> Warning: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> Major opcode: 62 (X_CopyArea)
> Resource id: 0x0
> Warning: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
> Major opcode: 62 (X_CopyArea)
> Resource id: 0x0
>
> I believe they are happening when the Octave GUI (3.8.0) is running on
> a remote system (local X DISPLAY).
>
> Does anyone else see errors like this when running the Octave GUI?
Definitely when Octave is running on Xvnc:
http://savannah.gnu.org/bugs/?41304
IIRC the errors correspond to the first appearance of any popup menu,
e.g. menu bar, context menu.
--
mike
- X protocol errors, John W. Eaton, 2014/03/04
- Re: X protocol errors,
Mike Miller <=
- Re: X protocol errors, John W. Eaton, 2014/03/11
- Re: X protocol errors, Mike Miller, 2014/03/12
- Re: X protocol errors, John W. Eaton, 2014/03/13
- Re: X protocol errors, Mike Miller, 2014/03/13
- Message not available
- Re: X protocol errors, Mike Miller, 2014/03/14
- Re: X protocol errors, John W. Eaton, 2014/03/14
- Re: X protocol errors, Mike Miller, 2014/03/14
- Re: X protocol errors, John W. Eaton, 2014/03/14
- Re: X protocol errors, Mike Miller, 2014/03/14