Wmaker, massive handle leak with Xorg
The window manager Windowmaker has a massive handle leak, loosing about 50 handles per second, until the Windows kernel runs out of buffer memory (after 12 hours or so, then everything fails, socket api functions etc.) I think this is the same problem Volker Zell reported at January 11. I just updated my cygwin, so the problem is still present in the current software. I simply changed in startxwin.sh XWin -multiwindow -clipboard -silent-dup-error ... to XWin -clipboard -silent-dup-error sleep 2 wmaker sleep 2 ... With fvwm or twm i have no problems. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: WMaker compile
Pascal A Dupuis writes: On Mon, Jan 12, 2009 at 05:27:07PM +0100, Dr. Volker Zell wrote: Can you please check if your version also leaks handles ? o http://cygwin.com/ml/cygwin-xfree/2009-01/msg00048.html Sorry, but how can I detect handle leakage ? With Windows Task Manager for example. You have to include the Handles column in the output with View Select Columns Checkbox on Handle Count Ciao Volker -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: WMaker compile
On Mon, Jan 12, 2009 at 05:27:07PM +0100, Dr. Volker Zell wrote: Can you please check if your version also leaks handles ? o http://cygwin.com/ml/cygwin-xfree/2009-01/msg00048.html Sorry, but how can I detect handle leakage ? Maybe this is not related, or maybe it is: - if I launch cygwin and and only use CLi programs, typing 'logout' ensure the window gets closed and disappear; - OTOH, launching 'startx', which starts the X environment and WMaker, then using WMaker 'exit' functions, leaves a window which does never get closed. Regards Pascal -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
WMaker compile
Hello, let first start by introducing myself: I'm a long time linux user, and tired of rebooting the home machine because childrens can't play Zoo Tycon under linux. I've just fiddled a bit with WindowMaker, and finally compiled the latest version, 0.92. It ran out of the box, configured as CC=gcc-4 CPP=cpp-4 CXX=g++-4 ../configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/sbin --localstatedir=/var --datadir=/usr/share --mandir=/usr/share/man --infodir=/usr/share/info --with-gnustepdir=/usr/lib/GNUstep/System Two explanations: 1) the path reflect the way there are setup in the corresponding debian package 2) I compiled it under gcc-4 In order to make it run: 1) create a ~/.xserverrc file with export CYGWIN=server exec X :0 This ensures the X server starts with the MIT-SHM ewtension enabled, run 'cygserver-config' once to have the required service enabled under Windows 2) launch wmaker at the end of .xinitrc as exec env CYGWIN=server LANG=fr_BE.UTF-8 wmaker This ensures that wmaker can access shared memory from the client side So ... it works. I used it with Belgian french locales. I would like to share the new wmaker package. To this end I tried to install it locally as make PREFIX=/usr/src/WindowMaker-0.92.0/package/ install but the package ended up being installed under /usr Could someone tell me how to generate a package under cygwin ? Where should I sent it to have it included in the cygwin distribution ? Which compiler should I use ? gcc-3 ? MingGW ? gcc-4 ? Regards Pascal Dupuis -- A conservative is a man who believes that nothing should be done for the first time. -- Alfred E. Wiggam -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Wmaker 0.92 Install Error
Greetings Everyone, I seem to have encountered the undefined reference to Xsetlocale issue while trying to upgrade to Wmaker 0.92. I read though all of the past emails on this issue but no one seemed to have a clear answer as to how to solve this problem. Thanks in advance. Dustin Making all in Resources make[2]: Entering directory `/usr/X11R6/share/WindowMaker-0.92.0/WINGs/Resources' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/X11R6/share/WindowMaker-0.92.0/WINGs/Resources' Making all in Examples make[2]: Entering directory `/usr/X11R6/share/WindowMaker-0.92.0/WINGs/Examples' /bin/sh ../../libtool --mode=link gcc -g -O2 -lX11 -o connect.exe connect.o ../../WINGs/libWUtil.a -L/usr/local/lib -L/usr/X11R6/lib gcc -g -O2 -o connect.exe connect.o -lX11 ../../WINGs/libWUtil.a -L/usr/local/lib -L/usr/X11R6/lib ../../WINGs/libWUtil.a(wapplication.o): In function `WMInitializeApplication': /usr/X11R6/share/WindowMaker-0.92.0/WINGs/wapplication.c:38: undefined reference to `__Xsetlocale' collect2: ld returned 1 exit status make[2]: *** [connect.exe] Error 1 make[2]: Leaving directory `/usr/X11R6/share/WindowMaker-0.92.0/WINGs/Examples' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/X11R6/share/WindowMaker-0.92.0/WINGs' make: *** [all-recursive] Error 1 [EMAIL PROTECTED] /usr/X11R6/share/WindowMaker-0.92.0 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
i can't start wmaker on cygwin
Hello, I use startx to have an X session. Then when i try to start wmaker i have the following errors : wmaker fatal error: it seems that there is already a window manager running waiting for X server to shut down winClipboardProc - Call to select () failed: -1. Bailing. winClipboardProc - XDestroyWindow succeeded Thank you for your response Cédric -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: i can't start wmaker on cygwin
Cédric Bouttes wrote: Hello, I use startx to have an X session. Then when i try to start wmaker i have the following errors : wmaker fatal error: it seems that there is already a window manager running waiting for X server to shut down winClipboardProc - Call to select () failed: -1. Bailing. winClipboardProc - XDestroyWindow succeeded Start by reading the user's guide, this section specially: http://x.cygwin.com/docs/ug/using-window-managers.html You are using startx, which uses multiwindow mode, if you want to use another window manager you should change the start script. -- René Berber -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
i can't start {twm,wmaker} on cygwin
On Tue, 9 May 2006, Cédric Bouttes wrote: Hello, I use startx to have an X session. Then when i try to start twm instead of xterm i have the following errors : $ twm: another window manager is already running on screen 0? twm: unable to find any unmanaged screens What can i do ? On Tue, 9 May 2006, Cédric Bouttes wrote: Hello, I use startx to have an X session. Then when i try to start wmaker i have the following errors : wmaker fatal error: it seems that there is already a window manager running waiting for X server to shut down winClipboardProc - Call to select () failed: -1. Bailing. winClipboardProc - XDestroyWindow succeeded In both cases, by default XWin starts in multiwindow mode, which basically means that XWin has a built-in window manager that wraps the Windows default window manager. If you are content with the multiwindow mode, just don't start any window manager. If you would rather use twm or windowmaker, remove the -multiwindow parameter from the XWin invocation (and you might wish to add -rootless if you want the windows to be listed among the regular Windows ones). HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Problem with the cygwin(perhaps the problem with wmaker,not sure)
hi everyone, I have got a problem. I really tried my best to solve it, but... The fact is that, a month ago, they have installed a cygwin for my system, and it worked well. Yesterday, I have tried to install a cygwin from internet. I installed it in another directory. The result is that, it does not work now, the cygwin. Before posting this message, I have tried: deleting the trace in the Windows registry,so it works better now. But it always can not display the fenetre xterm. the XWinlog file is as below: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.63 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -clipboard -multiplemonitors -rootless ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1024 dwHeight: 768 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winGetWorkArea - Original WorkArea: 0 0 738 1024 winGetWorkArea - Virtual screen is 1024 x 768 winGetWorkArea - Virtual screen origin is 0, 0 winGetWorkArea - Primary screen is 1024 x 768 winGetWorkArea - Adjusted WorkArea for multiple monitors: 0 0 738 1024 winAdjustForAutoHide - Original WorkArea: 0 0 738 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 0 738 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 738 r 1024 l 0 b 738 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 4096 winAllocateFBShadowDDNL - Created shadow pitch: 4096 winAllocateFBShadowDDNL - Created shadow stride: 1024 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 4 Rules = xfree86 Model = pc105 Layout = fr Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 512 384 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. ddxBeforeReset - Hello winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. ddxBeforeReset - Clipboard thread has exited. Thanks a lot for your help. Looking forward for replies. smiling_apple :) _ MSN Explorer: http://explorer.msn.com/lccn
Re: Problem with the cygwin(perhaps the problem with wmaker,not sure)
On Tue, 15 Feb 2005, ZHANG ming wrote: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.63 Try installing the xorg-x11 packages. The xfree 4.3.0 server is very old. I'm quite surprised it is still available on some mirrors. Maybe your mirror is outdated. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Some problem with wmaker
Hi, I got this problem on a fresh install of cygwin while starting wmaker : Xlib: extension MIT-SHM missing on display localhost:0.0 Any idea? Thanks in advance -- Franck http://fky.clacbec.net
Re: Some problem with wmaker
On Mon, 31 Jan 2005, fky wrote: Hi, I got this problem on a fresh install of cygwin while starting wmaker : Xlib: extension MIT-SHM missing on display localhost:0.0 Any idea? You'll have to setup the shared memory services for cygwin http://x.cygwin.com/docs/ug/using-shared-memory.html bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: WMaker 0.90 broken?
On Mon, 15 Nov 2004, Mark Paulus wrote: Xlib: extension MIT-SHM missing on display :0.0. Does window maker require SHM? Maybe you should consider running cygserver for shared memory support. wmaker warning: could not load font: helvetica:slant=0:weight=100:pixelsize=12. wmaker warning: could not load font: helvetica:xlfd=-*-helvetica-bold-r-normal-* -12-*-*-*-*-*-*-*:slant=0:weight=200:pixelsize=12. wmaker warning: could not load any fonts. Make sure your font installation and l ocale settings are correct. The font should be installed with the xorg-x11-fnts packages. Please verify that the font is available: $ xlsfonts -fn -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-* should print about 30 entries. If it does not then do $ rm /usr/X11R6/lib/X11/fonts/75dpi/fonts.dir $ font-update wmaker fatal error: could not initialize WINGs widget set wmaker fatal error: it seems that there is already a window manager running This does not seem to be related to the font issue. Are you sure there is no other window manager running? bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: WMaker 0.90 broken?
Well, it does seem to be a font issue. I used setup, and did a re-install of a couple of x11 font packages and everthing seems to be working just fine. On a side note, ipc-daemon2 does not seem to provide whatever is needed by MIT-SHM, as I get that message, whether I have ipc-daemon2 started or not. I also think it's not a goodness that using setup to handle an upgrade breaks the fonts package(s) and causes system failures But then, that's just my opinion, and as we all know, opinion are like rear-ends Everyone has one, and they are usually all full of .. On Tue, 16 Nov 2004 09:59:01 +0100 (MET), Alexander Gottwald wrote: On Mon, 15 Nov 2004, Mark Paulus wrote: Xlib: extension MIT-SHM missing on display :0.0. Does window maker require SHM? Maybe you should consider running cygserver for shared memory support. wmaker warning: could not load font: helvetica:slant=0:weight=100:pixelsize=12. wmaker warning: could not load font: helvetica:xlfd=-*-helvetica-bold-r-normal-* -12-*-*-*-*-*-*-*:slant=0:weight=200:pixelsize=12. wmaker warning: could not load any fonts. Make sure your font installation and l ocale settings are correct. The font should be installed with the xorg-x11-fnts packages. Please verify that the font is available: $ xlsfonts -fn -*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-* should print about 30 entries. If it does not then do $ rm /usr/X11R6/lib/X11/fonts/75dpi/fonts.dir $ font-update wmaker fatal error: could not initialize WINGs widget set wmaker fatal error: it seems that there is already a window manager running This does not seem to be related to the font issue. Are you sure there is no other window manager running? bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: WMaker 0.90 broken?
On Tue, 16 Nov 2004, Mark Paulus wrote: Well, it does seem to be a font issue. I used setup, and did a re-install of a couple of x11 font packages and everthing seems to be working just fine. On a side note, ipc-daemon2 does not seem to provide whatever is needed by MIT-SHM, as I get that message, whether I have ipc-daemon2 started or not. You have to setup cygserver. cygserver-config might help. And adding the server keyword to the CYGWIN environment variable. eg CYGWIN=server XWin.exe $OPTIONS @all: Is there documentation available on this? I also think it's not a goodness that using setup to handle an upgrade breaks the fonts package(s) and causes system failures But then, that's just my opinion, and as we all know, opinion are like rear-ends Everyone has one, and they are usually all full of .. It should not. But such things are sometimes hard to reproduce and hard to identify. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
WMaker 0.90 broken?
I just did an cygwin upgrade, hoping to get the latest cygwin1.dll. Got a whole bunch more than that, including wmaker 0.90. However, after doing the upgrade, wmaker seems to be broken. (Mind you, everything was working before I upgraded, then after I upgraded, it broke.) Here is the output from running startx: $ startx Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.1.0-5 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X :0 -clipboard winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TT F/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/ X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winFinishScreenInitFB - Masks: 00ff ff00 00ff MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = (null ) (--) 5 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from li st! 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/CID/, removing from li st! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winPointerWarpCursor - Discarding first warp: 636 496 winProcEstablishConnection - Hello cat: /home/Mark.Paulus/.Xauthority: No such file or directory winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. Xlib: extension MIT-SHM missing on display :0.0. wmaker warning: could not load font: helvetica:slant=0:weight=100:pixelsize=12. wmaker warning: could not load font: helvetica:xlfd=-*-helvetica-bold-r-normal-* -12-*-*-*-*-*-*-*:slant=0:weight=200:pixelsize=12. wmaker warning: could not load any fonts. Make sure your font installation and l ocale settings are correct. wmaker fatal error: could not initialize WINGs widget set wmaker fatal error: it seems that there is already a window manager running waiting for X server to shut down winClipboardProc - Call to select () failed: - 1. Bailing. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress [EMAIL PROTECTED] ~ === Here is the XWin.log: $ cat /tmp/XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.1.0-5 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X :0 -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TT F/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/ X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 5 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from li st! 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/CID/, removing from li st! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully
locale + how to run wmaker or twm?
By modifying startxwin.bat, I could change the font color. Now I have two questions. 1) How to run wmaker or twm instead of xterm? I tried several ways, but it did not work. 2) How to use locale parameter? I'd like to read/type Korean characters. Please help. Thank you in advance. David - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 9:31 PM Subject: How to change the font color? Hi all, I'd like to know how I can change the font color to white (now it's yellow)? Thank you in advance. David
Re: wmaker TIFF (actually libtiff4) problem
Thank you for clarification of patent issues. (Of course, this makes me wonder: (a) there were reports that this used to work -- or still works -- with cygtiff3. But THAT dll did not provide LZW support either. See below for random speculation. (b) Why Actually I have a system with a rather old cygwin installation. WindowMaker surely works fine on the system. In the old system WindowMaker is version 0.80.0-2 in contrast to the new system having version 0.80.2-1. The old wmaker.exe is linked against cygtiff3.dll. Since their cygtiff3.dll are identical in two systems the old wmaker.exe also works fine on the new system. I believe I have not recompiled any TIFF packages. For now I will not go further because I'm not using WindowMaker. It seems too hard for me to track down. Takuma Murakami ([EMAIL PROTECTED])
Re: wmaker TIFF (actually libtiff4) problem
I have tried to fix the wmaker problem but get stuck since I don't know how to debug DLLs... So there are a number of differences between cygtiff3 and cygtiff4. I tend to suspect the jpeg changes -- are some TIFF images which fail to load all jpeg-compressed, while the ones that succeed are not, perhaps? Although I don't know much about TIFF files, I ran tiffinfo on two systems. The target TIFF file is /usr/X11R6/share/WINGs/Images.tiff in cygwin WindowMaker distribution. On the problematic cygwin (WindowMaker-0.80.2-1, tiff-3.6.0-5) the output is: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field wi th tag 317 (0x13d) encountered. TIFF Directory at offset 0x449c Image Width: 128 Image Length: 128 Resolution: 72, 72 pixels/inch Bits/Sample: 8 Compression Scheme: LZW Photometric Interpretation: RGB color Extra Samples: 1assoc-alpha FillOrder: lsb-to-msb Document Name: /usr/src/Applications/windowmaker/WindowMaker/WINGs/Resources/ Images.tiff Image Description: Created with The GIMP Orientation: row 0 top, col 0 lhs Samples/Pixel: 4 Rows/Strip: 16 Planar Configuration: single image plane On a FreeBSD 4.8 system, the output is: TIFF Directory at offset 0x449c Image Width: 128 Image Length: 128 Resolution: 72, 72 pixels/inch Bits/Sample: 8 Compression Scheme: LZW Photometric Interpretation: RGB color Extra Samples: 1assoc-alpha FillOrder: lsb-to-msb Document Name: /usr/src/Applications/windowmaker/WindowMaker/WINGs/Resources/Images.tiff Image Description: Created with The GIMP Orientation: row 0 top, col 0 lhs Samples/Pixel: 4 Rows/Strip: 16 Planar Configuration: single image plane Predictor: horizontal differencing 2 (0x2) The differences are the warning and the last line. The 'Compression Scheme' field indicates LZW. Is this relevant to the problem? Takuma Murakami ([EMAIL PROTECTED])
Re: wmaker
Brian, Brian Ford wrote: Harold, we have this problem all the time. One user logs in, uses X, logs out, then the next user logs in and X won't start because they can't delete/open /tmp/.X11-unix/X0. Does anyone know how to fix this? Even if the second user has administrator privledges, the startxwin.bat script can not delete the unix socket. Only if the second user explicitly does a chown to themselves can they/startxwin.bat delete the file. Hmm... I ran into this once a long time ago. Are the users actually exiting XWin.exe, or are they leaving it open? You know, Takuma Murakami added a catch for WM_ENDSESSION in XFree86-xserv-4.3.0-22; this message is thrown when a user logs off and catching it causes XWin.exe to shutdown cleanly. Thus, 4.3.0-22 might fix your problem. Have you tried 4.3.0-22? Harold
Re: wmaker TIFF (actually libtiff4) problem
On Fri, Nov 14, 2003 at 06:56:20PM +, [EMAIL PROTECTED] wrote: Several people including myself have experienced the problem where WindowMaker 0.80.2-1 does not properly display some TIFF images. This message describes a solution that seems to work for me. It of course does not seem like a good thing to do, so use at your own risk. (I haven't experienced any adverse effects so far). I simply replaced /bin/cygtiff4.dll with /bin/cygtiff3.dll. i.e. cp /bin/cygtiff3.dll /bin/cygtiff4.dll If you do not have cygtiff3.dll, you just need to install the libtiff3 package. Copying dlls with different versions is rarely a good idea. It's a better idea to figure out what is ostensibly wrong with cygtiff4.dll and fix that.
wmaker
Every time I start Xwin32 ZoneAlarm asks me if I want to allow XWin32 to run as a server, so I answer yes. Then when I start Xterm from program bar ZoneAlarm asks me if I want to allow Xterm (or every other X app) to access the Internet. Nothing happens, neither I answer yes nor no. I want only run wmaker but I'm not connected in a LAN environment, I'm at home not in the office. What I've to do to reach to run wmaker?
Re: wmaker
You talking about X-Win32 or XWin.exe? The former is a commercial product supported by a company not related to the Cygwin/X project (contact them for assistance), while the latter is the our executable that we can help you with. Please advise. Harold Lorenzo Travaglio wrote: Every time I start Xwin32 ZoneAlarm asks me if I want to allow XWin32 to run as a server, so I answer yes. Then when I start Xterm from program bar ZoneAlarm asks me if I want to allow Xterm (or every other X app) to access the Internet. Nothing happens, neither I answer yes nor no. I want only run wmaker but I'm not connected in a LAN environment, I'm at home not in the office. What I've to do to reach to run wmaker?
Keyboard focus problem + scrambled icons in wmaker with latest release
Hello, I'm running the latest version of Cygwin, XFree and WindowMaker (from mirrors.rcn.net, but I also tried mirrors.sunsite.dk and mirrors.kernel.org) in my WinXP Pro workstation and I have the following problems: 1) when I move my mouse outside a xterm windows the keyboard focus is lost by that window and is re-taken when I get back to that window with the mouse pointer. It only happens with Cygwin-XFree's xterm, while if I launch, for example, HP-UX's xterm from a HP workstation or Cygwin's rxvt or Nedit it doesn't happen. This started to happen 1/2 weeks ago (consider that I constantly monitor the announce mailing lists of Cygwin and, hence, I make setup.exe run once every one/two days). I saw, from the list, that other people have this problem too. 2) this morning I ran setup and I downloaded the latest modifications to Xwinclip, XFree86-bin, etc. From that point on, some of the icons of wmaker are scrambled, in particular the icons that represents terminals and the icons of the Window Maker Preferences Utility, launching wmaker by hand (i.e. not as I usually do with a script that launces XWin and then wmaker) I get this errors on stderr: TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag 317 (0x13d) encountered. I don't know if this is a useful information, but I run XFree in rootless mode. I also tried to uninstall wmaker, to remove from my user's home the configuration files of wmaker (I renamed the ~/GNUstep dir) and to re-install wmaker but things haven't changed. Bye, Danilo Turina
wmaker install error
when trying to install from bash prompt (command is wmaker) i get an error related with my home name, that contains a space: example: home: the homedir error is cannot find /home/the - name is truncated at space!
Re: exec wmaker in /etc/xinit/xinitrc doesn't work
If you've never run wmaker before, you need to run /usr/X11R6/bin/wmaker.inst to configure your account. If there's no wmaker.inst, then you don't have the WindowMaker package installed. It's one of the packages available in the Cygwin Setup program. From: cygwin-xfree [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: exec wmaker in /etc/xinit/xinitrc doesn't work Date: Thu, 4 Sep 2003 23:33:14 -0400 Hi- I want to run WindowMaker rather than twm, so I edited /etc/xinit/xinitrc and replaced exec twm with exec wmaker then when I ran 'startx', WindowMaker started then immediately crashed. What am I missing here? Thanks for the help. _ Get a FREE computer virus scan online from McAfee. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
exec wmaker in /etc/xinit/xinitrc doesn't work
Hi- I want to run WindowMaker rather than twm, so I edited /etc/xinit/xinitrc and replaced exec twm with exec wmaker then when I ran 'startx', WindowMaker started then immediately crashed. What am I missing here? Thanks for the help.
wmaker fatal error: could not open display :0
Having trouble getting X to run... The worst part about this is that I had it working a few hours ago, but I uninstalled and reinstalled becaused I foobared my package choices and vim couldn't find some resource. So atleast I know it's a configuration problem. Now to pin it down... I am using WindowsXP Home Ed. SP1 When I attempt to startx I get the following: - $ startx waiting for X server to shut down $ wmaker fatal error: could not open display :0 - I've also tried: - $ startx -display :1 // I've tried it as 1, :1 and :1 with the same response /usr/X11R6/bin/xterm Xt error: Can't open display: :1 waiting for X server to shut down - My XWin.log from just the command startx reads as... - $ cat XWin.log - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed - WindowClient w 1018 h 735 r 1018 l 0 b 735 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 4072 winAllocateFBShadowDDNL - Created shadow pitch: 4072 winAllocateFBShadowDDNL - Created shadow stride: 1018 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 509 367 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned - END XWin.log - And my cygwin.bat file reads - cygwin.bat - @echo off set DISPLAY=127.0.0.1:0.0 set CYGWIN=tty notitle glob set HOME=C:\cygwin\home PATH=C:\cygwin\bin;C:\cygwin\sbin;C:\cygwin\usr\bin;C:\cygwin\usr\sbin;C:\cy gwin\usr\local\bin;C:\cygwin\usr\X11R6\bin;.. C: chdir C:\cygwin\bin bash --login -i - END cygwin.bat - Last but not least... my .xinitrc file looks like this... - $ cat .xinitrc - #!/bin/sh # $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $ userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11R6/lib/X11/xinit/.Xresources sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap # merge in defaults and keymaps if [ -f $sysresources ]; then xrdb -merge $sysresources fi if [ -f $sysmodmap ]; then xmodmap $sysmodmap fi if [ -f $userresources ]; then xrdb -merge $userresources fi if [ -f $usermodmap ]; then xmodmap $usermodmap fi # start some nice programs # twm # xclock -geometry 50x50-1+1 # xterm -geometry 80x50+494+51 # xterm -geometry 80x20+494-0 # exec xterm -geometry 80x66+0+0 -name login wmaker - END $ cat .xinitrc - Heeelllp! :P _ Free email with personality! Over 200 domains! http://www.MyOwnEmail.com Looking for friendships,romance and more? http://www.MyOwnFriends.com
Re: wmaker fatal error: could not open display :0
What happens if you try startxwin.sh? Thats how I pull up my xwindows. /Andy / digitalsmear [EMAIL PROTECTED] wrote: | Having trouble getting X to run... The worst part about this is that I | had it working a few hours ago, but I uninstalled and reinstalled becaused | I foobared my package choices and vim couldn't find some resource. So | atleast I know it's a configuration problem. Now to pin it down... | | I am using WindowsXP Home Ed. SP1 | When I attempt to startx I get the following: | - | $ startx | waiting for X server to shut down | $ wmaker fatal error: could not open display :0 -- The parser of the compiler rests on the code! Please note, new email, @telia.com - @comhem.se
RE: WMaker crashes when starting with startxwin.bat
Well I fixed the prob, I just added this to startxwin.bat REM Startup bash and run startx run bash --login -c startx Hope this helps someone else... Sergio -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sergio Sent: Wednesday, May 28, 2003 2:04 AM To: [EMAIL PROTECTED] Subject: Re: WMaker crashes when starting with startxwin.bat Hello, I have just installed cygwin and everything is working fine except for one small problem. When I start up cygwin and load up Xwin via bash everything is fine, I have 2 xterms popup and a clock. My xterms are set to start in my home dir. My problem is loading Xwin via startxwin.bat. I found this email in the archives, and the settings here fixed my Signal 11 Xwin problem, and Xwin loads up fine via the startxwin.bat, but when my xterms popup they don't have the HOME var set. I fixed this problem with the bash --login option. I know this is because /etc/profile isn't read in the .bat. Is there any way to have the /etc/profile read, because I have other little in there I would like to use. I could live without them, but I was just curious. Thanks, Sergio Hi Klaus yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? take my startxwin.bat as an example. Cygwin is installed on d:\cygwin. The only customized lines are SET HOME, SET CYGWIN_ROOT, the rest is standard startxwin.bat with different WM-calls REMmed on and off. HTH hjb @echo off D: SET DISPLAY=127.0.0.1:0.0 SET HOME=/CYGDRIVE/D/cygwin/home/DV105 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/XFree86, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=D:\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM Startup the X Server, the twm window manager, and an xterm. REM ... skipped if %OS% == Windows_NT goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxwin.bat - Starting on Windows NT/2000/XP :STARTUP REM REM Startup the programs REM REM Startup the X Server. REM start XWin %1 REM start XWin -fullscreen start XWin -rootless REM start XWin -broadcast REM Startup an xterm, using bash as the shell. REM run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash REM setxkbmap de REM Startup the twm window manager. REM run twm REM run fvwm2 REM run openbox run wmaker xrdb -merge .Xresources REM Set a background color. REM run xsetroot -solid aquamarine4 exit
Re: WMaker crashes when starting with startxwin.bat
Hello, I have just installed cygwin and everything is working fine except for one small problem. When I start up cygwin and load up Xwin via bash everything is fine, I have 2 xterms popup and a clock. My xterms are set to start in my home dir. My problem is loading Xwin via startxwin.bat. I found this email in the archives, and the settings here fixed my Signal 11 Xwin problem, and Xwin loads up fine via the startxwin.bat, but when my xterms popup they don't have the HOME var set. I fixed this problem with the bash --login option. I know this is because /etc/profile isn't read in the .bat. Is there any way to have the /etc/profile read, because I have other little in there I would like to use. I could live without them, but I was just curious. Thanks, Sergio Hi Klaus yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? take my startxwin.bat as an example. Cygwin is installed on d:\cygwin. The only customized lines are SET HOME, SET CYGWIN_ROOT, the rest is standard startxwin.bat with different WM-calls REMmed on and off. HTH hjb @echo off D: SET DISPLAY=127.0.0.1:0.0 SET HOME=/CYGDRIVE/D/cygwin/home/DV105 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/XFree86, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=D:\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM Startup the X Server, the twm window manager, and an xterm. REM ... skipped if %OS% == Windows_NT goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxwin.bat - Starting on Windows NT/2000/XP :STARTUP REM REM Startup the programs REM REM Startup the X Server. REM start XWin %1 REM start XWin -fullscreen start XWin -rootless REM start XWin -broadcast REM Startup an xterm, using bash as the shell. REM run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash REM setxkbmap de REM Startup the twm window manager. REM run twm REM run fvwm2 REM run openbox run wmaker xrdb -merge .Xresources REM Set a background color. REM run xsetroot -solid aquamarine4 exit
Antwort: Re: WMaker crashes when starting with startxwin.bat
Hi Klaus yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? take my startxwin.bat as an example. Cygwin is installed on d:\cygwin. The only customized lines are SET HOME, SET CYGWIN_ROOT, the rest is standard startxwin.bat with different WM-calls REMmed on and off. HTH hjb @echo off D: SET DISPLAY=127.0.0.1:0.0 SET HOME=/CYGDRIVE/D/cygwin/home/DV105 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/XFree86, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=D:\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM Startup the X Server, the twm window manager, and an xterm. REM ... skipped if %OS% == Windows_NT goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxwin.bat - Starting on Windows NT/2000/XP :STARTUP REM REM Startup the programs REM REM Startup the X Server. REM start XWin %1 REM start XWin -fullscreen start XWin -rootless REM start XWin -broadcast REM Startup an xterm, using bash as the shell. REM run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash REM setxkbmap de REM Startup the twm window manager. REM run twm REM run fvwm2 REM run openbox run wmaker xrdb -merge .Xresources REM Set a background color. REM run xsetroot -solid aquamarine4 exit
Re: Antwort: Re: WMaker crashes when starting with startxwin.bat
Hi hjb, this was the sollution! Actually I had two problems: 1. When I installed cygwin, it didn't create a 'good' home directory. It cretared a directory '/usr/bin/%USERPROFILE%' because my Windows Home is on a different drive than my cygwin installation. 2. The correct path to HOME had to be set. I've done that and now it works. Cheers, Klaus Hi Klaus yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? take my startxwin.bat as an example. Cygwin is installed on d:\cygwin. The only customized lines are SET HOME, SET CYGWIN_ROOT, the rest is standard startxwin.bat with different WM-calls REMmed on and off. HTH hjb @echo off D: SET DISPLAY=127.0.0.1:0.0 SET HOME=/CYGDRIVE/D/cygwin/home/DV105 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/XFree86, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=D:\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM Startup the X Server, the twm window manager, and an xterm. REM ... skipped if %OS% == Windows_NT goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxwin.bat - Starting on Windows NT/2000/XP :STARTUP REM REM Startup the programs REM REM Startup the X Server. REM start XWin %1 REM start XWin -fullscreen start XWin -rootless REM start XWin -broadcast REM Startup an xterm, using bash as the shell. REM run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash REM setxkbmap de REM Startup the twm window manager. REM run twm REM run fvwm2 REM run openbox run wmaker xrdb -merge .Xresources REM Set a background color. REM run xsetroot -solid aquamarine4 exit -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Re: WMaker crashes when starting with startxwin.bat
Klaus, FYI, HOME is set in the default /etc/profile... When you start from the Cygwin bash window, bash will have executed /etc/profile, and you have the right $HOME. If you run from a batch file, /etc/profile would not have been executed, and $HOME not set. Try putting 'bash --login -c wmaker', for example, in your batch file... Igor On Fri, 28 Feb 2003 [EMAIL PROTECTED] wrote: JS, yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? Klaus Hi Klaus, This answer probably won't help because I'm probably speaking rubbish, but I have got the same problem as you, so I know what you're talking about. You can start wmaker from the cygwin window, but not from a batch file (or more specifically a windows command window). I think this probably has something to do with the user $HOME, because in Cygwin it knows your $HOME is /home/user, and under there you have the GNUstep folder with your WindowMaker settings. However your windows home is probably pointing somewhere else, so WindowMaker can't find the GNUstep folder in your home directory, causing it to crash? JS. Hi all, I just installed Cygwin using the Internet installation including XFree86 and wmaker. I can start X without any problem and I can start wmaker from the bash prompt. The only problem I have is with startxwin.bat. I changed the window manager in this file from twm to wmaker, but whenever I try, I get the following error: Window Maker received signal 11. I see that X is up and it even changed the background color according to the settings in startxwin.bat. In the archive for this mailing list I found the suggestion to change the HOME path settings, but either I did something wrong there, or the problem is something else. I can start wmaker using startxwin.sh and startx - no problem with this. Just startxwin.bat is the problem and just with wmaker. I'm really sorry if this is the wrong mailing list, or this is a real bug I should have reported somewhere else. I just think this is probably not a bug, because wmaker is running fine when started from the bash. Thanks very much for any help. Cheers, Klaus -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune
WMaker crashes when starting with startxwin.bat
Hi all, I just installed Cygwin using the Internet installation including XFree86 and wmaker. I can start X without any problem and I can start wmaker from the bash prompt. The only problem I have is with startxwin.bat. I changed the window manager in this file from twm to wmaker, but whenever I try, I get the following error: Window Maker received signal 11. I see that X is up and it even changed the background color according to the settings in startxwin.bat. In the archive for this mailing list I found the suggestion to change the HOME path settings, but either I did something wrong there, or the problem is something else. I can start wmaker using startxwin.sh and startx - no problem with this. Just startxwin.bat is the problem and just with wmaker. I'm really sorry if this is the wrong mailing list, or this is a real bug I should have reported somewhere else. I just think this is probably not a bug, because wmaker is running fine when started from the bash. Thanks very much for any help. Cheers, Klaus -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Re: WMaker crashes when starting with startxwin.bat
Hi Klaus, This answer probably won't help because I'm probably speaking rubbish, but I have got the same problem as you, so I know what you're talking about. You can start wmaker from the cygwin window, but not from a batch file (or more specifically a windows command window). I think this probably has something to do with the user $HOME, because in Cygwin it knows your $HOME is /home/user, and under there you have the GNUstep folder with your WindowMaker settings. However your windows home is probably pointing somewhere else, so WindowMaker can't find the GNUstep folder in your home directory, causing it to crash? JS. Hi all, I just installed Cygwin using the Internet installation including XFree86 and wmaker. I can start X without any problem and I can start wmaker from the bash prompt. The only problem I have is with startxwin.bat. I changed the window manager in this file from twm to wmaker, but whenever I try, I get the following error: Window Maker received signal 11. I see that X is up and it even changed the background color according to the settings in startxwin.bat. In the archive for this mailing list I found the suggestion to change the HOME path settings, but either I did something wrong there, or the problem is something else. I can start wmaker using startxwin.sh and startx - no problem with this. Just startxwin.bat is the problem and just with wmaker. I'm really sorry if this is the wrong mailing list, or this is a real bug I should have reported somewhere else. I just think this is probably not a bug, because wmaker is running fine when started from the bash. Thanks very much for any help. Cheers, Klaus -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! _ Chat online in real time with MSN Messenger http://messenger.msn.co.uk
Re: WMaker crashes when starting with startxwin.bat
JS, yes, you're probably right. But now the tricky question: How can I change the windows home to point to my $HOME in cygwin to solve that problem? Klaus Hi Klaus, This answer probably won't help because I'm probably speaking rubbish, but I have got the same problem as you, so I know what you're talking about. You can start wmaker from the cygwin window, but not from a batch file (or more specifically a windows command window). I think this probably has something to do with the user $HOME, because in Cygwin it knows your $HOME is /home/user, and under there you have the GNUstep folder with your WindowMaker settings. However your windows home is probably pointing somewhere else, so WindowMaker can't find the GNUstep folder in your home directory, causing it to crash? JS. Hi all, I just installed Cygwin using the Internet installation including XFree86 and wmaker. I can start X without any problem and I can start wmaker from the bash prompt. The only problem I have is with startxwin.bat. I changed the window manager in this file from twm to wmaker, but whenever I try, I get the following error: Window Maker received signal 11. I see that X is up and it even changed the background color according to the settings in startxwin.bat. In the archive for this mailing list I found the suggestion to change the HOME path settings, but either I did something wrong there, or the problem is something else. I can start wmaker using startxwin.sh and startx - no problem with this. Just startxwin.bat is the problem and just with wmaker. I'm really sorry if this is the wrong mailing list, or this is a real bug I should have reported somewhere else. I just think this is probably not a bug, because wmaker is running fine when started from the bash. Thanks very much for any help. Cheers, Klaus -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! _ Chat online in real time with MSN Messenger http://messenger.msn.co.uk -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
RE: wmaker signal 11
Vikram [mailto:[EMAIL PROTECTED]] wrote: I downloaded cygwin afresh on a new box yesterday. For the first time decided to try out wmaker.exe wmaker got signal 11 everytime I started. I had similar problems at first. I believe I had to switch to a binary mount point. Something like this: $ mount -f -s -b C:/cygwin / But make sure you know what you're doing before you try it. :-) -Jerry
RE: wmaker signal 11
I can report that if you install Cygwin and choose DOS files instead of UNIX files as a setup option, wmaker crashes on startup as a matter of course. 'course I don't really know WHY that is, but I did observe the fact. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold L Hunt II Sent: Monday, October 14, 2002 11:26 AM To: [EMAIL PROTECTED] Subject: Re: wmaker signal 11 Did I build the wmaker package? I am guessing that I did... in that case, I should be linking automode.o with the wmaker executable so that we are not dependent upon binary mounts. Any objections? Harold Gerald S. Williams wrote: Vikram [mailto:[EMAIL PROTECTED]] wrote: I downloaded cygwin afresh on a new box yesterday. For the first time decided to try out wmaker.exe wmaker got signal 11 everytime I started. I had similar problems at first. I believe I had to switch to a binary mount point. Something like this: $ mount -f -s -b C:/cygwin / But make sure you know what you're doing before you try it. :-) -Jerry
