Re: Problems with Startx even after rebaseall
* Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700) On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote: * Robert Neville (Mon, 30 Apr 2007 10:18:15 -0700) I am not sure if this is the appropriate group. In addition, searching through these gmane newsgroups is not straightforward since Google groups does not return them. Startx fails to initialize when it worked yesterday. I ran setup and the process may have not completed (it was late and I needed to sleep). After running setup.exe again, I navigated to the System category and reinstalled rebase. Then I reviewed the README file; kill all processes associated with cygwin; ran ash; and typed /bin/rebaseall -v; the utility performed some actions and returned without errors. I fired up a cygwin window and startx would still not initialize. The console gave me the following font error. sageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. The cygwin console appears fully functional. The console has returned some errors when running make, but these issues may be completely separate. Please give me whatever insight you may have on these scenarios. I have already spent considerable time troubleshooting these issues and need better guidance. After rebooting the computer and typing startx, cygwin gave me the following error message. [...] winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMes sageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winClipboardIOErrorHandler! Well, if there is an winClipboardIOErrorHandler error (whatever that is) you should try starting without -clipboard says my common sense... I am not familiar with the startx options. The man page only has basic info about startx. I tried startx -clipboard as suggested; and the console returned the following error. XWin was started with the following command line: X :0 -multiwindow -clipboard Read again my posting. I said without and not with (which wouldn't make sense at all if there is a winClipboardIOError). startx is a shell script. Copy it, find the line where XWin is started and remove the arguments (parameters). Then start this script. Thorsten -- 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: X Server cycling when trying to connect to gdm/dtlogin.
I am having the same problem...any solution? Thanks, Chris I'm trying to use Cygwin/X to connect to remote machines' gdm or dtlogin session managers. If I run: XWin.exe -query hostname I get the session login screen, can enter in my username and password and see the desktop clear and appear to begin loading. Then all of the sudden the X window quits and restarts back at the login screen again. This happens with both Solaris 10 dtlogin sessions and RH gdm sessions. On RH, if I choose failsafe (just an xterm with no WM), the login succeeds and I get a single xterm. Thought maybe this was a font issue, so I used the -fp tcp/hostname:7100 on the command-line (yes, also modified xfs to accept tcp connections ...) but the same thing continues to happen. The XWin.log file doesn't show any errors that I can use to troubleshoot this, and I don't see anything in the logs on the remote systems either. Any hunches as to what the problem is? Ray (PS: I did add -logverbose 255 as well, but got no additional information). -- 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/ -- 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/
display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Hello. I use Cygwin/X on my office computer to run a program called Cadence (using 24-bit display), but have limited Cygwin functionality when I use remote desktop to work from home. Displays are set to 32-bit on both computers, and the Windows XP remote-desktop protocol (RDP) version I am using on both supports 32-bit displays. If I start Cygwin at the office and then use RDP to connect from home, everything continues working perfectly. However, if I log in remotely and then start a new Cygwin session, I get the following: *ERROR* Failed to find either 24-bit TrueColor or 8-bit PseudoColor Visual. *WARNING* Failed to find either 24-bit TrueColor or 8-pbit PseudoColor Visual. And my application will not start. I am using the following to start cygwin: run XWin -multiwindow -clipboard -silent-dup-error run xterm -e /usr/bin/bash -l I believe that Cygwin is detecting the optimal display settings on startup and determining it to be less than 32-bit when initiated through remote desktop. I would use the -depth command line option to manually set the depth to 32 bits, but this does not work with multiwindow enabled. Is there another way that I can manually set the display depth? Or somehow ensure that Cygwin determines that 32-bits are optimal when started through a remote desktop session? I have tried modifying the .inputrc file for 8-bit mode as follows, but had the same problem. set meta-flag on set convert-meta off set output-meta on Many thanks, Jason cygcheck_original.out Description: Binary data -- 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: X Server cycling when trying to connect to gdm/dtlogin.
Chris Eagan schrieb: I'm trying to use Cygwin/X to connect to remote machines' gdm or dtlogin session managers. XWin.exe -query hostname Does anything change if you use XWin -query numeric.ip.address -from numeric.ip.address ? And create and use a new user on your unix box to get a clean profile on login if that is possible. -- 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: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Jason May schrieb: I believe that Cygwin is detecting the optimal display settings on startup and determining it to be less than 32-bit when initiated through remote desktop. I would use the -depth command line option to manually set the depth to 32 bits, but this does not work with multiwindow enabled. Is there another way that I can manually set the display depth? You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. I have tried modifying the .inputrc file for 8-bit mode as follows, but had the same problem. That has no influence on Xwin. A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. -- 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: Problems with Startx even after rebaseall
On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote: * Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700) On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote: * Robert Neville (Mon, 30 Apr 2007 10:18:15 -0700) I am not sure if this is the appropriate group. In addition, searching through these gmane newsgroups is not straightforward since Google groups does not return them. Startx fails to initialize when it worked yesterday. I ran setup and the process may have not completed (it was late and I needed to sleep). After running setup.exe again, I navigated to the System category and reinstalled rebase. Then I reviewed the README file; kill all processes associated with cygwin; ran ash; and typed /bin/rebaseall -v; the utility performed some actions and returned without errors. I fired up a cygwin window and startx would still not initialize. The console gave me the following font error. sageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. The cygwin console appears fully functional. The console has returned some errors when running make, but these issues may be completely separate. Please give me whatever insight you may have on these scenarios. I have already spent considerable time troubleshooting these issues and need better guidance. XWin was started with the following command line: X :0 -multiwindow -clipboard Read again my posting. I said without and not with (which wouldn't make sense at all if there is a winClipboardIOError). startx is a shell script. Copy it, find the line where XWin is started and remove the arguments (parameters). Then start this script. Thorsten I did not realize that startx was just a script. Honestly, the clipboard is the main reason for me launching Xwin. After editing the script and removing the clipboard argument, the console returns a winInitMultiWindowXMsgProc - Caught IO Error. Then I removed the multiwindow argument and the console returned the following error. I don't have much time to evaluate this scenario or the patience; hopefully someone has seen this scenario before. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.99.901-4 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root 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 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: 509 353 winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard is not enabled, returning. cat: /home/Ferdie/.Xauthority: No such file or directory waiting for X server to shut down FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. winDeinitMultiWindowWM - Noting shutdown in progress -- 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: display depth changing when using remote desktop and -multiwindow option, unable to set depth manually with -multiwindow
Thanks Holger for the response. - You can't set Xwins display depth larger than the Desktop it is running on. Usually that would be 16 Bit with rdp sessions. Did you ever check on the rdp Windows Desktop that you really get 32 Bit in Windows? Because i get 16 Bit even if i request 24 Bit. - I'm using a new beta version of microsoft's RDP which should support 32-bit displays (http://support.microsoft.com/kb/925876), but I will have to check whether it is actually working as advertised. - A possible solution would be a ssh connection and tunneling X11 through it. Cygwin provides a ssh daemon for windows. I am currently using SSH (putty) with tunneling to connect from the office PC to a linux server. The network administrators have not opened any ports on the linux server for outside access, I believe I can only enter the network via RDP on my office computer. I will see if they will allow me to open another port on my computer for SSH port forwarding, it should indeed solve the problem if I can bypass the office computer directly. Jason -- 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/
