[linux-audio-dev] Re: X Error: BadWindow errors with qjackctl 0.2.15a

From: Rui Nuno Capela <rncbc@email-addr-hidden>
Date: Fri Feb 18 2005 - 01:23:44 EET

Lee Revell wrote:
> Every time I start qjackctl from a remote X session I get these errors
> at startup. I am using the Cygwin X server.
>
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadAtom (invalid Atom parameter) 5
> Major opcode: 18
> Minor opcode: 0
> Resource id: 0x134
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 7
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 7
> Minor opcode: 0
> Resource id: 0x3a
>
> Then if I activate the Messages window and move the mouse back and forth
> between it and the qjackctl window I get tons of these. They seem to be
> associated with the tooltips popping up in the main qjackctl window.
>
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 38
> Minor opcode: 0
> Resource id: 0x3a
>
> The latter are especially annoying as they spam the Messages window not
> the xterm I launched qjackctl from.
>

I thought these messages were harmless :/ I also get something like this,
always for all (my) Qt apps:

X Error: BadDevice, invalid or uninitialized input device 155
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 155
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

AFAICR this started somewhere since some Qt 3.3.x, don't know really since...

Again , I think this is simply noise, but can be hidding something under
the sheets .... :)

-- 
rncbc aka Rui Nuno Capela
rncbc@email-addr-hidden
Received on Fri Feb 18 04:15:04 2005

This archive was generated by hypermail 2.1.8 : Fri Feb 18 2005 - 04:15:05 EET