Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
... I have a customer that has the following scenario : A DECstation 5000 Model 200 CX running UWS 2.2D, 16 MG memory they also have an NCD X terminal and an AT&T 386 machine ... here is what they want to do : using telnet on the NCD they login to the DECstation 5000, then set the display back to the NCD. Then they want to start dxsession and have it display on the NCD. When they try this they get the following error messages : X Protocol error detected by server. Bad Access - attempt to access private resource Failed request major opcode 111 (X_SetAccessControl). This works fine with such clients as clock, calculator and dxwm. Only the session mananger gives this error. This is doable on the VT1000 but not on the NCD or the AT&T machine. Any help is appreciated .... _ellen
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2669.1 | sm*security: False | OPHION::MIKEY | Mike Yang | Thu Apr 26 1990 17:11 | 6 |
The problem is that dxsession attempts to set the security list of its display. This can only be done from a local client. To disable, put the following in your .Xdefaults: sm*security: False | |||||
2669.2 | sm*secuirty False does not work | ROYALT::MISHRA | Mon Oct 01 1990 16:05 | 38 | |
Hi, I have a two system running ULTRIX UWS v2.0, I have started the X-server on machine A by using the command # /usr/bin/Xqvsm -fd 75 & server comes up without any problem, now from machine B I issued following commands dxterm -d A:0 & dxterm comes up without any problem, now when I type (inside dxterm ) csh>dxsession -d A:0 I get following message, and dxsession exits. X Protocol error detected by server: attempt to access private resource Failed request major op code 111 X_SetAccessControl Failed request minor op code 0 (if applicable) ResourceID 0x8006b in failed request (if applicable) Serial number of failed request 15 Current serial number in output stream 26 I have also put sm*security: false in the .Xdefaults file still I get above mentioned error. any clues, Thanks in advance Alok Kumar | |||||
2669.3 | try UWS4.0 | OXNARD::KLEE | Ken Lee | Wed Oct 03 1990 16:05 | 4 |
I'm told that this problem is fixed in UWS4.0. You don't even need the sm*security: False resource now. Ken |