Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
Fedora 12 - kdm for the greeter. Jon TURNEY wrote: On 20/11/2009 15:46, Michael Breuer wrote: I've attached the log. Thanks. Can you also please tell me what OS the XDMCP host at 10.0.0.1 is running? Jon TURNEY wrote: On 19/11/2009 16:25, Michael Breuer wrote: For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. Could you tell me what the clipboard related error message is? 2009-11-20 10:46:08 winClipboardIOErrorHandler! 2009-11-20 10:46:08 winClipboardProc - setjmp returned for IO Error Handler. 2009-11-20 10:46:08 winClipboardShutdown - Clipboard thread has exited. Hmmm... The problem here is that the internal clipboard integration client is terminating for some reason. (This is not entirely unexpected in XDMCP use, as login managers often try to kill other clients to ensure they don't watch you type your password, but there is code in place to try to prevent this happening to the clipboard integration client, in case you want to paste your password...) Since Xserver 1.7.1-1, terminating the clipboard integration client causes the Xserver to terminate as well (although this change, which also applies to the -multiwindow internal window manager, doesn't seem to be mentioned in any of the announce emails) My reasoning for this change was that we shouldn't accept the options turning these internal clients on and then silently allow them to fail. This was particularly bad with the -multiwindow internal window manager, as if that client exits all new windows have no native frames, which is particularly useless. I guess this also interacts unfortunately with -clipboard being the default now, since 1.6.1.902-1 So, perhaps we need to do something smarter here, either improve the way we try to avoid the internal clipboard client getting killed, or perhaps restart it after an interval ... -- 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: XWin stopped working with xorg-server 1.7.1 - no log-file created
On 20/11/2009 15:46, Michael Breuer wrote: I've attached the log. Thanks. Can you also please tell me what OS the XDMCP host at 10.0.0.1 is running? Jon TURNEY wrote: On 19/11/2009 16:25, Michael Breuer wrote: For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. Could you tell me what the clipboard related error message is? 2009-11-20 10:46:08 winClipboardIOErrorHandler! 2009-11-20 10:46:08 winClipboardProc - setjmp returned for IO Error Handler. 2009-11-20 10:46:08 winClipboardShutdown - Clipboard thread has exited. Hmmm... The problem here is that the internal clipboard integration client is terminating for some reason. (This is not entirely unexpected in XDMCP use, as login managers often try to kill other clients to ensure they don't watch you type your password, but there is code in place to try to prevent this happening to the clipboard integration client, in case you want to paste your password...) Since Xserver 1.7.1-1, terminating the clipboard integration client causes the Xserver to terminate as well (although this change, which also applies to the -multiwindow internal window manager, doesn't seem to be mentioned in any of the announce emails) My reasoning for this change was that we shouldn't accept the options turning these internal clients on and then silently allow them to fail. This was particularly bad with the -multiwindow internal window manager, as if that client exits all new windows have no native frames, which is particularly useless. I guess this also interacts unfortunately with -clipboard being the default now, since 1.6.1.902-1 So, perhaps we need to do something smarter here, either improve the way we try to avoid the internal clipboard client getting killed, or perhaps restart it after an interval ... -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: XWin stopped working with xorg-server 1.7.1 - no log-file created
I've attached the log. Jon TURNEY wrote: On 19/11/2009 16:25, Michael Breuer wrote: For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. Could you tell me what the clipboard related error message is? Then I could perhaps try to fix it rather than tell everyone to use -noclipboard :-) One other point - as older versions of CygwinX have major issues (100% cpu) with the newer version of Gnome (now in F12), more people are going to be trying the beta and hitting this. Not sure what code is involved, but including this on the beta FAQ might be worthwhile. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: xwin :0 -query 10.0.0.1 -xinerama -logverbose 3 -from 10.0.0.11 ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1680 h 1050 winInitializeDefaultScreens - Returning 2009-11-20 10:46:01 OsVendorInit - Creating bogus screen 0 2009-11-20 10:46:07 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-11-20 10:46:07 winValidateArgs - Returning. 2009-11-20 10:46:07 (II) xorg.conf is not supported 2009-11-20 10:46:07 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-11-20 10:46:07 winPrefsLoadPreferences: /etc/X11/system.XWinrc 2009-11-20 10:46:07 LoadPreferences: Done parsing the configuration file... 2009-11-20 10:46:07 winGetDisplay: DISPLAY=:0.0 2009-11-20 10:46:07 winDetectSupportedEngines - Windows NT/2000/XP 2009-11-20 10:46:07 winDetectSupportedEngines - DirectDraw installed 2009-11-20 10:46:07 winDetectSupportedEngines - DirectDraw4 installed 2009-11-20 10:46:07 winDetectSupportedEngines - Returning, supported engines 0007 2009-11-20 10:46:07 winScreenInit - dwWidth: 1680 dwHeight: 1050 2009-11-20 10:46:07 winSetEngine - Using Shadow DirectDraw NonLocking 2009-11-20 10:46:07 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel 2009-11-20 10:46:07 winCreateBoundingWindowWindowed - User w: 1680 h: 1050 2009-11-20 10:46:07 winCreateBoundingWindowWindowed - Current w: 1680 h: 1050 2009-11-20 10:46:07 winAdjustForAutoHide - Original WorkArea: 0 0 1050 1680 2009-11-20 10:46:07 winAdjustForAutoHide - Taskbar is auto hide 2009-11-20 10:46:07 winAdjustForAutoHide - Found BOTTOM auto-hide taskbar 2009-11-20 10:46:07 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1049 1680 2009-11-20 10:46:07 winCreateBoundingWindowWindowed - WindowClient w 1674 h 1021 r 1674 l 0 b 1021 t 0 2009-11-20 10:46:07 winWindowProc - WM_ACTIVATEAPP 2009-11-20 10:46:07 winCreateBoundingWindowWindowed - Returning 2009-11-20 10:46:07 winCreatePrimarySurfaceShadowDDNL - Creating primary surface 2009-11-20 10:46:07 winCreatePrimarySurfaceShadowDDNL - Created primary surface 2009-11-20 10:46:07 winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface 2009-11-20 10:46:07 winAllocateFBShadowDDNL - lPitch: 6696 2009-11-20 10:46:07 winAllocateFBShadowDDNL - Created shadow pitch: 6696 2009-11-20 10:46:07 winAllocateFBShadowDDNL - Created shadow stride: 1674 2009-11-20 10:46:07 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2009-11-20 10:46:07 winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2009-11-20 10:46:07 winRandRInit () 2009-11-20 10:46:07 winCreateDefColormap - Deferring to fbCreateDefColormap () 2009-11-20 10:46:07 winFinishScreenInitFB - returning 2009-11-20 10:46:07 Screen 0 added at XINERAMA coordinate (0,0). 2009-11-20 10:46:07 winScreenInit - returning 2009-11-20 10:46:07 winGenerateAuthorization - GenerateAuthorization success! AuthDataLen: 16 AuthData: [8 ¤ÖøÃ3n{)®¡èú 2009-11-20 10:46:07 InitOutput - Returning. 2009-11-20 10:46:07 MIT-SHM extension disabled due to lack of kernel support 2009-11-20 10:46:07 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-20 10:46:07 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-11-20 10:46:07 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-11-20 10:46:08 winPointerWarpCursor - Discarding first warp: 837 510 2009-11-20 10:46:08 (--) 8 mouse buttons found 2009-11-20 10:46:08 (--) Setting autorepeat to delay=500, rate=31 2009-11-20 10:46:08 (--) winConfigKeyboard - Layout: "0409" (0409) 2009-11-20 10:46:08 (--) Using preset keyboard for "English (USA)" (409), type "7" 2009-11-20 10:46:08 Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" 2009-11-20 10:46:08 winBlockHandler - Releasing pmServerStarted 2009-11-20 10:46:08 winBlockHandler - pthread_mutex_unlock () returned 2009-11-20 10:46:08 winProcEstablishConne
Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
On 19/11/2009 16:25, Michael Breuer wrote: For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. Could you tell me what the clipboard related error message is? Then I could perhaps try to fix it rather than tell everyone to use -noclipboard :-) One other point - as older versions of CygwinX have major issues (100% cpu) with the newer version of Gnome (now in F12), more people are going to be trying the beta and hitting this. Not sure what code is involved, but including this on the beta FAQ might be worthwhile. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: XWin stopped working with xorg-server 1.7.1 - no log-file created
For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. One other point - as older versions of CygwinX have major issues (100% cpu) with the newer version of Gnome (now in F12), more people are going to be trying the beta and hitting this. Not sure what code is involved, but including this on the beta FAQ might be worthwhile. Gertjan van Noord wrote: the DLL's are all there. Using the other poster's suggestion to use -noclipboard solves my problem, although I have no idea what/why. GJ On Thu, Nov 19, 2009 at 02:00:28PM +, Jon TURNEY wrote: On 19/11/2009 08:33, Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it identifies a missing DLL. -- 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/
Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
the DLL's are all there. Using the other poster's suggestion to use -noclipboard solves my problem, although I have no idea what/why. GJ On Thu, Nov 19, 2009 at 02:00:28PM +, Jon TURNEY wrote: > On 19/11/2009 08:33, Gertjan van Noord wrote: > > > >after upgrading to xorg-server 1.7.1-3 starting X does no longer > >work. Previous version 1.6.? worked. However, I can't seem to go > >back to that version using the cygwin setup programme. > > > >the startxwin.bat script does not complain, but no X logo appears, > >and indeed no X programs can be started. > > > >moreover no log-file is created in /var/log, which seems to suggest something > >very basic is going wrong? > > > >starting XWin from the command line, also with -logverbose 10 does not > >produce any output. > > > >rebooting does not change a thing > > > >I've attached my cygcheck.out > > You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it > identifies a missing DLL. -- 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: XWin stopped working with xorg-server 1.7.1 - no log-file created
On Thu, Nov 19, 2009 at 10:18:22AM -0500, Michael Breuer wrote: > Try -noclipboard. this solves my problem, many thanks. GJ > > I hit this as well. > Gertjan van Noord wrote: > >after upgrading to xorg-server 1.7.1-3 starting X does no longer > >work. Previous version 1.6.? worked. However, I can't seem to go > >back to that version using the cygwin setup programme. > > > >the startxwin.bat script does not complain, but no X logo appears, > >and indeed no X programs can be started. > > > >moreover no log-file is created in /var/log, which seems to suggest something > >very basic is going wrong? > > > >starting XWin from the command line, also with -logverbose 10 does not > >produce any output. > > > >rebooting does not change a thing > > > >I've attached my cygcheck.out > > > >GJ > > > > > > > > > >-- > >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/ > -- 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: XWin stopped working with xorg-server 1.7.1 - no log-file created
Try -noclipboard. I hit this as well. Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out GJ -- 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/
Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
On 19/11/2009 08:33, Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it identifies a missing DLL. -- 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/