.
SYBYL usually opens two windows, a main window and a (graphical)
terminal. When the first (main) window pops up, XWin crashes with the
following error:
Fatal server error
...
Package version: 1.12.1-1 built 2012-05-02
...
X was called with: X :0 -multiwindow
An full Cygwin
pinpoint the exact time when it stopped
working.
SYBYL usually opens two windows, a main window and a (graphical)
terminal. When the first (main) window pops up, XWin crashes with the
following error:
Fatal server error
...
Package version: 1.12.1-1 built 2012-05-02
...
X
not set cooperative level:
88760245
[ 1601.771] winFinishScreenInitFB - Could not allocate framebuffer
[ 1601.771] winScreenInit - winFinishScreenInit () failed
[ 1601.771] Fatal server error: InitOutput - Couldn't add screen 1
Error 88760245 is DDERR_EXCLUSIVEMODEALREADYSET
cooperative level:
88760245
[ 1601.771] winFinishScreenInitFB - Could not allocate framebuffer
[ 1601.771] winScreenInit - winFinishScreenInit () failed
[ 1601.771] Fatal server error: InitOutput - Couldn't add screen 1
Error 88760245 is DDERR_EXCLUSIVEMODEALREADYSET
At the moment, XWin always
Hi,
When I give the -fullscreen argument to XWin using two screens, a
window pops up with the error
InitOutput - Couldn't add screen 1
and
Aborted (core dumped)
is printed in the bash shell.
The following command lines work perfectly:
XWin -fullscreen -screen 0 @2 -query 10.3.22.73
XWin
Synopsis: if you encounter the fatal server error due to fixed font,
and have tried FAQ 8.4 to no avail, switching the end-of-lines to UNIX
may solve the problem:
After following the Cygwin/X installation instruction, running startx
ended with this message, which others have reported
server error:
InitOutput - Duplicate invocation on display number: 0. Exiting.
winDeinitMultiWindowWM - Noting shutdown in progress
on display 0
Fatal server error:
InitOutput - Duplicate invocation on display number: 0. Exiting.
winDeinitMultiWindowWM - Noting shutdown in progress
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#errors
I got a Fatal server error after running startx.
Does anyone know what I need to do next to fix this error and get X server
running?
The /tmp/Xwin.log file is shown below:
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens
On Mon, 14 Feb 2005, Blake Owen wrote:
I got a Fatal server error after running startx.
Does anyone know what I need to do next to fix this error and get X server
running?
The /tmp/Xwin.log file is shown below:
The logfile seems clean. Maybe it is from an old session and Xwin can't
On Sun, Apr 14, 2002 at 07:19:37PM -0400, Warren Postma wrote:
The FAQ listing for section 6.5. Fatal server error: could not open default
font 'fixed'
does not work. For one thing, the suggested remedy does NOT change the
mounting of the /usr directory.
A more direct fix would be to update
11 matches
Mail list logo