RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Still no luck. I tried cygwin1-20030117.dll but it made no difference: $ ls -l /bin/cygwin1.dll -rw-r--r--1 U752359 mkgroup906568 Jan 17 09:03 /bin/cygwin1.dll $ gdb ./XWin-Test71-DEBUG-2.exe GNU gdb 2002-12-19-cvs (cygwin-special) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i686-pc-cygwin... (gdb) run -multiwindow Starting program: /cygdrive/d/downloads/XWin-Test71-DEBUG-2.exe -multiwindow Program received signal SIGSEGV, Segmentation fault. 0x77e8c40c in _libkernel32_a_iname () (gdb) where #0 0x77e8c40c in _libkernel32_a_iname () #1 0x0001 in ?? () #2 0x6103f41f in _libkernel32_a_iname () #3 0x6103f44b in _libkernel32_a_iname () #4 0x6107bfbf in _libkernel32_a_iname () #5 0x6107c29a in _libkernel32_a_iname () #6 0x0044b94a in trans_mkdir (path=0x448c97 /tmp/.X11-unix, mode=1023) at ../../../lib/xtrans/Xtransutil.c:495 #7 0x00448e17 in _XSERVTransSocketUNIXCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtranssock.c:932 #8 0x0044a591 in _XSERVTransCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtrans.c:734 #9 0x0044ac78 in _XSERVTransMakeAllCOTSServerListeners (port=0x22fd20 0, partial=0x22fd48, count_ret=0x83d440, ciptrs_ret=0x7e2550) at ../../../lib/xtrans/Xtrans.c:1029 #10 0x0043ed3c in CreateWellKnownSockets () at connection.c:342 #11 0x0040153c in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:327 #12 0x61007438 in _libkernel32_a_iname () #13 0x6100771d in _libkernel32_a_iname () #14 0x007df252 in cygwin_crt0 () #15 0x0040103c in mainCRTStartup () #16 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610876e1 in _libkernel32_a_iname () #5 0x61089eb5 in _libkernel32_a_iname () #6 0x00457ec4 in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610896a1 in _libkernel32_a_iname () #5 0x61089768 in _libkernel32_a_iname () #6 0x00457eef in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3, pm=4294967295, bpp=24, reverse=0, upsidedown=0) at fbblt.c:174 174 fbblt.c: No such file or directory. in fbblt.c (gdb) where #0 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3, pm=4294967295, bpp=24, reverse=0, upsidedown=0) at fbblt.c:174 #1 0x0047ee96 in fbOddTile (dst=0x1b8, dstStride=1152, dstX=0, width=27648, height=208, tile=0x102c4468, tileStride=3, tileWidth=96, tileHeight=4, alu=3, pm=4294967295, bpp=24, xRot=0, yRot=0) at fbtile.c:149 #2 0x0047ef90 in fbTile (dst=0x1b8, dstStride=1152, dstX=0, width=27648, height=836, tile=0x102c4468, tileStride=3, tileWidth=96, tileHeight=4, alu=3, pm=4294967295, bpp=24, xRot=0, yRot=0) at fbtile.c:197 #3 0x00479763 in fbFillRegionTiled (pDrawable=0x1010b0b8, pRegion=0x22fce0, pTile=0x102c4428) at fbwindow.c:268 #4 0x0047981c in fbPaintWindow (pWin=0x1010b0b8, pRegion=0x22fce0, what=0) at fbwindow.c:304 #5 0x004bbe41 in miSpritePaintWindowBackground
Re: multiwindow problem with kterm
From: Sylvain Petreolle [EMAIL PROTECTED] Date: Fri, 17 Jan 2003 01:36:54 +0100 (CET) ::If I remember correct, when the dcop server isnt loaded it is started ::automatically when you call a kde application. :: ::Could the kde window manager be loaded the same way ? Well, kterm is not a KDE application. It's just a Japanese capable xterm. ;-) Thanks for the info anyway. BTW, I've tried the newest TestServer-72, but made no difference. I could send the kterm binary and/or source code that I'm using, if anybody wants try it out. # May be, I should contact Kensuke-san directly, so that I could # help him debug the problem, in Japanese. :-) Thank you, Haro :: --- [EMAIL PROTECTED] a écrit : Hello Harold, :: :: Yes, I'm quite certain that I have commented out 'twm' from my :: startxwin.bat script. :: Xterm seems to run just fine, so I think this is something to with :: kterm or the multiwindow mode. =--- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Kubota Graphics Technology Inc. /|\ |_| |_|_| 2-8-8 Shinjuku, Shinjuku-ku Tokyo 160-0022, Japan Tel: +81-3-3225-0931 Fax: +81-3-3225-0930 Email: [EMAIL PROTECTED]
Re: multiwindow problem with kterm
[EMAIL PROTECTED] wrote: From: Sylvain Petreolle [EMAIL PROTECTED] Date: Fri, 17 Jan 2003 01:36:54 +0100 (CET) ::If I remember correct, when the dcop server isnt loaded it is started ::automatically when you call a kde application. :: ::Could the kde window manager be loaded the same way ? Well, kterm is not a KDE application. It's just a Japanese capable xterm. ;-) Thanks for the info anyway. For future reference, no, KDE apps won't load the kde window manager, I can run the whole of KDE under cygwin with the multiwindow manager instead. David
Use XFree86 on W98 to connect to AIX (WAS: Use XFree86 on W98 to connect to Linux)
If I try the ssh method to connect to an AIX machine (instead of a Linux box), everything seems to work fine, I even can open an xterm to display on my local XFree86 window. Unfortunately, none of the remote X applications does accept any keyboard input. Any help or hint is very much appreciated Bjoern Wolf Harold L Hunt II wrote: Frank, You can use XDMCP for a remote session: http://xfree86.cygwin.com/docs/ug/using-remote-session.html Or, you can launch individual clients with SSH (or you can even start a remote window manager which makes this very similar to XDMCP, including KDE... by using, for example, startkde): http://xfree86.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh I hope that helps, Harold fchi wrote: Is it possible to run XFree86 on W98 under Cygwin to connect to a Linux in X11 sessions? We are very interested in setting up a lab where various Linux boxes are clusted and the personal workstations (for various reasons) are MS W98 or Windows XP. Any insight that you can provide will be appreciated. Frank Chi
xwinclip copy pasting from Xwin/Sun dtterm to Windows XP
Hi, I use my Cygwin mainly for connecting to various UNIX hosts throught the company ,and export terminals and other apps back to my local Cygwin/Windows XP display. Anyway, the reason for this post is to make others aware, as I have not seen it mentioned in the archives, - so forgive me if it's there and I missed it - that in order to copy and paste text from an exported SUN dtterm back into Windows (notepad or something), you have to select the dtterm text, CTRL-Insert (copy) within the dtterm, then SELECT some other text from a regular cygwin xterm to push the dtterm text into the clipboard, then you can paste into Windows. If you don't selct the subsequent text from a Cygwin xterm, the dtterm never gets pushed intot he clipboard and you can't past your dtterm text into Windows. You can, however, copy and paste by merely selecting and middle clicking anywhere in Xwindows, or from xterm to windows, just not from dtterm to windows without using the above method. I've tried this numerous times, with the latest xwinclip installed, and using Blackbox as my Window Manager. The other thing that won't work within dtterm is if you open a file in vi the SHIFT special characters, like #, won't work. I get a beep. Anyone know how to fix that one? Regards, -- Tom Connelly
Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
It looks like this is dying in a DLL somewhere. 'info dll' should help tell what the 0x100f8628 address is related to. However, it would certainly help if you built debugging versions of the X DLLs so that symbol info would be available. It doesn't seem to be dying in the cygwin DLL, that much is relatively clear. cgf On Fri, Jan 17, 2003 at 09:24:59AM +, J S wrote: Still no luck. I tried cygwin1-20030117.dll but it made no difference: $ ls -l /bin/cygwin1.dll -rw-r--r--1 U752359 mkgroup906568 Jan 17 09:03 /bin/cygwin1.dll $ gdb ./XWin-Test71-DEBUG-2.exe GNU gdb 2002-12-19-cvs (cygwin-special) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i686-pc-cygwin... (gdb) run -multiwindow Starting program: /cygdrive/d/downloads/XWin-Test71-DEBUG-2.exe -multiwindow Program received signal SIGSEGV, Segmentation fault. 0x77e8c40c in _libkernel32_a_iname () (gdb) where #0 0x77e8c40c in _libkernel32_a_iname () #1 0x0001 in ?? () #2 0x6103f41f in _libkernel32_a_iname () #3 0x6103f44b in _libkernel32_a_iname () #4 0x6107bfbf in _libkernel32_a_iname () #5 0x6107c29a in _libkernel32_a_iname () #6 0x0044b94a in trans_mkdir (path=0x448c97 /tmp/.X11-unix, mode=1023) at ../../../lib/xtrans/Xtransutil.c:495 #7 0x00448e17 in _XSERVTransSocketUNIXCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtranssock.c:932 #8 0x0044a591 in _XSERVTransCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtrans.c:734 #9 0x0044ac78 in _XSERVTransMakeAllCOTSServerListeners (port=0x22fd20 0, partial=0x22fd48, count_ret=0x83d440, ciptrs_ret=0x7e2550) at ../../../lib/xtrans/Xtrans.c:1029 #10 0x0043ed3c in CreateWellKnownSockets () at connection.c:342 #11 0x0040153c in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:327 #12 0x61007438 in _libkernel32_a_iname () #13 0x6100771d in _libkernel32_a_iname () #14 0x007df252 in cygwin_crt0 () #15 0x0040103c in mainCRTStartup () #16 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610876e1 in _libkernel32_a_iname () #5 0x61089eb5 in _libkernel32_a_iname () #6 0x00457ec4 in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610896a1 in _libkernel32_a_iname () #5 0x61089768 in _libkernel32_a_iname () #6 0x00457eef in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3, pm=4294967295, bpp=24, reverse=0, upsidedown=0) at fbblt.c:174 174 fbblt.c: No such file or directory. in fbblt.c (gdb) where #0 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3, pm=4294967295, bpp=24, reverse=0, upsidedown=0) at fbblt.c:174 #1 0x0047ee96 in fbOddTile (dst=0x1b8, dstStride=1152, dstX=0, width=27648, height=208, tile=0x102c4468, tileStride=3, tileWidth=96, tileHeight=4, alu=3, pm=4294967295, bpp=24, xRot=0, yRot=0) at fbtile.c:149 #2 0x0047ef90 in fbTile (dst=0x1b8, dstStride=1152, dstX=0, width=27648, height=836, tile
Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Christopher Faylor wrote: It looks like this is dying in a DLL somewhere. 'info dll' should help tell what the 0x100f8628 address is related to. However, it would certainly help if you built debugging versions of the X DLLs so that symbol info would be available. It doesn't seem to be dying in the cygwin DLL, that much is relatively clear. The Xserver does not use any X11 dlls. Only cygz.dll. Is where the same as backtrace (bt). The last stackframe looks perfect for debugging. The others have nearly no line information. bye ago NP: Apoptygma Berzerk - Near [Banilla Dream version] -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
JS, I know what I want you to do: Run XWin.exe without gdb, and send in the last few lines of XWinrl.log. I need to know if the last message in that log is ``calling pthread...'' or something else entirely. By continuing with c in gdb you are kinda throwing us off the trail, because we don't know exactly how far XWin.exe is getting before it runs into problems. Harold Christopher Faylor wrote: It looks like this is dying in a DLL somewhere. 'info dll' should help tell what the 0x100f8628 address is related to. However, it would certainly help if you built debugging versions of the X DLLs so that symbol info would be available. It doesn't seem to be dying in the cygwin DLL, that much is relatively clear. cgf On Fri, Jan 17, 2003 at 09:24:59AM +, J S wrote: Still no luck. I tried cygwin1-20030117.dll but it made no difference: $ ls -l /bin/cygwin1.dll -rw-r--r--1 U752359 mkgroup906568 Jan 17 09:03 /bin/cygwin1.dll $ gdb ./XWin-Test71-DEBUG-2.exe GNU gdb 2002-12-19-cvs (cygwin-special) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i686-pc-cygwin... (gdb) run -multiwindow Starting program: /cygdrive/d/downloads/XWin-Test71-DEBUG-2.exe -multiwindow Program received signal SIGSEGV, Segmentation fault. 0x77e8c40c in _libkernel32_a_iname () (gdb) where #0 0x77e8c40c in _libkernel32_a_iname () #1 0x0001 in ?? () #2 0x6103f41f in _libkernel32_a_iname () #3 0x6103f44b in _libkernel32_a_iname () #4 0x6107bfbf in _libkernel32_a_iname () #5 0x6107c29a in _libkernel32_a_iname () #6 0x0044b94a in trans_mkdir (path=0x448c97 /tmp/.X11-unix, mode=1023) at ../../../lib/xtrans/Xtransutil.c:495 #7 0x00448e17 in _XSERVTransSocketUNIXCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtranssock.c:932 #8 0x0044a591 in _XSERVTransCreateListener (ciptr=0x100f2338, port=0x22fd20 0) at ../../../lib/xtrans/Xtrans.c:734 #9 0x0044ac78 in _XSERVTransMakeAllCOTSServerListeners (port=0x22fd20 0, partial=0x22fd48, count_ret=0x83d440, ciptrs_ret=0x7e2550) at ../../../lib/xtrans/Xtrans.c:1029 #10 0x0043ed3c in CreateWellKnownSockets () at connection.c:342 #11 0x0040153c in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:327 #12 0x61007438 in _libkernel32_a_iname () #13 0x6100771d in _libkernel32_a_iname () #14 0x007df252 in cygwin_crt0 () #15 0x0040103c in mainCRTStartup () #16 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610876e1 in _libkernel32_a_iname () #5 0x61089eb5 in _libkernel32_a_iname () #6 0x00457ec4 in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x77e83ab6 in _libkernel32_a_iname () (gdb) where #0 0x77e83ab6 in _libkernel32_a_iname () #1 0x100f8628 in ?? () #2 0x6108861d in _libkernel32_a_iname () #3 0x61088698 in _libkernel32_a_iname () #4 0x610896a1 in _libkernel32_a_iname () #5 0x61089768 in _libkernel32_a_iname () #6 0x00457eef in InitQueue () #7 0x004584d5 in winInitWM () #8 0x00452a97 in winFinishScreenInitFB () #9 0x0045228d in winScreenInit () #10 0x00402389 in AddScreen (pfnInit=0x4520d0 winScreenInit, argc=2, argv=0x100f1888) at main.c:768 #11 0x0044fe9a in InitOutput () #12 0x00401719 in main (argc=2, argv=0x100f1888, envp=0x100f0328) at main.c:380 #13 0x61007438 in _libkernel32_a_iname () #14 0x6100771d in _libkernel32_a_iname () #15 0x007df252 in cygwin_crt0 () #16 0x0040103c in mainCRTStartup () #17 0x77e992a6 in _libkernel32_a_iname () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3, pm=4294967295, bpp=24, reverse=0, upsidedown=0) at fbblt.c:174 174 fbblt.c: No such file or directory. in fbblt.c (gdb) where #0 0x00475b8a in fbBlt (srcLine=0x102c4498, srcStride=3, srcX=0, dstLine=0x1e431fc, dstStride=1152, dstX=0, width=96, height=0, alu=3
Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
On Fri, 17 Jan 2003, Harold L Hunt II wrote: JS, I know what I want you to do: Run XWin.exe without gdb, and send in the last few lines of XWinrl.log. I need to know if the last message in that log is ``calling pthread...'' or something else entirely. By continuing with c in gdb you are kinda throwing us off the trail, because we don't know exactly how far XWin.exe is getting before it runs into problems. I do not know if I have the same problem as JS, but I experiece the same symptom, a crash after a few seconds. The last lines of XWinrl.log on my machine looks like below. I run build: 2003-01-17 - Test72 Regards, /Erik winQueryRGBBitsAndMasks - GetDeviceCaps (BITSPIXEL) returned 24 for the screen. Using default 24bpp masks. winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 24 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winScreenInit - returning (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (n ull) winInitMultiWindowWM - DISPLAY=:0.0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
I am beginning to think that the DISPLAY=:0.0 has something to do with these crashes. If I recall correctly, specifying a display name such as :0.0 means that you should connect using UNIX domain sockets, which are emulated in Cygwin using TCP/IP sockets. We should change XWin.exe to connect to DISPLAY=127.0.0.1:0.0 and see what happens. You know... there may be an exit (1) being called in the multi-window window-manager portions of the code that does not have an error message being printed out before exit is called. I will take a peek at the code. I suspect that the window manager is unable to connect, so it bails. Erik --- will you be available to test a DEBUG build in the next few minutes? Harold Erik Frisk wrote: On Fri, 17 Jan 2003, Harold L Hunt II wrote: JS, I know what I want you to do: Run XWin.exe without gdb, and send in the last few lines of XWinrl.log. I need to know if the last message in that log is ``calling pthread...'' or something else entirely. By continuing with c in gdb you are kinda throwing us off the trail, because we don't know exactly how far XWin.exe is getting before it runs into problems. I do not know if I have the same problem as JS, but I experiece the same symptom, a crash after a few seconds. The last lines of XWinrl.log on my machine looks like below. I run build: 2003-01-17 - Test72 Regards, /Erik winQueryRGBBitsAndMasks - GetDeviceCaps (BITSPIXEL) returned 24 for the screen. Using default 24bpp masks. winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 24 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winScreenInit - returning (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (n ull) winInitMultiWindowWM - DISPLAY=:0.0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Okay, there is a new DEBUG build that connects to DISPLAY=127.0.0.1:0.0, instead of :0.0, and I added the messages back into the XOpenDisplay loop that print out if a connection attempt is failed. However, I do not think that the connection attempt will fail anymore. If some one can test this within 5 minutes, then I can make a release before I leave town for the weekend. Otherwise, I might not get to make a new release until Sunday or Monday. Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold L Hunt II Sent: Friday, January 17, 2003 4:44 PM To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD] I am beginning to think that the DISPLAY=:0.0 has something to do with these crashes. If I recall correctly, specifying a display name such as :0.0 means that you should connect using UNIX domain sockets, which are emulated in Cygwin using TCP/IP sockets. We should change XWin.exe to connect to DISPLAY=127.0.0.1:0.0 and see what happens. You know... there may be an exit (1) being called in the multi-window window-manager portions of the code that does not have an error message being printed out before exit is called. I will take a peek at the code. I suspect that the window manager is unable to connect, so it bails. Erik --- will you be available to test a DEBUG build in the next few minutes? Harold Erik Frisk wrote: On Fri, 17 Jan 2003, Harold L Hunt II wrote: JS, I know what I want you to do: Run XWin.exe without gdb, and send in the last few lines of XWinrl.log. I need to know if the last message in that log is ``calling pthread...'' or something else entirely. By continuing with c in gdb you are kinda throwing us off the trail, because we don't know exactly how far XWin.exe is getting before it runs into problems. I do not know if I have the same problem as JS, but I experiece the same symptom, a crash after a few seconds. The last lines of XWinrl.log on my machine looks like below. I run build: 2003-01-17 - Test72 Regards, /Erik winQueryRGBBitsAndMasks - GetDeviceCaps (BITSPIXEL) returned 24 for the screen. Using default 24bpp masks. winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 24 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winScreenInit - returning (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (n ull) winInitMultiWindowWM - DISPLAY=:0.0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Of course, pointing to the new debug build would help: http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test72-DEBUG.exe.bz2 Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold L Hunt II Sent: Friday, January 17, 2003 4:44 PM To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD] I am beginning to think that the DISPLAY=:0.0 has something to do with these crashes. If I recall correctly, specifying a display name such as :0.0 means that you should connect using UNIX domain sockets, which are emulated in Cygwin using TCP/IP sockets. We should change XWin.exe to connect to DISPLAY=127.0.0.1:0.0 and see what happens. You know... there may be an exit (1) being called in the multi-window window-manager portions of the code that does not have an error message being printed out before exit is called. I will take a peek at the code. I suspect that the window manager is unable to connect, so it bails. Erik --- will you be available to test a DEBUG build in the next few minutes? Harold Erik Frisk wrote: On Fri, 17 Jan 2003, Harold L Hunt II wrote: JS, I know what I want you to do: Run XWin.exe without gdb, and send in the last few lines of XWinrl.log. I need to know if the last message in that log is ``calling pthread...'' or something else entirely. By continuing with c in gdb you are kinda throwing us off the trail, because we don't know exactly how far XWin.exe is getting before it runs into problems. I do not know if I have the same problem as JS, but I experiece the same symptom, a crash after a few seconds. The last lines of XWinrl.log on my machine looks like below. I run build: 2003-01-17 - Test72 Regards, /Erik winQueryRGBBitsAndMasks - GetDeviceCaps (BITSPIXEL) returned 24 for the screen. Using default 24bpp masks. winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 24 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winScreenInit - returning (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (n ull) winInitMultiWindowWM - DISPLAY=:0.0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
Multiwindow mode authorization bug
Geert, Multiwindow mode connects X server as X client. So XDMCP does'nt work. Kensuke Matsuzaki
xwinclip not working? or nor running?
Hi, I have just installed xwinclip on a Window 95 PC according to the instructions on the xwinclip web page. The xwinclip.exe is dated 29 December 2002, thus I assume that it is Test07. It was on my system as the result of an install of Cygwin that was downloaded about a week ago -- I guess Test08 was not in that. I start Cygwin and it seems to take longer to start, but does not give any error messages. I am trying to use xwinclip to copy/paste between Mozilla 1.2 running on a Red Hat 8 server -- Linux/Mozilla is running through the Cygwin XFree86 stuff that is running on this PC. When I try to copy/paste in either direction, I get nothing; nothing happens. No errors, no crashes, just nothing. My primary need is to copy URLs to/from IE 5.x and Linux Mozilla 1.2. Between Window 95 programs, copy/paste works fine. Between Mozilla windows copy/paste works fine. Between other linux windows and Mozilla, copy/paste does _not_ work. ?? How do determine if the xwinclip is even running? ?? How should I further test to try to determine the source of the problem? Jay
Re: xwinclip not working? or nor running?
?? How do determine if the xwinclip is even running? ps should retun something like this : 2188 12052 2188 con 18317 05:15:39 /usr/X11R6/bin/xwinclip if it isnt running, check if you put it in the startxwin.bat or $HOME/.xinitrc. ?? How should I further test to try to determine the source of the problem? = Sylvain Petreolle [EMAIL PROTECTED] Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 Don't think you are. Know you are. Morpheus, in Matrix. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
