search for: badatom

http://bugzilla.mindrot.org/show_bug.cgi?id=851 Summary: some X11 prgs generate ``BadAtom (invalid Atom parameter)'' in X_GetProperty when using X11 forwarding Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P2 C...

...t klima-pc ~]# iptables-save [root at klima-pc ~]# SELinux is OFF I am connecting by ssh with Xforwarding enabled to - Centos 3 box [09:32 root at tux:root]# gvim --sync The program 'gvim' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 287 error_code 5 request_code 20 minor_code 0) (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...

Folks, This morning I downloaded and installed a security update for my MAC G5. I am running MAC OSX 10.3.9. Friday March 16 I was able to ssh -X me at targetcpu and launch my application this morning March 19 I get this error: X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 20 (X_GetProperty) Atom id in failed request: 0x25 Serial number of failed request: 309 Current serial number in output stream: 309 I can get an xclock window to open but the GUI for my application is not able to launch. I can...

...term The terminal comes up and I can work with it - without the mouse. If I left click the mouse and highlight any text in the xterm, I get a fatal error and the xterm closes. The error is consistent and happens every time. xterm xterm: warning, error event received: X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 18 (X_ChangeProperty) Atom id in failed request: 0x185 Serial number of failed request: 218 Current serial number in output stream: 220 When I log in using telnet and doing the xhost thing, the window does not crash. I am not sur...

...8>, |ssh| will now use untrusted X11 cookies by default. The previous behaviour can be restored by setting *ForwardX11Trusted yes* in /ssh_config/. Possible symptoms include: |BadWindow (invalid Window parameter) BadAccess (attempt to access private resource denied) X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 20 (X_GetProperty)|

...and the server is 3.5p1, most X Window System clients work OK, but the following fail with the indicated obscure error messages: xmag BadDrawable (infinite loop of this error) xwd BadWindow xcalc (intermittent; sorry, didn't write down the code) tcl/tk apps BadAtom doing X_GetProperty for 0x1a0 = InterpRegistry. To demonstrate, it's sufficient to do "wish" with no script. Opera, Konqueror, Mozilla and Netscape were not tested but they all have a feature similar to tcl/tk and most likely would fail similarly. This is a property on the root...