T.R | Title | User | Personal Name | Date | Lines |
---|
1867.1 | | MIPSBX::thomas | The Code Warrior | Fri Dec 08 1989 18:09 | 45 |
| ___________________________tm
! ! ! ! ! ! ! !
! d ! i ! g ! i ! t ! a ! l ! MEMORANDUM
!___!___!___!___!___!___!___!
Digital Internal Use Only
TO: CSCs DATE: 11-Nov-89
FROM: ULTRIX
CSSE/Support
LOC: ZKO3-3/X08
SUBJECT: X server problem with XPutImage on RISC platforms
PROBLEM STATEMENT: Calls to XPutImage cause the X server to dump core.
SOLUTION: The solution involves an addition to the /etc/ttys file. Change the
line that starts the X server to include the '-bs' option as follows.
Current X invocation:
:0 "/usr/bin/login -P /usr/bin/Xprompter -C /usr/bin/dxsession" none on
secure window="/usr/bin/Xmfb"
Change to look like this:
:0 "/usr/bin/login -P /usr/bin/Xprompter -C /usr/bin/dxsession" none on
secure window="/usr/bin/Xmfb -bs"
^^^
The difference is the '-bs' at the end of the line. If there is
a '-fd' option already there, then remove it.
A third party vendor named Parametics Tech found this problem.
Their customers are also going to need this 'fix' for their RISC
machines. If a caller identifies himself as a Parametic's customer,
and he is complaining of X server crashes, please explain the
addition of the '-bs' option to /etc/ttys. There may also be other
customers with the same problem.
ULTRIX CSSE Support Group
Digital Internal Use Only
|
1867.2 | How about on VAX Ultrix | DUGGAN::FALSAFI | Aram Falsafi, LDP Engineering | Mon Dec 11 1989 09:52 | 7 |
| On Friday, I was talking to a customer who had a problem with this same
routine, except that he is running VAX Ultirx. I looked at the
/etc/ttys file on a VAX Ultrix machine, but it didn't even have
that particular line! Any ideas?
Aram Falsafi
LDP Engineering
|
1867.3 | More detail ... | DUGGAN::FALSAFI | Aram Falsafi, LDP Engineering | Mon Dec 11 1989 11:12 | 12 |
| I forgot to mention that this is running on a VS 3520 (Firefox). I
suspect this is an improtant detail!
The application bombs because of a parameter mismatch (something about
scan depth vs. window depth).
Could this be a bug in the Firefox X server, or do they have a
parameter set wrong?
Thanks,
-Aram
|