Re: cygGNOME2
On Wed, May 05, 2004 at 06:16:53PM +0200, Alessandro Lendaro wrote: >Christopher Faylor wrote: >>On Wed, May 05, 2004 at 12:28:54PM +0200, Alessandro Lendaro wrote: >>>Christopher Faylor wrote: Why are you asking about this here rather than using the resources at the web site where you downloaded the package? >>> >>>because I didn' t find any resources for my problems in that site. >> >>Then you really didn't look too hard. > >Yeah, probably. I have to work so I don't have so much time to search >for pages that are not in evidence. + I 'm not english speaking, so >searching for me it's a bit more difficult. If you find that the >solution to my problems is in those sites' pages, then why you don't >post a link? That could be helpful. I did not find a solution for your problem. I went to the project's site and saw a link called "Forum". That would point you to the place where you should ask questions. This has already been pointed out to you.
Re: Debugging Output
On Wed, 5 May 2004, Wilks, Dan wrote: > Alexander Gottwald wrote: > > > - debugging output: winDebug(format, args...) > > - non important configuration messages: winErrorFVerb(2, format, args) > > > -logverbose 3...? can give debug messages with differing severity > > eg -logverbose 3 may print simple traces > > while -logverbose 10 will also dump all windows messages received > > Looking at the #if 0'd logging in windclipboardwndproc would you expect > that be converted to winDebug (which is logged at level 3) or should it > be explicitly logged at level 10: winErrorFVerb(10,...) since it's really > logging window messages? no. winDebug is sufficient. I was thinking about setting the WM_XXX messages to a higher loglevel since they may create to many messages. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Silent exit after double-clicking on text in xterm
This is a recurring problem for me. Occasionally, Xwin.exe will quickly terminate when I double-click on a string of text displayed in an xterm. This occurs on my home computer running Windows 2000, and on my office computer running Windows XP. Here is the Xwin.log file. I believe that it indicates that I have the latest version of the cygwin/x software installed. Note that the last line of the log is "winMultiWindowXMsgProc - another window manager is running. Exiting." This is certainly false. I have been using the -multiwindow method for monthes, and there is not even a window manager installed on my computer. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-8 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning 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 winPrefsLoadPreferences: /cygdrive/p/.XWinrc LoadPreferences: .XWinrc Loaded winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () 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: "0409" (0409) (EE) Keyboardlayout "US" (0409) is unknown Rules = "xorg" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 640 511 winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /cygdrive/p/.XWinrc LoadPreferences: .XWinrc Loaded winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless => ShadowGDI winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 MIT-SHM extension disabled due to lack of kernel support winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () 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: "0409" (0409) (EE) Keyboardlayout "US" (0409) is unknown Rules = "xorg" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc -
checksum failure for xorg-bin-6.7.0.0-4
Hi *, when installing with setup.exe I get a "Checksum failure" for the file xorg-bin-6.7.0.0-4.tar.bz2 I checked manualy and the md5 seems to be different from the should-be but same over all mirrors I tested. Regards, -- Michael Thomas Kirchner
Debugging Output
Alexander Gottwald wrote: > - debugging output: winDebug(format, args...) > - non important configuration messages: winErrorFVerb(2, format, args) > -logverbose 3...? can give debug messages with differing severity > eg -logverbose 3 may print simple traces > while -logverbose 10 will also dump all windows messages received Looking at the #if 0'd logging in windclipboardwndproc would you expect that be converted to winDebug (which is logged at level 3) or should it be explicitly logged at level 10: winErrorFVerb(10,...) since it's really logging window messages? Thanks, Dan
Re: cygGNOME2
Christopher Faylor wrote: On Wed, May 05, 2004 at 12:28:54PM +0200, Alessandro Lendaro wrote: Christopher Faylor wrote: Why are you asking about this here rather than using the resources at the web site where you downloaded the package? because I didn' t find any resources for my problems in that site. Then you really didn't look too hard. Yeah, probably. I have to work so I don't have so much time to search for pages that are not in evidence. + I 'm not english speaking, so searching for me it's a bit more difficult. If you find that the solution to my problems is in those sites' pages, then why you don't post a link? That could be helpful.
New X server with WindowMaker does not allow keystroke when is on
I refer to Cygwin's XWin version 6.7.0.0-7 or -8 and wmaker version 0.80.2-1. If is ON, key does not passed down to program. In particular I've observed it with xfte and xterm/bash sessions. The program is not responding to the key as it should. If I turn off the , the key is passed as usual. I have tested the problem with full screen, or windowed desktop (i.e. cygwin server running on a single window and all the X sessions inside it). I haven't tested it with rootless WM session. BTW my computer is a Pentium III running Windows 2000 (SP 4). This problem does not exist if I don't use window manager at all, or if I use twm. It must have been specific to WindowMaker, or bad interaction between it and the X server. Wirawan
Re: cygGNOME2
On Wed, May 05, 2004 at 12:28:54PM +0200, Alessandro Lendaro wrote: >Christopher Faylor wrote: >>Why are you asking about this here rather than using the resources at >>the web site where you downloaded the package? >> >because I didn' t find any resources for my problems in that site. Then you really didn't look too hard.
Cygwin
Hi, I use cygwin-xfree in multi-users environment. The first user always succes in start X (startxwin.bat) , but if cygwin crash or winXP crash, the file c:\cygwin\tmp\.X11-unix\X0 isn't erase and the others users cannot start X ... I have found some posts about this problem but none explain how to fix that. I have try to set the HOME variable but, it seem that the tmp directory is not affect by that. How could i run start X on NTFS and prevent that this file stay here with bad rights (the only user who can delete the file is the one who start X, even the administrator cannot delete the file without appropriation). Here is my cygcheck : http://www.esstin.uhp-nancy.fr/tmp/cygcheck.txt FMH.
Re: cygGNOME2
On Wed, 5 May 2004, Alessandro Lendaro wrote: > Christopher Faylor wrote: > > On Fri, Apr 30, 2004 at 04:22:42PM +0200, Alessandro Lendaro wrote: > > > >>I can't make GNOME2 work on cygwin. > >>I installed the packages found at cygnom2.sourceforge.net/install > >>but I don't knowh which commands must be issued to start a GNOME2 > >>session. > >>When I try to launch apps like Gaim or Bluefish I get a win32 error > >>saying the app is unable to locate the cygfontconfig-1.dll > >>which is not installed in my cygwin folder. > >> > >>Is somebody able to give me a clue? > > > > > > Why are you asking about this here rather than using the resources > > at the web site where you downloaded the package? > > > because I didn' t find any resources for my problems > in that site. There is a mailinglist which may be more useful for your problems: http://lists.sourceforge.net/lists/listinfo/cygnome2-user bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: cygGNOME2
Christopher Faylor wrote: On Fri, Apr 30, 2004 at 04:22:42PM +0200, Alessandro Lendaro wrote: I can't make GNOME2 work on cygwin. I installed the packages found at cygnom2.sourceforge.net/install but I don't knowh which commands must be issued to start a GNOME2 session. When I try to launch apps like Gaim or Bluefish I get a win32 error saying the app is unable to locate the cygfontconfig-1.dll which is not installed in my cygwin folder. Is somebody able to give me a clue? Why are you asking about this here rather than using the resources at the web site where you downloaded the package? because I didn' t find any resources for my problems in that site.
