From lisa_s_a@yahoo.ca Sat Dec 7 03:46:00 2013 From: lisa_s_a@yahoo.ca (Lisa Alexander) Date: Sat, 07 Dec 2013 03:46:00 -0000 Subject: X-startup-scripts Message-ID: <1386387994.50562.YahooMailBasic@web121905.mail.ne1.yahoo.com> Hello, I am trying to install X Cygwin and I need a package usually found under X11, named X-startup-scripts, but I can't seem to find it using the .exe installation program. Do you know where I can get this? Or has it been renamed? Thanks, Lisa -- 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/ From marco.atzeri@gmail.com Sat Dec 7 06:10:00 2013 From: marco.atzeri@gmail.com (marco atzeri) Date: Sat, 07 Dec 2013 06:10:00 -0000 Subject: X-startup-scripts In-Reply-To: <1386387994.50562.YahooMailBasic@web121905.mail.ne1.yahoo.com> References: <1386387994.50562.YahooMailBasic@web121905.mail.ne1.yahoo.com> Message-ID: <52A2BBBD.6020608@gmail.com> Il 12/7/2013 4:46 AM, Lisa Alexander ha scritto: > Hello, > > I am trying to install X Cygwin and I need a package usually found under X11, named X-startup-scripts, but I can't seem to find it using the .exe installation program. Do you know where I can get this? Or has it been renamed? http://cygwin.com/packages/x86/xinit/xinit-1.3.2-1 > > Thanks, > Lisa > Regards Marco -- 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/ From cre8tivspirit@live.com Mon Dec 9 14:37:00 2013 From: cre8tivspirit@live.com (Kevin Brown) Date: Mon, 09 Dec 2013 14:37:00 -0000 Subject: Restricting Port 6000 access in Cygwin/X Message-ID: My company recently sent an audit finding requesting for our Cygwin/X users with a finding of the following; "The remote host is running an X11 server.? X11 is a client-server protocol that can be used to display graphical applications running on a given host on a remote client.?? Since the X11 traffic is not ciphered, it is possible for an attacker to eavesdrop on the connection." The suggested solution was; "Restrict access to this port. If the X11 client/server facility is not used, disable TCP support in X11 entirely (-nolisten tcp)." My problem is that I haven't found any information that would help me accomplish this task. I've only recently taken over support of our Cygwin users and am not well versed in the software. Can this be done without breaking the functionality of the the software? If so, can you please advise on the steps to take to accomplish this? Current version being used is 1.7.11-1. Thanks, Kevin E. Brown Soli Deo Gloria! -- 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/ From jon.turney@dronecode.org.uk Mon Dec 9 15:27:00 2013 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 09 Dec 2013 15:27:00 -0000 Subject: Restricting Port 6000 access in Cygwin/X In-Reply-To: References: Message-ID: <52A5E17B.7010705@dronecode.org.uk> On 09/12/2013 14:37, Kevin Brown wrote: > My company recently sent an audit finding requesting for our Cygwin/X users > with a finding of the following; > > "The remote host is running an X11 server. X11 is a client-server protocol > that can be used to display graphical applications running on a given host > on a remote client. Since the X11 traffic is not ciphered, it is possible > for an attacker to eavesdrop on the connection." > > The suggested solution was; > > "Restrict access to this port. If the X11 client/server facility is not > used, disable TCP support in X11 entirely (-nolisten tcp)." > > > My problem is that I haven't found any information that would help me > accomplish this task. I've only recently taken over support of our Cygwin > users and am not well versed in the software. Can this be done without > breaking the functionality of the the software? If so, can you please > advise on the steps to take to accomplish this? The usual caveat applies: if you have an actual need for security, a random person on the internet is not where you should be getting your information. As suggested, if you start the X server with the option '-nolisten tcp' (see 'man Xserver'), then it will not accept remote connections. There's probably something to be said for this being the default configuration and requiring an explicit '-listen', but historically it's been this way. If you then need to connect to remote clients, use ssh forwarding, see [1]. [1] http://x.cygwin.com/docs/ug/using-remote-apps.html -- 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/ From jon.turney@dronecode.org.uk Tue Dec 10 21:08:00 2013 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 10 Dec 2013 21:08:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.14.4-2 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.14.4-2 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.14.4-1: * Fix a regression introduced in 1.14.3-2 which caused large X->Windows clipboard pastes to fail (Reported by Matthew D'Onofrio and Markus Hoenicka) x86: 1b301b4adf30bcd676ed17b646da739f *xorg-server-1.14.4-2-src.tar.xz a9267d8e8b0de27a855c32c70873e3ce *xorg-server-1.14.4-2.tar.xz fb8600efa64cba8104ab95fb3193e342 *xorg-server-common-1.14.4-2.tar.xz 7a6fcf8e459b2d47dbc41d898dd8e13c *xorg-server-debuginfo-1.14.4-2.tar.xz e15c9b3b9a93da9f703293a9a574b272 *xorg-server-devel-1.14.4-2.tar.xz d1f990416adbd2128932de395ff76b92 *xorg-server-dmx-1.14.4-2.tar.xz eb87c1306f2d61df637e6c7699578870 *xorg-server-extra-1.14.4-2.tar.xz e4e6ab9a97521a2a676f6a0be2917b62 *xwinclip-1.14.4-2.tar.xz x86_64: b5b4275491dd52340f5624816fe57800 *xorg-server-1.14.4-2-src.tar.xz f20699106bb72e6d00e54eb4074a4297 *xorg-server-1.14.4-2.tar.xz c90e7fa2bc08705b139d0220eef05195 *xorg-server-common-1.14.4-2.tar.xz 126717f83e68a7cb727e2fa8fe8d417c *xorg-server-debuginfo-1.14.4-2.tar.xz 21b1552b741b868a7d953a30ff319b85 *xorg-server-devel-1.14.4-2.tar.xz 4e48650aa07b8e8ca460ddcd5c45492a *xorg-server-dmx-1.14.4-2.tar.xz c826a17f6efaa7366443fbca3d659567 *xorg-server-extra-1.14.4-2.tar.xz 34157b2dc670ba3ec921deacdd1217f8 *xwinclip-1.14.4-2.tar.xz -- 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/ From jon.turney@dronecode.org.uk Wed Dec 11 01:27:00 2013 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 11 Dec 2013 01:27:00 -0000 Subject: ideas on how to debug an X server crash on Windows 8.1 (x64)? In-Reply-To: <4075.1386724429@freon.franz.com> References: <4075.1386724429@freon.franz.com> Message-ID: <52A7BF82.1040605@dronecode.org.uk> On 11/12/2013 01:13, Kevin Layer wrote: > I forgot to attach my XWin.0.log. Here it is: That log doesn't show any signs of a crash. If you install the xorg-server-debuginfo package, a possibly useful backtrace should be written to the log after a crash occurs. -- 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/ From layer@franz.com Wed Dec 11 03:11:00 2013 From: layer@franz.com (Kevin Layer) Date: Wed, 11 Dec 2013 03:11:00 -0000 Subject: ideas on how to debug an X server crash on Windows 8.1 (x64)? In-Reply-To: <52A7BF82.1040605@dronecode.org.uk> References: <4075.1386724429@freon.franz.com> <52A7BF82.1040605@dronecode.org.uk> Message-ID: <9253.1386731508@freon.franz.com> Jon, thanks for the reply. Jon TURNEY wrote: >> On 11/12/2013 01:13, Kevin Layer wrote: >> > I forgot to attach my XWin.0.log. Here it is: >> >> That log doesn't show any signs of a crash. >> >> If you install the xorg-server-debuginfo package, a possibly useful backtrace >> should be written to the log after a crash occurs. OK, done. And, curiously, the recipe I used 4 times to get the crash to happen doesn't reproduce it anymore. Next crash, send the crash report if there is one. Kevin -- 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/ From kbrown@cornell.edu Fri Dec 13 14:31:00 2013 From: kbrown@cornell.edu (Ken Brown) Date: Fri, 13 Dec 2013 14:31:00 -0000 Subject: gtk+ applications crash when filechooser opened In-Reply-To: References: Message-ID: <52AB1A51.9050906@cornell.edu> [This is a followup to http://cygwin.com/ml/cygwin/2013-12/msg00255.html; see also http://cygwin.com/ml/cygwin/2013-12/msg00146.html] On 12/13/2013 2:12 AM, Carl Michal wrote: > I recently started trying to port a gtk program to cygwin, and have > found that my program crashes everytime it tries to open a file chooser > widget. > > This doesn't happen with just my own programs, but also with gvim and > emacs-x11. Either will start up ok, but both crash as soon as File->Open > is selected. FWIW, here's one more data point. I can confirm this behavior of gvim and emacs-X11, but on x86 only. The File->Open dialog works fine in both gvim and emacs-X11 on x86_64. Ken -- 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/ From corinna-cygwin@cygwin.com Fri Dec 13 14:47:00 2013 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Fri, 13 Dec 2013 14:47:00 -0000 Subject: gtk+ applications crash when filechooser opened In-Reply-To: <52AB1A51.9050906@cornell.edu> References: <52AB1A51.9050906@cornell.edu> Message-ID: <20131213144744.GG9487@calimero.vinschen.de> On Dec 13 09:31, Ken Brown wrote: > [This is a followup to > http://cygwin.com/ml/cygwin/2013-12/msg00255.html; see also > http://cygwin.com/ml/cygwin/2013-12/msg00146.html] > > On 12/13/2013 2:12 AM, Carl Michal wrote: > >I recently started trying to port a gtk program to cygwin, and have > >found that my program crashes everytime it tries to open a file chooser > >widget. > > > >This doesn't happen with just my own programs, but also with gvim and > >emacs-x11. Either will start up ok, but both crash as soon as File->Open > >is selected. > > FWIW, here's one more data point. I can confirm this behavior of > gvim and emacs-X11, but on x86 only. The File->Open dialog works > fine in both gvim and emacs-X11 on x86_64. A crash at this point would indicate a broken value returned from *g_private_get_impl (key). It should be a valid pthread_key_t value but appears not to be one, for some reason. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From michal@physics.ubc.ca Fri Dec 13 19:02:00 2013 From: michal@physics.ubc.ca (Carl Michal) Date: Fri, 13 Dec 2013 19:02:00 -0000 Subject: gtk+ applications crash when filechooser opened In-Reply-To: <20131213144744.GG9487@calimero.vinschen.de> References: <52AB1A51.9050906@cornell.edu> <20131213144744.GG9487@calimero.vinschen.de> Message-ID: On Fri, 13 Dec 2013, Corinna Vinschen wrote: > On Dec 13 09:31, Ken Brown wrote: >> [This is a followup to >> http://cygwin.com/ml/cygwin/2013-12/msg00255.html; see also >> http://cygwin.com/ml/cygwin/2013-12/msg00146.html] >> >> On 12/13/2013 2:12 AM, Carl Michal wrote: >>> I recently started trying to port a gtk program to cygwin, and have >>> found that my program crashes everytime it tries to open a file chooser >>> widget. >>> >>> This doesn't happen with just my own programs, but also with gvim and >>> emacs-x11. Either will start up ok, but both crash as soon as File->Open >>> is selected. >> >> FWIW, here's one more data point. I can confirm this behavior of >> gvim and emacs-X11, but on x86 only. The File->Open dialog works >> fine in both gvim and emacs-X11 on x86_64. > > A crash at this point would indicate a broken value returned from > *g_private_get_impl (key). It should be a valid pthread_key_t > value but appears not to be one, for some reason. > What's interesting is that the call to open the filechooser hits this routine (g_private_get) a few times (through g_slice_alloc). If you don't try to step into pthread_getspecific, it crashes on the third time it is called. The same key is returned by g_private_get_impl every time. Trying to follow into pthread_getspecific gets really weird though. The debugger can't see the argument at all - says it doesn't exist in the current context. It appears that if I step into pthread_getspecific it crashes every time. I'm a little boggled here - there are 40 odd calls to pthread_getspecific that occur while my program starts up, and they appear to complete successfully, unless I try to follow with the debugger. This is from an early call to pthread_getspecific, that wouldn't crash if I wasn't running in the debugger: 0x6c62fe70 in pthread_getspecific () at /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/thread.cc:2617 2617 { gdb) list 2612 return 0; 2613 } 2614 2615 extern "C" void * 2616 pthread_getspecific (pthread_key_t key) 2617 { 2618 if (!pthread_key::is_good_object (&key)) 2619 return NULL; 2620 2621 return (key)->get (); (gdb) print key No symbol "key" in current context. (gdb) s /netrel/src/gdb-7.6.50-4/gdb/infrun.c:1942: internal-error: resume: Assertion `pc_in_thread_step_range (pc, tp)' failed. A problem internal to GDB has been detected, It crashes at line 2617 - before even getting to any of the code in the function! I haven't tried this on the 64 bit install, but will try to. Carl -- 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/ From jon.turney@dronecode.org.uk Mon Dec 30 22:29:00 2013 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 30 Dec 2013 22:29:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.14.5-1 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.14.5-1 These packages contain XWin and the other X.Org X11 servers. In addition to upstream fixes [1], this contains the following cygwin-specific changes since 1.14.4-2: * [source] Fix compilation issues due to wglext.h from current w32api-headers being older than current khronos-opengl-registry, by only generating wrappers for used WGL functions, rather than for all WGL functions in the khronos registry. * Add Windows 8.1, Windows Server 2012 R2 and Windows XP x64 to the list of Windows versions we know the name of x86: dce14b69416f4dd266e64259dd5608cd *xorg-server-1.14.5-1-src.tar.xz 7a6678e1faa65d68db2454d55d035fca *xorg-server-1.14.5-1.tar.xz c26482974b9d5489d45e7e3aa7f2ffa8 *xorg-server-common-1.14.5-1.tar.xz d10032aa8aef4232e985e1eb02fbcdd2 *xorg-server-debuginfo-1.14.5-1.tar.xz dccc65c582d969353e4240831372f6fe *xorg-server-devel-1.14.5-1.tar.xz fe4c78489e6292c15196ad2d4017b6e8 *xorg-server-dmx-1.14.5-1.tar.xz 5cda1742e20627e221d556a1247c5c34 *xorg-server-extra-1.14.5-1.tar.xz 7dc9c8ad2595c33a29950eeec9b357e7 *xwinclip-1.14.5-1.tar.xz x86_64: f443f626460c070ffa864388b4b313c1 *xorg-server-1.14.5-1-src.tar.xz bc2eada8deaa1a9302ba06467778f03f *xorg-server-1.14.5-1.tar.xz 315119e3b02fc24554a5ede0adfea5ad *xorg-server-common-1.14.5-1.tar.xz 9454005636a0d7e2e8a807ce845ef18a *xorg-server-debuginfo-1.14.5-1.tar.xz 983974d314c7bfe911cff24345cc130d *xorg-server-devel-1.14.5-1.tar.xz 29c1917eec35daa6b7526af4460b9bca *xorg-server-dmx-1.14.5-1.tar.xz 582293c6ee84bdd1b1cf5e94cf07ab32 *xorg-server-extra-1.14.5-1.tar.xz 0626211769fa5349491844649c56b912 *xwinclip-1.14.5-1.tar.xz [1] http://lists.x.org/archives/xorg-announce/2013-December/002380.html -- 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/