Sponsored Content
Top Forums Shell Programming and Scripting X Forwarding issue on Solaris 11 Post 303024051 by ajayram_arya on Thursday 27th of September 2018 02:51:08 PM
Old 09-27-2018
X Forwarding issue on Solaris 11

Hello All , Need assistance in finding out a solution for X Forwarding issue

IBM applications requires X Forwarding . Server X11 works fine when i try xclock but not this application . On a different server with the same OS it is working . Need inputs .

OS Version : Solaris 11 with updated patches .

Error
Code:
The program 'IBMIM' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 46 error_code 2 request_code 147 minor_code 4)
  (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.)
The program 'IBMIM' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 46 error_code 2 request_code 147 minor_code 4)
  (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.)

 

10 More Discussions You Might Find Interesting

1. Cybersecurity

ssh X-forwarding and remote forwarding behind proxy

Hi, from my workplace we use a proxy to connect to the outside world, including external ssh servers. The problem is that the server is seeing the connection coming from the proxy and knows nothing about the client behind it. The ssh connection itself works fine, but x-forwarding does not work as... (1 Reply)
Discussion started by: vampirodolce
1 Replies

2. Solaris

Port/IP Forwarding in Solaris 10.0

Hi, I am looking out a way to forward all UDP traffic coming on ports 3001,3002,3003 and 3004 on server 10.2.45.200 to corresponding ports of server 10.2.45.197. I am using Solaris 10.0. -bash-3.00$ uname -a SunOS airtelussd2 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V445 Is... (6 Replies)
Discussion started by: vikas027
6 Replies

3. Solaris

Solaris Issue

Hi, I am having a serious problem with a Solaris 2.6 box. Whenever I try and tar a large directory I get this error:tar: write error: unexpected EOF My own research shows that I might have to enable tarring large files by this command: fsadm -o largefiles <mountpoint> My box does not... (8 Replies)
Discussion started by: mojoman
8 Replies

4. Solaris

ip and port forwarding in Solaris 10

Hi; I have the following issue: I have a Solaris server running an old applications which connects to an http server in other server at certain port. The thing is that the http server has changed its ip and port and the addres in the app is hard coded and touching the app by now is out of the... (0 Replies)
Discussion started by: ppereira
0 Replies

5. Solaris

du -sh issue in solaris 10

i have 30 file systems on my production system and my system is responding too slow and / is 99% full is there any way i can run the du -sh only on root file systems and skip all the SAN file systems as the system is unable to do du -sdh * / as it would try to run du on all the SAN/NAS file... (5 Replies)
Discussion started by: fugitive
5 Replies

6. Solaris

