| Title: | note 3 has pointer to current kit |
| Notice: | note 3 has pointer to current kit |
| Moderator: | PEACHS::GHEFF |
| Created: | Wed May 29 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3301 |
| Total number of notes: | 14905 |
Hi there I'm having a number of problems with eXcursion trying to display from a Digital Unix 3.2G system with CDE. eXcursion is V3.0.554 on NT 4.0 Alpha and Intel (same results). The main problems are when I try to use XDMCP (I then use the Single Window mode but the same things happen in Multiple Windows mode): 1/ When eXcursion starts, I get a bunch of message boxes with text like : "Couldn't add font path element /etc/dt/config/xfonts/C" for a bunch of fonts. I *did* the font thing for CDE listed in the eXcursion release notes. 2/ After I've been through the fonts message boxes, I get the login screen, I can login, and I get the main screen with the CDE Front Panel, the file manager and the desktop help thing. I can use the File Manager just fine but whenever I touch the Front Panel (just trying to fire up a terminal, or pressing the Exit button or anything), all freezes: the front panel is totally unresponsive, the file manager (which was OK seconds before) is unresponsive, etc. eXcursion is NOT hung as I can use another terminal to set the DISPLAY back to my NT system and start an Xterm that way, the Xterm comes up and is usable, but the rest remains broken. Here's what's in eXcursion log: 11/04/97 15:27:35 X Server Information eXcursion X3.0.554 (Alpha) logging enabled. 11/04/97 15:27:35 Network Warning setsockopt(304) failed, error=ENOPROTOOPT 11/04/97 15:27:40 X Server Error couldn't set fpe '/etc/dt/config/xfonts/C' 11/04/97 15:27:40 X Server Warning Couldn't add font path element /etc/dt/config/xfonts/C 11/04/97 15:27:55 X Server Error couldn't set fpe '/usr/dt/config/xfonts/C' 11/04/97 15:27:55 X Server Warning Couldn't add font path element /usr/dt/config/xfonts/C 11/04/97 15:27:56 X Server Error couldn't set fpe '/usr/lib/X11/fonts/decwin/75dpi' 11/04/97 15:27:56 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/decwin/75dpi 11/04/97 15:27:56 X Server Error couldn't set fpe '/usr/lib/X11/fonts/Speedo/' 11/04/97 15:27:56 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/Speedo/ 11/04/97 15:27:57 X Server Error couldn't set fpe '/usr/lib/X11/fonts/Type1/' 11/04/97 15:27:57 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/Type1/ 11/04/97 15:27:57 X Server Error couldn't set fpe '/usr/lib/X11/fonts/Type1Adobe/' 11/04/97 15:27:57 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/Type1Adobe/ 11/04/97 15:27:58 X Server Error couldn't set fpe '/usr/lib/X11/fonts/user/75dpi' 11/04/97 15:27:58 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/user/75dpi 11/04/97 15:27:58 X Server Error couldn't set fpe '/usr/lib/X11/fonts/user/misc' 11/04/97 15:27:58 X Server Warning Couldn't add font path element /usr/lib/X11/fonts/user/misc 11/04/97 15:27:59 Network Warning recv(364) failed, error=EWOULDBLOCK 11/04/97 15:28:17 X Protocol Error Reply sent to Client #8, Request=QueryFont, Error=BadFont 11/04/97 15:28:17 X Protocol Error Reply sent to Client #8, Request=QueryFont, Error=BadFont 11/04/97 15:28:17 X Protocol Error Reply sent to Client #8, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #8, Request=MapWindow, Error=BadWindow 11/04/97 15:28:18 X Protocol Error Reply sent to Client #8, Request=ChangeProperty, Error=BadWindow 11/04/97 15:28:18 X Protocol Error Reply sent to Client #8, Request=MapWindow, Error=BadWindow 11/04/97 15:28:18 X Protocol Error Reply sent to Client #8, Request=GetWindowAttributes, Error=BadWindow 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:18 X Protocol Error Reply sent to Client #9, Request=QueryFont, Error=BadFont 11/04/97 15:28:23 X Protocol Error Reply sent to Client #8, Request=SetInputFocus, Error=BadWindow 11/04/97 15:28:25 X Protocol Error Reply sent to Client #8, Request=ChangeSaveSet, Error=BadWindow I've also tried to look at UNIX logs and I've found this that might be related (it seems to appear when CDE freezes): Apr 11 15:29:45 corse syslog: libtt[4932]: ttdt_Xt_input_handler(): tttk_message _receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_op en() has not been called yet. If this code is returned from tt_open() it means t tsession could not be started, which generally means ToolTalk is not installed o n this system. Of course CDE works just fine from the UNIX system console. Any advice welcome Vincent
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3265.1 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Tue Apr 15 1997 17:44 | 5 | |
See if you can determine if the problem is related to xdmcp.
I fixed xdmcp after ssb went out. For example, if you run cde without
using xdmcp, does it work better ?
/Eric
| |||||
| 3265.2 | nova05.vbo.dec.com::BERGER | Wed Apr 16 1997 04:23 | 15 | ||
Eric Thanks for the reply, but if I run without XDCMP I'm not gonna get the CDE front panel, am I ? I don't know what application to start to get it. At least the font problem (my 1/ in .0) doesn't occur without XDMCP. FWIW, I've also tried 3.0.564 (candidate for 7.0a I believe) and it's exactly the same. Right now, I'm running xdm instead of cde, and still XDMCP, and that combination is OK (except that I like cde :-(). Vincent PS: do you want a QAR ? | |||||
| 3265.3 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Wed Apr 16 1997 12:17 | 8 | |
I'm experimenting with 3.0.564 here and using xdmcp to our unix system,
and it seems to work o.k. Can you possibly email me a node, username,
and password for your unix so I can remotely try cde to your machine ?
Thanks.
/Eric
| |||||
| 3265.4 | Has this been fixed? | KERNEL::SHOULDING | Wed Apr 30 1997 13:03 | 10 | |
Hi, I have a customer with the same problem. Is there any update on this or should they just not use XDMCP with eXcursion? Many thanks Regards, Samantha Houlding Client/Server Support Group, CSC, UK | |||||
| 3265.5 | PEACHS::GHEFF | Do you feel like swimming? | Wed Apr 30 1997 13:45 | 3 | |
I don't know that anyone's been able to reproduce this problem.
#Gary
| |||||
| 3265.6 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Wed Apr 30 1997 16:58 | 10 | |
We experimented with this for awhile.
First, we found some setting in cde to make the font errors go away.
But the hang still happened.
The hang only happens on unix version 3 and not unix version 4. So
for some customers, a solution is to upgrade their unix to version 4.
/Eric
| |||||
| 3265.7 | PEACHS::GHEFF | Do you feel like swimming? | Wed Apr 30 1997 17:42 | 12 | |
Ach! I didn't notice it was Dux 3 we were talking about. CDE on 3.2*
is kind of kinky to begin with. I guess technically it shouldn't ball
up the eXcursion server, but running CDE on 3.2 probably isn't a good
idea in the first place. The ADK is not a supported configuration.
XDM is the recommended mode of operation on 3.2.
FWIW, I haven't had any real trouble with 4.0 and CDE beyond what is
mentioned in the eXcursion release notes. (Actually I lie, it should
probably be mentioned in the release notes that CDE behaves best if the
"Allow foreign window manager" checkbox is selected. So that dtwm can
do its thing.)
| |||||
| 3265.8 | Sun Solaris V2.5.1 | KERNEL::SHOULDING | Fri May 02 1997 06:16 | 103 | |
My customer is running Sun Solaris V2.5.1 and they are getting the following the errors. Is there a problem with this version? Do you have the details of what to change within the CDE Setup, to remove the font errors? The errors don't happen when XDMCP isn't used, but then they don't get the interface. They have the 'Allow foreign Window Manager' checkbox selected, but this hasn't made any difference. Regards, Sam 5/1/97 4:37:57 PM X Server Information eXcursion V3.0.554 (Intel)logging enabled. 5/1/97 4:38:02 PM X Server Error couldn't set fpe'/etc/dt/config/xfonts/C' 5/1/97 4:38:04 PM X Server Error couldn't set fpe'/usr/dt/config/xfonts/C' 5/1/97 4:38:04 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:04 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:04 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:05 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:13 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:13 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:13 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:13 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:13 PM X Protocol Error Reply sent to Client #3,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #8,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #7,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:15 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=MapWindow, Error=BadWindow 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=ChangeProperty, Error=BadWindow 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=MapWindow, Error=BadWindow 5/1/97 4:38:16 PM X Protocol Error Reply sent to Client #9,Request=GetWindowAttributes, Error=BadWindow 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:17 PM X Protocol Error Reply sent to Client #11,Request=QueryFont, Error=BadFont 5/1/97 4:38:18 PM X Protocol Error Reply sent to Client #9,Request=SetInputFocus, Error=BadWindow 5/1/97 4:38:32 PM X Server Information No host selected. | |||||
| 3265.9 | PEACHS::GHEFF | Do you feel like swimming? | Fri May 02 1997 09:51 | 19 | |
>My customer is running Sun Solaris V2.5.1 and they are getting the
>following the errors. Is there a problem with this version?
Digital's CDE implementation in Unix 4.0 plays fine with eXcursion 2.1
and 3.0.
>Do you have the details of what to change within the CDE Setup, to
>remove the font errors?
Have you implemented the procedure listed in the eXcursion release
notes for CDE fonts? That would be the place to start. At least that
might clean up the log file. You don't mention whether or not they're
really having any problems or if they are just concerned about the
error messages.
See http://tuvok.alf.dec.com/excursion/notes_en3.html if you don't have
the release notes handy.
#Gary
| |||||
| 3265.10 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Fri May 02 1997 15:31 | 5 | |
It was the author of .0 that did something in the "config" for cde
to prevent the font errors. You could ask him.
/Eric
| |||||