From andy.koppe@gmail.com Fri Apr 1 06:02:00 2011 From: andy.koppe@gmail.com (Andy Koppe) Date: Fri, 01 Apr 2011 06:02:00 -0000 Subject: mintty problem with "tail -f" on Windows XP with virtual desktops In-Reply-To: References: Message-ID: On 31 March 2011 19:45, Larry Breyer wrote: > I am really glad I switched from rxvt to mintty as it works great with or without X11. > I am seeing one problem, though, where I wonder if there is a fix. Mintty isn't actually an X11 program, so cygwin-xfree is the wrong list for this. Please send followups to the cygwin mailing list or the mintty discussion group. > I have observed the problem when switching between virtual desktops for both Windows > Desktop Manager and Dexpot Desktop Manager. By "Windows Desktop Manager" do you mean the "Virtual Desktop Manager" powertoy? Which Windows version are we talking about? > I frequently remote into servers and run "tail -f" to monitor various log files. > I have noticed when I switched to another virtual desktop, the mintty sessions > in the hidden virtual desktops do not get updated. ?When I switch back to the > desktop and hit the enter key within the mintty window it seems to catch up. > But, for some reason, the windows display gets jumbled. What exactly is getting jumbled and how? > Is there a way to refresh the window such that it looks normal without disturbing > the running process (tail)? There are several ways you could force a refresh of mintty's display: - minimize and restore - scroll up and down - flip screen and back (i.e. press Alt+F12 twice) However, none of that should be necessary, i.e. it sounds like there's a bug there somewhere. Do you have transparency enabled in mintty? Does disabling or enabling it make a difference? Regards, Andy -- 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 jjreisert@alum.mit.edu Fri Apr 1 16:06:00 2011 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Fri, 01 Apr 2011 16:06:00 -0000 Subject: xterm access violations (again) In-Reply-To: References: <20110322165117.N24352@mail101.his.com> <20110323171230.G30377@mail101.his.com> <1300929672.316.17.camel@YAAKOV04> <20110325052241.GA18053@ednor.casa.cgf.cx> <20110326183523.GA30114@ednor.casa.cgf.cx> Message-ID: On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote: > On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: > >> Could someone try this with the latest snapshot? ?I haven't made any >> changes but I just want to confirm that it still fails with something >> close to what will become Cygwin 1.7.9. >> >> http://cygwin.com/snapshots/ >> >> You just have to replace the DLL. ?Don't bother with a "cygwin-inst*" >> tarball. > > Yes, still there: How can I/we assist in debugging this problem? First we need to determine where the problem lies, whether it's in Cygwin itself, or xterm. Today it took me 3-4 tries to get an xterm up. As I was running late for work, it was kind of frustrating. -- Jim Reisert AD1C, , http://www.ad1c.us -- 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 Sat Apr 2 16:54:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 02 Apr 2011 16:54:00 -0000 Subject: X connection issues with Solaris CDE 1.6 In-Reply-To: References: Message-ID: <4D9754DB.2060204@dronecode.org.uk> On 01/04/2011 00:25, Gary R Buell wrote: > This apparently is a 1.5+ issue that still persists: Does this mean that the issue has been present since X server 1.5.0? Or do you mean since Cygwin 1.5? > I start an X session to connect to a Sun server and it takes 10-15 minutes > to get the login prompt. This is pretty likely to be waiting for something on the host you are trying to login to. Google's favourite answer is that host is spending that time trying to rDNS the address you are connecting from. The X server doesn't seem to be able to connect to the fontserver you are pointing it at, so you should be able to drop the -fp option, although I don't think that can be the cause of the delay. > I can login OK and can then work within an > existing xterm session. However, if I try to do anything on the CDE > desktop, the X session freezes. > > I have attached the log file. > Release: 1.8.2.0 (10802000) > Build Date: 2010-08-06 This X server release was superceded by 1.9.0-2 on 2010-10-23. The current X server release is 1.10.0-1. Your CDE freezing problem sounds a lot like upstream bugs [1] and [2], which I believe are resolved since 1.9.0, so you might like to try upgrading your X server. [1] https://bugs.freedesktop.org/show_bug.cgi?id=25400 [2] https://bugs.freedesktop.org/show_bug.cgi?id=27295 -- 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 Mon Apr 4 13:27:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 04 Apr 2011 13:27:00 -0000 Subject: xterm access violations (again) In-Reply-To: References: <20110322165117.N24352@mail101.his.com> <20110323171230.G30377@mail101.his.com> <1300929672.316.17.camel@YAAKOV04> <20110325052241.GA18053@ednor.casa.cgf.cx> <20110326183523.GA30114@ednor.casa.cgf.cx> Message-ID: <4D99C73F.7080708@dronecode.org.uk> On 01/04/2011 17:05, Jim Reisert AD1C wrote: > On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote: >> On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: >>> Could someone try this with the latest snapshot? I haven't made any >>> changes but I just want to confirm that it still fails with something >>> close to what will become Cygwin 1.7.9. >>> >>> http://cygwin.com/snapshots/ >>> >>> You just have to replace the DLL. Don't bother with a "cygwin-inst*" >>> tarball. >> >> Yes, still there: > > How can I/we assist in debugging this problem? First we need to > determine where the problem lies, whether it's in Cygwin itself, or > xterm. Today it took me 3-4 tries to get an xterm up. As I was > running late for work, it was kind of frustrating. I think you could: 1. Obtain the cygwin1.dbg file corresponding to your cygwin1.dll (for snapshots, it is available from the snapshot page, for releases, I believe it is in the corresponding cygwin src package), and place it next to your cygwin1.dll 2. Run xterm under gdb 3. Obtain a backtrace when the segv occurs 4. Diagnose the problem 5. Write and test a patch to fix it You'll probably want to refer to [1] for that last step. :-) [1] http://cygwin.com/contrib.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 cgf-use-the-mailinglist-please@cygwin.com Mon Apr 4 15:13:00 2011 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Mon, 04 Apr 2011 15:13:00 -0000 Subject: xterm access violations (again) In-Reply-To: <4D99C73F.7080708@dronecode.org.uk> References: <1300929672.316.17.camel@YAAKOV04> <20110325052241.GA18053@ednor.casa.cgf.cx> <20110326183523.GA30114@ednor.casa.cgf.cx> <4D99C73F.7080708@dronecode.org.uk> Message-ID: <20110404151251.GD1140@ednor.casa.cgf.cx> On Mon, Apr 04, 2011 at 02:27:27PM +0100, Jon TURNEY wrote: >On 01/04/2011 17:05, Jim Reisert AD1C wrote: >> On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote: >>> On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: >>>> Could someone try this with the latest snapshot? I haven't made any >>>> changes but I just want to confirm that it still fails with something >>>> close to what will become Cygwin 1.7.9. >>>> >>>> http://cygwin.com/snapshots/ >>>> >>>> You just have to replace the DLL. Don't bother with a "cygwin-inst*" >>>> tarball. >>> >>> Yes, still there: >> >> How can I/we assist in debugging this problem? First we need to >> determine where the problem lies, whether it's in Cygwin itself, or >> xterm. Today it took me 3-4 tries to get an xterm up. As I was >> running late for work, it was kind of frustrating. > >I think you could: > >1. Obtain the cygwin1.dbg file corresponding to your cygwin1.dll (for >snapshots, it is available from the snapshot page, for releases, I believe it >is in the corresponding cygwin src package), and place it next to your cygwin1.dll >2. Run xterm under gdb >3. Obtain a backtrace when the segv occurs >4. Diagnose the problem >5. Write and test a patch to fix it > >You'll probably want to refer to [1] for that last step. :-) > >[1] http://cygwin.com/contrib.html FWIW, I know what is causing the problem but not how to fix it. It's similar to http://cygwin.com/ml/cygwin/2011-04/msg00001.html Rebasing should fix that particular problem but it's not a panacea. cgf -- 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 richardvoigt@gmail.com Mon Apr 4 20:50:00 2011 From: richardvoigt@gmail.com (richardvoigt@gmail.com) Date: Mon, 04 Apr 2011 20:50:00 -0000 Subject: xterm access violations (again) In-Reply-To: <20110404151251.GD1140@ednor.casa.cgf.cx> References: <1300929672.316.17.camel@YAAKOV04> <20110325052241.GA18053@ednor.casa.cgf.cx> <20110326183523.GA30114@ednor.casa.cgf.cx> <4D99C73F.7080708@dronecode.org.uk> <20110404151251.GD1140@ednor.casa.cgf.cx> Message-ID: > FWIW, I know what is causing the problem but not how to fix it. ?It's > similar to > > http://cygwin.com/ml/cygwin/2011-04/msg00001.html > > Rebasing should fix that particular problem but it's not a panacea. The strace output in that other thread shows that GetLastError of 997 formerly caused some pipe handling functions deep in cygwin1.dll to return success and now is converted to an error. 997 is one of the rare non-zero success codes (in some sense). #define ERROR_IO_PENDING 997L Ben Voigt -- 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 viviendohoras@daiweb.info Wed Apr 6 14:52:00 2011 From: viviendohoras@daiweb.info (Mercedes) Date: Wed, 06 Apr 2011 14:52:00 -0000 Subject: Taller de teatro B.Norte/Palermo Message-ID: <20110406145146.520DF36E8128@daiweb.info> Taller de teatro.Al encuentro con nuestra creatividad... Distendity!!!! www.distendity.com.ar Laprida 1363, Y Santa Fe. Mi?rcoles de 19 a 21 hs. Cuota Mensual $180- Consultar programa. 4806-5990/4827-2522 viviendohoras@hotmail.com Saludos!! Se agradece difusi?n!!!!!! -------------- next part -------------- Taller de teatro.Al encuentro con nuestra creatividad... Distendity!!!! www.distendity.com.ar Laprida 1363, Y Santa Fe. Mi?rcoles de 19 a 21 hs. Cuota Mensual $180- Consultar programa. 4806-5990/4827-2522 viviendohoras@hotmail.com Saludos!! Se agradece difusi?n!!!!!! From ajay050@gmail.com Sat Apr 9 10:41:00 2011 From: ajay050@gmail.com (Ajay Jain) Date: Sat, 09 Apr 2011 10:41:00 -0000 Subject: Arrow Keys & Bash Shortcuts do not work Message-ID: Hi, I am in a fix. My arrow keys (left, right, up, down, Alt-F, Alt-B, Ctrl-P, Ctrl-N ) do not work. What should I do? I tried looking on the net, but there is no clear way out. Then I opened cygiwn (c:\cygwin\cygwin.bat). I did the following: cygcheck -k Left Arrow - Pressed 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Released 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Right Arrow - Pressed 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Released 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Up Arrow - Pressed 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Released 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Down Arrow - Pressed 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Released 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- Then I pressed Ctrl-V Left Arrow, Ctrl-V Right Arrow, Ctrl-V Up Arrow, Ctrl-V Bottom Arrow and I get: ^[[D^[[C^[[A^[[B What should I do? I expect that the keys should work out of box. Regards, Ajay. A -- 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 cgf-use-the-mailinglist-please@cygwin.com Sat Apr 9 16:21:00 2011 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Sat, 09 Apr 2011 16:21:00 -0000 Subject: Arrow Keys & Bash Shortcuts do not work In-Reply-To: References: Message-ID: <20110409162145.GB29135@ednor.casa.cgf.cx> On Sat, Apr 09, 2011 at 04:10:58PM +0530, Ajay Jain wrote: >Hi, > >I am in a fix. My arrow keys (left, right, up, down, Alt-F, Alt-B, >Ctrl-P, Ctrl-N ) do not work. > >What should I do? I tried looking on the net, but there is no clear way out. > >Then I opened cygiwn (c:\cygwin\cygwin.bat). > >I did the following: > >cygcheck -k > >Left Arrow - Pressed 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- >-- -- -- -- -- >Released 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- > >Right Arrow - Pressed 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- >-- -- -- -- -- >Released 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- > >Up Arrow - Pressed 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- >-- -- -- -- >Released 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- > >Down Arrow - Pressed 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- >-- -- -- -- -- >Released 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- > >Then I pressed Ctrl-V Left Arrow, Ctrl-V Right Arrow, Ctrl-V Up Arrow, >Ctrl-V Bottom Arrow and I get: > >^[[D^[[C^[[A^[[B > >What should I do? I expect that the keys should work out of box. Nothing above illustrates the arror keys not working. Please follow the instructions here: http://cygwin.com/problems.html We will need cygcheck output but you also need to consider that we don't know what you mean by "do not work". As a wild guess, however, it sounds like you have improperly set your TERM environment variable. -- 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 cgf-use-the-mailinglist-please@cygwin.com Sat Apr 9 17:08:00 2011 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Sat, 09 Apr 2011 17:08:00 -0000 Subject: Arrow Keys & Bash Shortcuts do not work In-Reply-To: <20110409162145.GB29135@ednor.casa.cgf.cx> References: <20110409162145.GB29135@ednor.casa.cgf.cx> Message-ID: <20110409170834.GC29135@ednor.casa.cgf.cx> On Sat, Apr 09, 2011 at 12:21:45PM -0400, Christopher Faylor wrote: >On Sat, Apr 09, 2011 at 04:10:58PM +0530, Ajay Jain wrote: >>Hi, >> >>I am in a fix. My arrow keys (left, right, up, down, Alt-F, Alt-B, >>Ctrl-P, Ctrl-N ) do not work. >> >>What should I do? I tried looking on the net, but there is no clear way out. >> >>Then I opened cygiwn (c:\cygwin\cygwin.bat). >> >>I did the following: >> >>cygcheck -k >> >>Left Arrow - Pressed 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- >>-- -- -- -- -- >>Released 1x VK: 0x25 VS: 0x4b A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- >> >>Right Arrow - Pressed 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- >>-- -- -- -- -- >>Released 1x VK: 0x27 VS: 0x4d A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- >> >>Up Arrow - Pressed 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- >>-- -- -- -- >>Released 1x VK: 0x26 VS: 0x48 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- >> >>Down Arrow - Pressed 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- >>-- -- -- -- -- >>Released 1x VK: 0x28 VS: 0x50 A: 0x00 CTRL: -- EK -- -- -- -- -- -- -- >> >>Then I pressed Ctrl-V Left Arrow, Ctrl-V Right Arrow, Ctrl-V Up Arrow, >>Ctrl-V Bottom Arrow and I get: >> >>^[[D^[[C^[[A^[[B >> >>What should I do? I expect that the keys should work out of box. > >Nothing above illustrates the arror keys not working. arrow -- 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 JOEL.MOOTS@L-3com.com Wed Apr 13 14:49:00 2011 From: JOEL.MOOTS@L-3com.com (JOEL.MOOTS@L-3com.com) Date: Wed, 13 Apr 2011 14:49:00 -0000 Subject: Initial XWin desktop placement Message-ID: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> Hi, I feel like this question was answered on the list previously but could not find it. I run XWin with two screens on multiple monitors (i.e., "XWin :4 -nodecoration -multiplemonitors -screen 0 1600 1200 -screen 1 1600 1200") and at one point got it to remember to place both screens on my secondary monitor. After switching my monitor setup recently, it now always pops up the screens on my primary monitor. I've searched my registry (for cygwin and xwin) but could not find where it was storing the initial locations. After moving the screens to where I want them, I've tried various means of shutting down XWin.exe but it does not remember the locations. This is a Windows XP machine, if that matters. Any help would be appreciated, TIA, -joel moots -- 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 jonathan.david.conrad@gmail.com Wed Apr 13 15:55:00 2011 From: jonathan.david.conrad@gmail.com (Jonathan Conrad) Date: Wed, 13 Apr 2011 15:55:00 -0000 Subject: Initial XWin desktop placement In-Reply-To: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> References: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> Message-ID: On Wed, Apr 13, 2011 at 10:49 AM, wrote: ... > always pops up the screens on my primary monitor. I've searched my > registry (for cygwin and xwin) but could not find where it was storing ... I would love to become an expert on the subject of Cygwin and X and Windows XP but am becoming more out of touch, as it were. I recently followed a link from this mailing list to get started with the Cygcheck utility and noticed that there are more than a couple of entries in the registry. Anyway, as Cygwin is a sort of a POSIX environment, there is very little dependence on the message-driven paradigm of Windows programming and even less on the registry and problems with case-insensitivity and registered filename extensions. Server processes (such as the X Window System) are configured with text files which are mainly located in your home directory and the "C:/cygwin/etc" and /usr/share and /lib folders. It is unfortunately beyond the scope of an Linux emulator to fathom all of the facilities of X. Hopefully, another reader will tell you more exactly where to start. I'll be back. - http://facebook.com/FNORDLY -- 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 Apr 13 16:46:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 13 Apr 2011 16:46:00 -0000 Subject: Initial XWin desktop placement In-Reply-To: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> References: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> Message-ID: <4DA5D379.3000300@dronecode.org.uk> On 13/04/2011 15:49, JOEL.MOOTS@L-3com.com wrote: > I feel like this question was answered on the list previously but could > not find it. I run XWin with two screens on multiple monitors (i.e., > "XWin :4 -nodecoration -multiplemonitors -screen 0 1600 1200 -screen 1 > 1600 1200") and at one point got it to remember to place both screens on > my secondary monitor. After switching my monitor setup recently, it now > always pops up the screens on my primary monitor. I've searched my > registry (for cygwin and xwin) but could not find where it was storing > the initial locations. After moving the screens to where I want them, > I've tried various means of shutting down XWin.exe but it does not > remember the locations. This is a Windows XP machine, if that matters. The description of the -screen option in 'man XWin' should clear all this up. XWin doesn't store the position of the screen windows anywhere, it places them where you request them. If you just specify a height and width and no position in the -screen option, the screen window is placed at the top-left of the Windows virtual desktop. I guess perhaps you've switched from a setup with the primary monitor on the right to one with the primary monitor on the left, hence the window is now located on your primary monitor? (It could perhaps be made clearer that a normalized coordinate space is used for specifying the screen window position, where (0,0) is the top-left of the Windows virtual desktop, which is not the same as the Windows virtual desktop coordinate space (which has (0,0) at the top-left of the primary monitor), to avoid negative coordinates.) To place a screen window on the secondary monitor, I'd suggest you use the syntax '-nodecoration -screen 0 @2'. (You shouldn't need to use -multiplemonitors, as it isn't doing anything much for you, since all it should do is set the size of screen 0 to match the Windows virtual desktop, which you are then overriding with an explicitly specified screen size, but experimenting a bit, it looks like there is a bug at the moment, in that, when -multiplemonitors isn't specified, the screen window size is always constrained to fit the usable area of the primary monitor (rather than the usable area of the specified monitor), so you will need to specify -mutliplemonitors and the window size if you want a screen the same size as your secondary monitor and your secondary monitors is larger than your primary monitor, e.g. '-nodecoration -multiplemonitors -screen 0 1600x1200@2'.) -- 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 JOEL.MOOTS@L-3com.com Wed Apr 13 17:00:00 2011 From: JOEL.MOOTS@L-3com.com (JOEL.MOOTS@L-3com.com) Date: Wed, 13 Apr 2011 17:00:00 -0000 Subject: Initial XWin desktop placement In-Reply-To: <4DA5D379.3000300@dronecode.org.uk> References: <615935CE76907149AFEC6599C969D4D5046EAB0D@XCGTXH01.corp.eos.l-3com.com> <4DA5D379.3000300@dronecode.org.uk> Message-ID: <615935CE76907149AFEC6599C969D4D5046EAB0F@XCGTXH01.corp.eos.l-3com.com> > From: Jon TURNEY > Sent: Wednesday, April 13, 2011 9:47 AM > To place a screen window on the secondary monitor, I'd suggest you > use the > syntax '-nodecoration -screen 0 @2'. Wow. I don't see that @ syntax listed in the man page for my very outdated Cygwin/X, and that's obviously not how I got it to "remember" before, but you just made my day! Thank you very, very much, -joel -- 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 davidmichaelkarr@gmail.com Sun Apr 17 22:30:00 2011 From: davidmichaelkarr@gmail.com (David M. Karr) Date: Sun, 17 Apr 2011 22:30:00 -0000 Subject: Tried to fix "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server Message-ID: <4DAB6A08.7060002@gmail.com> Cygwin 1.7.8 (and 1.7.9), Win7SP1. I was having issues with my Emacs startup occasionally failing with "Doing vfork: resource temporarily unavailable". I found a link that alleged to have the solution to this (http://blog.cottee.org/2008/05/cygwin-emacs-problems.html). I followed these steps, although when I looked at "libncurses7", I saw it was set to "Skip", and that I had versions 8, 9, and 10. So, I set those to reinstall and continued the update. It also updated some other things, including updating me from Cygwin 1.7.8 to 1.7.9. Now, when I run "startxwin", it chugs for a bit and then presents an error dialog saying "Failed to activate core devices". The log file contents follows this. It fails like this every time now. ----------------------------------- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.10.0.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] Package version 1.10.0-1 built 2011-03-15 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeDefaultScreens - native DPI x 96 y 96 [ 46.020] (II) xorg.conf is not supported [ 46.020] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 46.020] LoadPreferences: /home/David/.XWinrc not found [ 46.020] LoadPreferences: Loading /etc/X11/system.XWinrc [ 46.020] LoadPreferences: Done parsing the configuration file... [ 50.419] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [ 50.419] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 50.419] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 50.466] winDetectSupportedEngines - Returning, supported engines 0000001f [ 50.466] winSetEngine - Multi Window or Rootless => ShadowGDI [ 50.466] winScreenInit - Using Windows display depth of 32 bits per pixel [ 50.466] winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32 [ 50.466] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 50.466] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 50.466] winInitMultiWindowWM - Calling pthread_mutex_lock () [ 50.466] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 50.466] Screen 0 added at virtual desktop coordinate (0,0). [ 52.541] MIT-SHM extension disabled due to lack of kernel support [ 52.541] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 53.102] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [ 53.102] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 53.165] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [ 53.165] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [ 53.523] (EE) XKB: Could not invoke xkbcomp [ 53.523] (EE) XKB: Couldn't compile keymap [ 53.523] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 53.633] (EE) XKB: Could not invoke xkbcomp [ 53.633] (EE) XKB: Couldn't compile keymap [ 53.633] XKB: Failed to compile keymap [ 53.633] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 53.633] Fatal server error: [ 53.633] Failed to activate core devices. -- 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 Mon Apr 18 12:13:00 2011 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 18 Apr 2011 12:13:00 -0000 Subject: Tried to fix "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server In-Reply-To: <4DAB6A08.7060002@gmail.com> References: <4DAB6A08.7060002@gmail.com> Message-ID: <4DAC2ABD.6000702@cornell.edu> On 4/17/2011 6:30 PM, David M. Karr wrote: > Cygwin 1.7.8 (and 1.7.9), Win7SP1. > > I was having issues with my Emacs startup occasionally failing with > "Doing vfork: resource temporarily unavailable". I found a link that > alleged to have the solution to this > (http://blog.cottee.org/2008/05/cygwin-emacs-problems.html). The advice about libncurses on that page is obsolete. It applied to old versions of emacs. The suggestion of running rebaseall is good but... > I followed these steps, although when I looked at "libncurses7", I saw > it was set to "Skip", and that I had versions 8, 9, and 10. So, I set > those to reinstall and continued the update. It also updated some other > things, including updating me from Cygwin 1.7.8 to 1.7.9. you should try rebaseall now. 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 vterekhina@psmconsulting.ru Tue Apr 19 21:10:00 2011 From: vterekhina@psmconsulting.ru (Severina) Date: Tue, 19 Apr 2011 21:10:00 -0000 Subject: =?UTF-8?B?QmxpZcW+YW1pZSwgZHLEgXRl?= un, =?UTF-8?B?bG/Eo2lza2ksIGNvcGVzdsSrcnUgcGllZHrEq3ZvanVtaQ==?= Message-ID: Apr????a numur?? lasi lieliskus aprakstus par p??ris ve??u erekcijas probl??m??m un to, k?? tie varo??i ar to c??n??j??s. T??pat ieg??sti info, kur nopirkt labus med-preper??tus, un k?? ??am??jiem g??ja ribalk?? Peipus??. Iesaku izlas??t m??su galvaspils??tas iznes??g??ko mauku knieb??ju st??stus par saviem piedz??vojumiem! palasi to te: http://www.lieliskaisvirietis.lv -- 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 davidmichaelkarr@gmail.com Thu Apr 21 01:02:00 2011 From: davidmichaelkarr@gmail.com (David M. Karr) Date: Thu, 21 Apr 2011 01:02:00 -0000 Subject: Tried to fix "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server In-Reply-To: <4DAC2ABD.6000702@cornell.edu> References: <4DAB6A08.7060002@gmail.com> <4DAC2ABD.6000702@cornell.edu> Message-ID: <4DAF8212.5090305@gmail.com> On 4/18/2011 5:12 AM, Ken Brown wrote: > On 4/17/2011 6:30 PM, David M. Karr wrote: >> Cygwin 1.7.8 (and 1.7.9), Win7SP1. >> >> I was having issues with my Emacs startup occasionally failing with >> "Doing vfork: resource temporarily unavailable". I found a link that >> alleged to have the solution to this >> (http://blog.cottee.org/2008/05/cygwin-emacs-problems.html). > > The advice about libncurses on that page is obsolete. It applied to > old versions of emacs. The suggestion of running rebaseall is good > but... > >> I followed these steps, although when I looked at "libncurses7", I saw >> it was set to "Skip", and that I had versions 8, 9, and 10. So, I set >> those to reinstall and continued the update. It also updated some other >> things, including updating me from Cygwin 1.7.8 to 1.7.9. > > you should try rebaseall now. > I tried to reply to this a while ago, but it never showed up on the list. This didn't fix the problem. I still can't start the X server. It fails with "Failed to activate core devices". Here is the log output: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.10.0.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] Package version 1.10.0-1 built 2011-03-15 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeDefaultScreens - native DPI x 96 y 96 [181003.592] (II) xorg.conf is not supported [181003.592] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [181003.592] LoadPreferences: /home/David/.XWinrc not found [181003.592] LoadPreferences: Loading /etc/X11/system.XWinrc [181003.592] LoadPreferences: Done parsing the configuration file... [181003.654] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [181003.654] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [181003.654] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [181003.763] winDetectSupportedEngines - Returning, supported engines 0000001f [181003.763] winSetEngine - Multi Window or Rootless => ShadowGDI [181003.763] winScreenInit - Using Windows display depth of 32 bits per pixel [181003.779] winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32 [181003.779] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [181003.779] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [181003.779] winInitMultiWindowWM - Calling pthread_mutex_lock () [181003.779] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [181003.779] Screen 0 added at virtual desktop coordinate (0,0). [181003.779] MIT-SHM extension disabled due to lack of kernel support [181003.794] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [181003.826] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [181003.826] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [181003.841] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [181003.841] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [181003.966] (EE) XKB: Could not invoke xkbcomp [181003.966] (EE) XKB: Couldn't compile keymap [181003.966] (EE) XKB: Failed to load keymap. Loading default keymap instead. [181004.091] (EE) XKB: Could not invoke xkbcomp [181004.091] (EE) XKB: Couldn't compile keymap [181004.091] XKB: Failed to compile keymap [181004.091] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [181004.091] Fatal server error: [181004.091] Failed to activate core devices. -- 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 jbugden@amh.net.au Thu Apr 21 07:20:00 2011 From: jbugden@amh.net.au (Jesse Bugden) Date: Thu, 21 Apr 2011 07:20:00 -0000 Subject: Latest Cygwin X hangs when mouse is used to highlight text Message-ID: <4DAFDA9E.4050308@amh.net.au> Hi, I am not a cygwin user. I am troubleshooting an issue with an old version of Adobe Framemaker (7.0) and I came across your thread in my googling. I wonder if it has some similarities. Our problem is that highlighting text causes the program to become non-responsive. I have found that our problem appears to be related to dwm.exe (to do with Aero). I would be interested to see if you can replicate the problem and 'remedy' it by going into the task manager and killing the dwm.exe process (it should restart itself automatically). You might find that disabling aero fixes your problem. For interest's sake I should mention (although we are still in the early stages of dealing with the problem) that we have been able to reproduce the problem on two of our intel h55 chipset boards with core i5 graphics. The other test machine with nVidia graphics did not have the problem. Hope this helps. Regards Jesse Bugden -- 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 tarwati@gmail.com Fri Apr 22 01:34:00 2011 From: tarwati@gmail.com (tarwati@gmail.com) Date: Fri, 22 Apr 2011 01:34:00 -0000 Subject: Plus de 40 000 backlinks de qualite Message-ID: Cher Webmaster. Gagnez du temps Enregistrer effort economiser de l argent = Obtenir votre objectif Professional Software semi-automatique Directory Submitter Plus de 40 000 backlinks de qualite: http://superdirectorysubmitter.com/index.php?fm=13 Ameliorez votre classement sur moteurs de recherche. Nouveau et Meilleur Software SEO: Super Directory Submitter Ce que cepouvez faire pour votre site web? Donnez 40000 backlinks vers votre site et une position elevee dans les moteurs de recherche. eventail grande popularite. plus de visiteurs. et plus de ventes... -- 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 Sat Apr 23 12:57:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 23 Apr 2011 12:57:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.10.1-1 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.10.1-1 *** xorg-server-dmx-1.10.1-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.10.0-1: * Correctly handle user log-off or shutdown, exiting cleanly and removing any lockfile and unix domain socket. I'm doubtful WM_ENDSESSION handling has ever worked properly before (as reported by numerous people over the years) * Allow XScreenSaverSuspend() to also suspend Windows screen saver or monitor power off (sourceware bugzilla #11563) * Bug fixes for screen windows sized to a non-primary monitor's size: (i) size to the chosen monitor's work area, not the primary monitor's work area (ii) only reduce the size by one pixel to allow for an auto-hide taskbar if an auto-hide taskbar is on that monitor. * In multiwindow mode, don't grab the Windows input focus for new X windows which hint they don't want it * Add items to the default tray icon menu to open the logfile, FAQ and User's Guide * Report if OS is WoW64 or not when reporting OS version in log * Remove some ancient pre-NT4 compatibility cruft 01af92713085e3d7991a4e12f963f8b4 *xorg-server-1.10.1-1.tar.bz2 73bc1317dddbd6c2b983c01a6b8bfb3a *xorg-server-dmx-1.10.1-1.tar.bz2 d3d1567371f174e42541fb2243cf9d80 *xorg-server-1.10.1-1-src.tar.bz2 [1] http://lists.freedesktop.org/archives/xorg-announce/2011-April/001646.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 davidmichaelkarr@gmail.com Sat Apr 23 16:47:00 2011 From: davidmichaelkarr@gmail.com (David M. Karr) Date: Sat, 23 Apr 2011 16:47:00 -0000 Subject: Still can't run XServer or any apps that require it Message-ID: <4DB302A9.1090105@gmail.com> Cygwin 1.7.9 on Win7SP1. Almost a week ago now, I've been unable to run my XServer, and thus any of the apps that normally run with it, like Emacs. When I run "startxwin", it just says "failed to activate core devices". Here's the XWin.0.log: -------------------------------- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.10.1.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win32) Package: version 1.10.1-1 built 2011-04-22 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeDefaultScreens - native DPI x 96 y 96 [498341.590] (II) xorg.conf is not supported [498341.590] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [498341.590] LoadPreferences: /home/David/.XWinrc not found [498341.590] LoadPreferences: Loading /etc/X11/system.XWinrc [498341.605] LoadPreferences: Done parsing the configuration file... [498341.652] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [498341.652] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [498341.652] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [498341.730] winDetectSupportedEngines - Returning, supported engines 0000001f [498341.730] winSetEngine - Multi Window or Rootless => ShadowGDI [498341.730] winScreenInit - Using Windows display depth of 32 bits per pixel [498341.746] winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32 [498341.746] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [498341.746] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [498341.746] winInitMultiWindowWM - Calling pthread_mutex_lock () [498341.761] Screen 0 added at virtual desktop coordinate (0,0). [498341.761] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [498341.761] MIT-SHM extension disabled due to lack of kernel support [498341.761] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [498341.808] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [498341.808] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [498341.808] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [498341.808] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [498341.949] (EE) XKB: Could not invoke xkbcomp [498341.949] (EE) XKB: Couldn't compile keymap [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead. [498342.089] (EE) XKB: Could not invoke xkbcomp [498342.089] (EE) XKB: Couldn't compile keymap [498342.089] XKB: Failed to compile keymap [498342.089] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [498342.089] Fatal server error: [498342.089] Failed to activate core devices. ------------------------------ I looked in the FAQ for the entry corresponding to this error, but none of the steps found any issues. I've tried doing "rebaseall" according to the instructions, but that hasn't made any difference. In fact, my problems started when I ran "rebaseall" to fix a different problem. I was getting "Doing vfork: resource temporarily unavailable" when I started up Emacs, and some advice I found suggested running "rebaseall". I've run "cygcheck -c" and got all OK. I ran "cygcheck -s" and the only part that seemed vaguely suspicious was this excerpt: 12k 2010/08/03 C:\/usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. cygwin\bin\cygXcomposite-1.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/ From jon.turney@dronecode.org.uk Mon Apr 25 15:23:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 25 Apr 2011 15:23:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB302A9.1090105@gmail.com> References: <4DB302A9.1090105@gmail.com> Message-ID: <4DB5920C.9010202@dronecode.org.uk> On 23/04/2011 17:47, David M. Karr wrote: > Almost a week ago now, I've been unable to run my XServer, and thus any of the > apps that normally run with it, like Emacs. I realise this situation is an inconvenience, but please don't post to multiple lists just because you don't get a quick response. > When I run "startxwin", it just > says "failed to activate core devices". [snip] > [498341.949] (EE) XKB: Could not invoke xkbcomp > [498341.949] (EE) XKB: Couldn't compile keymap > [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [498342.089] (EE) XKB: Could not invoke xkbcomp > [498342.089] (EE) XKB: Couldn't compile keymap > [498342.089] XKB: Failed to compile keymap > [498342.089] Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > [498342.089] Fatal server error: Failed to activate core devices. > ------------------------------ > > I looked in the FAQ for the entry corresponding to this error, but none of the > steps found any issues. I've tried doing "rebaseall" according to the > instructions, but that hasn't made any difference. In fact, my problems > started when I ran "rebaseall" to fix a different problem. I was getting > "Doing vfork: resource temporarily unavailable" when I started up Emacs, and > some advice I found suggested running "rebaseall". Unfortunately, rebaseall is a rather limited workaround, rather than a solution for these issues (for reasons which have been discussed extensively in the past) There has been a recent cygwin DLL change which *might* help in this situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if that makes a difference. (I wouldn't recommend later ones as they seem to have a regression in a different area) [1] http://cygwin.com/snapshots/ -- 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 cgf-use-the-mailinglist-please@cygwin.com Mon Apr 25 17:07:00 2011 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Mon, 25 Apr 2011 17:07:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB5920C.9010202@dronecode.org.uk> References: <4DB302A9.1090105@gmail.com> <4DB5920C.9010202@dronecode.org.uk> Message-ID: <20110425170715.GB3841@ednor.casa.cgf.cx> On Mon, Apr 25, 2011 at 04:23:56PM +0100, Jon TURNEY wrote: >On 23/04/2011 17:47, David M. Karr wrote: >> Almost a week ago now, I've been unable to run my XServer, and thus any of the >> apps that normally run with it, like Emacs. > >I realise this situation is an inconvenience, but please don't post to >multiple lists just because you don't get a quick response. > >> When I run "startxwin", it just >> says "failed to activate core devices". >[snip] >> [498341.949] (EE) XKB: Could not invoke xkbcomp >> [498341.949] (EE) XKB: Couldn't compile keymap >> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead. >> [498342.089] (EE) XKB: Could not invoke xkbcomp >> [498342.089] (EE) XKB: Couldn't compile keymap >> [498342.089] XKB: Failed to compile keymap >> [498342.089] Keyboard initialization failed. This could be a missing or >> incorrect setup of xkeyboard-config. >> [498342.089] Fatal server error: Failed to activate core devices. >> ------------------------------ >> >> I looked in the FAQ for the entry corresponding to this error, but none of the >> steps found any issues. I've tried doing "rebaseall" according to the >> instructions, but that hasn't made any difference. In fact, my problems >> started when I ran "rebaseall" to fix a different problem. I was getting >> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and >> some advice I found suggested running "rebaseall". > >Unfortunately, rebaseall is a rather limited workaround, rather than a >solution for these issues (for reasons which have been discussed extensively >in the past) > >There has been a recent cygwin DLL change which *might* help in this >situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if >that makes a difference. (I wouldn't recommend later ones as they seem to have >a regression in a different area) > >[1] http://cygwin.com/snapshots/ Also, I've found that using a different base address with rebaseall seems to help with some X problems: dash -c "rebaseall -b 0x77000000" http://cygwin.com/ml/cygwin/2011-04/msg00306.html cgf -- 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 davidmichaelkarr@gmail.com Tue Apr 26 01:32:00 2011 From: davidmichaelkarr@gmail.com (David M. Karr) Date: Tue, 26 Apr 2011 01:32:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB5920C.9010202@dronecode.org.uk> References: <4DB302A9.1090105@gmail.com> <4DB5920C.9010202@dronecode.org.uk> Message-ID: <4DB620B2.7020805@gmail.com> On 4/25/2011 8:23 AM, Jon TURNEY wrote: > On 23/04/2011 17:47, David M. Karr wrote: >> Almost a week ago now, I've been unable to run my XServer, and thus any of the >> apps that normally run with it, like Emacs. > I realise this situation is an inconvenience, but please don't post to > multiple lists just because you don't get a quick response. I didn't do that entirely because I hadn't seen a response. I considered the possibility that this was caused by an issue outside of the X server itself. >> When I run "startxwin", it just >> says "failed to activate core devices". > [snip] >> [498341.949] (EE) XKB: Could not invoke xkbcomp >> [498341.949] (EE) XKB: Couldn't compile keymap >> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead. >> [498342.089] (EE) XKB: Could not invoke xkbcomp >> [498342.089] (EE) XKB: Couldn't compile keymap >> [498342.089] XKB: Failed to compile keymap >> [498342.089] Keyboard initialization failed. This could be a missing or >> incorrect setup of xkeyboard-config. >> [498342.089] Fatal server error: Failed to activate core devices. >> ------------------------------ >> >> I looked in the FAQ for the entry corresponding to this error, but none of the >> steps found any issues. I've tried doing "rebaseall" according to the >> instructions, but that hasn't made any difference. In fact, my problems >> started when I ran "rebaseall" to fix a different problem. I was getting >> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and >> some advice I found suggested running "rebaseall". > Unfortunately, rebaseall is a rather limited workaround, rather than a > solution for these issues (for reasons which have been discussed extensively > in the past) > > There has been a recent cygwin DLL change which *might* help in this > situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if > that makes a difference. (I wouldn't recommend later ones as they seem to have > a regression in a different area) > > [1] http://cygwin.com/snapshots/ Thanks, I'll move towards that. -- 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 davidmichaelkarr@gmail.com Tue Apr 26 05:16:00 2011 From: davidmichaelkarr@gmail.com (David M. Karr) Date: Tue, 26 Apr 2011 05:16:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <20110425170715.GB3841@ednor.casa.cgf.cx> References: <4DB302A9.1090105@gmail.com> <4DB5920C.9010202@dronecode.org.uk> <20110425170715.GB3841@ednor.casa.cgf.cx> Message-ID: <4DB6551C.30309@gmail.com> On 4/25/2011 10:07 AM, Christopher Faylor wrote: > On Mon, Apr 25, 2011 at 04:23:56PM +0100, Jon TURNEY wrote: >> On 23/04/2011 17:47, David M. Karr wrote: >>> Almost a week ago now, I've been unable to run my XServer, and thus any of the >>> apps that normally run with it, like Emacs. >> I realise this situation is an inconvenience, but please don't post to >> multiple lists just because you don't get a quick response. >> >>> When I run "startxwin", it just >>> says "failed to activate core devices". >> [snip] >>> [498341.949] (EE) XKB: Could not invoke xkbcomp >>> [498341.949] (EE) XKB: Couldn't compile keymap >>> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead. >>> [498342.089] (EE) XKB: Could not invoke xkbcomp >>> [498342.089] (EE) XKB: Couldn't compile keymap >>> [498342.089] XKB: Failed to compile keymap >>> [498342.089] Keyboard initialization failed. This could be a missing or >>> incorrect setup of xkeyboard-config. >>> [498342.089] Fatal server error: Failed to activate core devices. >>> ------------------------------ >>> >>> I looked in the FAQ for the entry corresponding to this error, but none of the >>> steps found any issues. I've tried doing "rebaseall" according to the >>> instructions, but that hasn't made any difference. In fact, my problems >>> started when I ran "rebaseall" to fix a different problem. I was getting >>> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and >>> some advice I found suggested running "rebaseall". >> Unfortunately, rebaseall is a rather limited workaround, rather than a >> solution for these issues (for reasons which have been discussed extensively >> in the past) >> >> There has been a recent cygwin DLL change which *might* help in this >> situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if >> that makes a difference. (I wouldn't recommend later ones as they seem to have >> a regression in a different area) >> >> [1] http://cygwin.com/snapshots/ > Also, I've found that using a different base address with rebaseall > seems to help with some X problems: > > dash -c "rebaseall -b 0x77000000" > > http://cygwin.com/ml/cygwin/2011-04/msg00306.html > Ok, that appears to have fixed my problem. Is that a "permanent" fix? -- 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 reply-to-list-only-lh@cygwin.com Tue Apr 26 15:37:00 2011 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Tue, 26 Apr 2011 15:37:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB6551C.30309@gmail.com> References: <4DB302A9.1090105@gmail.com> <4DB5920C.9010202@dronecode.org.uk> <20110425170715.GB3841@ednor.casa.cgf.cx> <4DB6551C.30309@gmail.com> Message-ID: <4DB6E69F.6030706@cygwin.com> On 4/26/2011 1:16 AM, David M. Karr wrote: > On 4/25/2011 10:07 AM, Christopher Faylor wrote: >> On Mon, Apr 25, 2011 at 04:23:56PM +0100, Jon TURNEY wrote: >>> On 23/04/2011 17:47, David M. Karr wrote: >>>> Almost a week ago now, I've been unable to run my XServer, and thus any >>>> of the >>>> apps that normally run with it, like Emacs. >>> I realise this situation is an inconvenience, but please don't post to >>> multiple lists just because you don't get a quick response. >>> >>>> When I run "startxwin", it just >>>> says "failed to activate core devices". >>> [snip] >>>> [498341.949] (EE) XKB: Could not invoke xkbcomp >>>> [498341.949] (EE) XKB: Couldn't compile keymap >>>> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap >>>> instead. >>>> [498342.089] (EE) XKB: Could not invoke xkbcomp >>>> [498342.089] (EE) XKB: Couldn't compile keymap >>>> [498342.089] XKB: Failed to compile keymap >>>> [498342.089] Keyboard initialization failed. This could be a missing or >>>> incorrect setup of xkeyboard-config. >>>> [498342.089] Fatal server error: Failed to activate core devices. >>>> ------------------------------ >>>> >>>> I looked in the FAQ for the entry corresponding to this error, but none >>>> of the >>>> steps found any issues. I've tried doing "rebaseall" according to the >>>> instructions, but that hasn't made any difference. In fact, my problems >>>> started when I ran "rebaseall" to fix a different problem. I was getting >>>> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and >>>> some advice I found suggested running "rebaseall". >>> Unfortunately, rebaseall is a rather limited workaround, rather than a >>> solution for these issues (for reasons which have been discussed extensively >>> in the past) >>> >>> There has been a recent cygwin DLL change which *might* help in this >>> situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if >>> that makes a difference. (I wouldn't recommend later ones as they seem to >>> have >>> a regression in a different area) >>> >>> [1] http://cygwin.com/snapshots/ >> Also, I've found that using a different base address with rebaseall >> seems to help with some X problems: >> >> dash -c "rebaseall -b 0x77000000" >> >> http://cygwin.com/ml/cygwin/2011-04/msg00306.html >> > > Ok, that appears to have fixed my problem. Is that a "permanent" fix? For now, yes. ;-) -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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 haba713@gmail.com Thu Apr 28 04:22:00 2011 From: haba713@gmail.com (Harri T.) Date: Thu, 28 Apr 2011 04:22:00 -0000 Subject: Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Message-ID: <4DB8EB70.8010106@gmail.com> Hi! I have a problem with Cygwin/X: If I don't log in Windows (Win7 Pro 64-bit) immediately when it is possible (after start-up), Cygwin/X does not start but gives the following error: ... [ 667.715] (EE) XKB: Could not invoke xkbcomp [ 667.715] (EE) XKB: Couldn't compile keymap [ 667.715] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 669.571] (EE) XKB: Could not invoke xkbcomp [ 669.571] (EE) XKB: Couldn't compile keymap [ 669.571] XKB: Failed to compile keymap [ 669.571] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 669.571] Fatal server error: [ 669.571] Failed to activate core devices. If I log in immediately everything works fine. Full /var/log/xwin/XWin.0.log is here (expires in a month): http://pastebin.com/80rjKMwb Any idea? Harri -- 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 Thu Apr 28 13:25:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 28 Apr 2011 13:25:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB6E69F.6030706@cygwin.com> References: <4DB302A9.1090105@gmail.com> <4DB5920C.9010202@dronecode.org.uk> <20110425170715.GB3841@ednor.casa.cgf.cx> <4DB6551C.30309@gmail.com> <4DB6E69F.6030706@cygwin.com> Message-ID: <4DB96AC4.5000905@dronecode.org.uk> On 26/04/2011 16:37, Larry Hall (Cygwin-X) wrote: > On 4/26/2011 1:16 AM, David M. Karr wrote: >> On 4/25/2011 10:07 AM, Christopher Faylor wrote: >>> On Mon, Apr 25, 2011 at 04:23:56PM +0100, Jon TURNEY wrote: >>>> On 23/04/2011 17:47, David M. Karr wrote: >>>>> Almost a week ago now, I've been unable to run my XServer, and thus any >>>>> of the >>>>> apps that normally run with it, like Emacs. >>>> I realise this situation is an inconvenience, but please don't post to >>>> multiple lists just because you don't get a quick response. >>>> >>>>> When I run "startxwin", it just >>>>> says "failed to activate core devices". >>>> [snip] >>>>> [498341.949] (EE) XKB: Could not invoke xkbcomp >>>>> [498341.949] (EE) XKB: Couldn't compile keymap >>>>> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap >>>>> instead. >>>>> [498342.089] (EE) XKB: Could not invoke xkbcomp >>>>> [498342.089] (EE) XKB: Couldn't compile keymap >>>>> [498342.089] XKB: Failed to compile keymap >>>>> [498342.089] Keyboard initialization failed. This could be a missing or >>>>> incorrect setup of xkeyboard-config. >>>>> [498342.089] Fatal server error: Failed to activate core devices. >>>>> ------------------------------ >>>>> >>>>> I looked in the FAQ for the entry corresponding to this error, but none >>>>> of the >>>>> steps found any issues. I've tried doing "rebaseall" according to the >>>>> instructions, but that hasn't made any difference. In fact, my problems >>>>> started when I ran "rebaseall" to fix a different problem. I was getting >>>>> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and >>>>> some advice I found suggested running "rebaseall". >>>> Unfortunately, rebaseall is a rather limited workaround, rather than a >>>> solution for these issues (for reasons which have been discussed extensively >>>> in the past) >>>> >>>> There has been a recent cygwin DLL change which *might* help in this >>>> situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if >>>> that makes a difference. (I wouldn't recommend later ones as they seem to >>>> have >>>> a regression in a different area) Looking into this a bit more, it's not quite clear what's going on here: There's a few failure modes which can be reported as "XKB: Could not invoke xkbcomp", but the assumption that this is a fork() failure seems likely, given that the problem can be made to go away by rebasing. But I think that, at the point which fork() is invoked, XWin hasn't loaded any DLLs yet, so the fork() failure shouldn't be due to an inability to remap DLLs in the child to the same address as the parent. >>>> [1] http://cygwin.com/snapshots/ >>> Also, I've found that using a different base address with rebaseall >>> seems to help with some X problems: >>> >>> dash -c "rebaseall -b 0x77000000" >>> >>> http://cygwin.com/ml/cygwin/2011-04/msg00306.html >>> >> >> Ok, that appears to have fixed my problem. Is that a "permanent" fix? > > For now, yes. ;-) Humour-impaired persons, please note smiley -- 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/