IP Forwarding on Solaris 10 (should be simple, but isn't!)

I'm having a hard time getting IP forwarding to work. I'll eventually have several interfaces, but all that matters for now is that two of them actually be able to IP forward. I have no network interfaces in the global zone, but both interfaces are in the same zone, Common. The IPs I've been... (0 Replies)
Discussion started by: cfalcon
0 Replies

7. IP Networking

NAT Forwarding Issue Endian and Vyatta Firewall

I've experienced this same issue with both the Endian Firewall Appliance and a Vyatta Firewall Appliance. Conversely, it works with a Draytek Firewall/Router. I am trying to forward port 80 traffic to my internal web server which is located on the /24 subnet. I have an external static IP which... (0 Replies)
Discussion started by: mboudro
0 Replies

8. Solaris

Vi issue with solaris

I'm facing a peculiar issue when using vi on solaris. When i open a file using vi & search for a string pattern & if that pattern is not found & if i exit, vi exits with return value 1. (Checked the return value with 'echo $?' ). When the string is found, vi exits with return value 0. This... (9 Replies)
Discussion started by: pj87
9 Replies

9. IP Networking

Port forwarding issue

hi guys i have a simple question ! i have two ips . a valid and internal(172.16.11.2) i want to use port forwarding to forward any request to valid IP port 8001 to internal ip port 80 . i use this rule : sysctl -w net.ipv4.ip_forward=1 iptables -t nat -A PREROUTING -p tcp... (1 Reply)
Discussion started by: mhs
1 Replies

10. Emergency UNIX and Linux Support

Proxmox dedicated Port forwarding issue Using Default Drop Chain filter

Hi Everyone, Hope all Doing good, we have a Dedicated server and its installed with proxmox VE 3.2, My Need is i want Protect my server and only i need to allow the specific port in the server, And i want to forward some of ports 22,80,443 to those VM's inside my dedicated... (0 Replies)
Discussion started by: babinlonston
0 Replies
Tk_CreateErrorHandler(3)				       Tk Library Procedures					  Tk_CreateErrorHandler(3)

__________________________________________________________________________________________________________________________________________________

NAME
Tk_CreateErrorHandler, Tk_DeleteErrorHandler - handle X protocol errors SYNOPSIS
#include <tk.h> Tk_ErrorHandler Tk_CreateErrorHandler(display, error, request, minor, proc, clientData) Tk_DeleteErrorHandler(handler) ARGUMENTS
Display *display (in) Display whose errors are to be handled. int error (in) Match only error events with this value in the error_code field. If -1, then match any error_code value. int request (in) Match only error events with this value in the request_code field. If -1, then match any request_code value. int minor (in) Match only error events with this value in the minor_code field. If -1, then match any minor_code value. Tk_ErrorProc *proc (in) Procedure to invoke whenever an error event is received for display and matches error, request, and minor. NULL means ignore any matching errors. ClientData clientData (in) Arbitrary one-word value to pass to proc. Tk_ErrorHandler handler (in) Token for error handler to delete (return value from a previous call to Tk_CreateErrorHandler). _________________________________________________________________ DESCRIPTION
Tk_CreateErrorHandler arranges for a particular procedure (proc) to be called whenever certain protocol errors occur on a particular dis- play (display). Protocol errors occur when the X protocol is used incorrectly, such as attempting to map a window that does not exist. See the Xlib documentation for XSetErrorHandler for more information on the kinds of errors that can occur. For proc to be invoked to han- dle a particular error, five things must occur: [1] The error must pertain to display. [2] Either the error argument to Tk_CreateErrorHandler must have been -1, or the error argument must match the error_code field from the error event. [3] Either the request argument to Tk_CreateErrorHandler must have been -1, or the request argument must match the request_code field from the error event. [4] Either the minor argument to Tk_CreateErrorHandler must have been -1, or the minor argument must match the minor_code field from the error event. [5] The protocol request to which the error pertains must have been made when the handler was active (see below for more information). Proc should have arguments and result that match the following type: typedef int Tk_ErrorProc( ClientData clientData, XErrorEvent *errEventPtr); The clientData parameter to proc is a copy of the clientData argument given to Tcl_CreateErrorHandler when the callback was created. Typi- cally, clientData points to a data structure containing application-specific information that is needed to deal with the error. ErrEventPtr is a pointer to the X error event. The procedure proc should return an integer value. If it returns 0 it means that proc han- dled the error completely and there is no need to take any other action for the error. If it returns non-zero it means proc was unable to handle the error. If a value of NULL is specified for proc, all matching errors will be ignored: this will produce the same result as if a procedure had been specified that always returns 0. If more than more than one handler matches a particular error, then they are invoked in turn. The handlers will be invoked in reverse order of creation: most recently declared handler first. If any handler returns 0, then subsequent (older) handlers will not be invoked. If no handler returns 0, then Tk invokes X's default error handler, which prints an error message and aborts the program. If you wish to have a default handler that deals with errors that no other handler can deal with, then declare it first. The X documentation states that "the error handler should not call any functions (directly or indirectly) on the display that will generate protocol requests or that will look for input events." This restriction applies to handlers declared by Tk_CreateErrorHandler; disobey it at your own risk. Tk_DeleteErrorHandler may be called to delete a previously-created error handler. The handler argument identifies the error handler, and should be a value returned by a previous call to Tk_CreateEventHandler. A particular error handler applies to errors resulting from protocol requests generated between the call to Tk_CreateErrorHandler and the call to Tk_DeleteErrorHandler. However, the actual callback to proc may not occur until after the Tk_DeleteErrorHandler call, due to buffering in the client and server. If an error event pertains to a protocol request made just before calling Tk_DeleteErrorHandler, then the error event may not have been processed before the Tk_DeleteErrorHandler call. When this situation arises, Tk will save information about the handler and invoke the handler's proc later when the error event finally arrives. If an application wishes to delete an error handler and know for certain that all relevant errors have been processed, it should first call Tk_DeleteErrorHandler and then call XSync; this will flush out any buffered requests and errors, but will result in a performance penalty because it requires communication to and from the X server. After the XSync call Tk is guaranteed not to call any error handlers deleted before the XSync call. For the Tk error handling mechanism to work properly, it is essential that application code never calls XSetErrorHandler directly; applica- tions should use only Tk_CreateErrorHandler. KEYWORDS
callback, error, event, handler Tk Tk_CreateErrorHandler(3)
All times are GMT -4. The time now is 07:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy