From epost_123@online.de Sun Apr 1 01:35:00 2012 From: epost_123@online.de (epost_123@online.de) Date: Sun, 01 Apr 2012 01:35:00 -0000 Subject: Your program FontForge can't be used with cygwin since a few years Message-ID: <4F77B0DB.7010209@online.de> Your program FontForge can't be used with cygwin since a few years. Many Greetings -- 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 Sun Apr 1 06:07:00 2012 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Sun, 01 Apr 2012 06:07:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F77221E.2010204@cornell.edu> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> Message-ID: On Sat, Mar 31, 2012 at 9:26 AM, Ken Brown wrote: > I wanted to do some further tests, but I thought I should install the latest > Cygwin snapshot (2012-03-30) first. ?With that Cygwin snapshot, the XWin > snapshot of 20120329 won't start. It's not quite right here either. Xwin starts up OK, but I can't get an xterm going from the menu (stack dump). But if I open a CMD window and type "xterm -display localhost:0" then the xterm starts up OK. - Jim -- 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 marco.atzeri@gmail.com Sun Apr 1 07:16:00 2012 From: marco.atzeri@gmail.com (marco atzeri) Date: Sun, 01 Apr 2012 07:16:00 -0000 Subject: Your program FontForge can't be used with cygwin since a few years In-Reply-To: <4F77B0DB.7010209@online.de> References: <4F77B0DB.7010209@online.de> Message-ID: <4F78009E.3080701@gmail.com> On 4/1/2012 3:35 AM, epost_123 wrote: > Your program FontForge can't be used with cygwin since a few years. > Many Greetings wrong mail target ? cygwin has no package fontforge. 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 jon.turney@dronecode.org.uk Sun Apr 1 13:36:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sun, 01 Apr 2012 13:36:00 -0000 Subject: X server crash when running texworks In-Reply-To: References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> Message-ID: <4F7859E3.7010001@dronecode.org.uk> On 01/04/2012 07:07, Jim Reisert AD1C wrote: > On Sat, Mar 31, 2012 at 9:26 AM, Ken Brown wrote: > >> I wanted to do some further tests, but I thought I should install the latest >> Cygwin snapshot (2012-03-30) first. With that Cygwin snapshot, the XWin >> snapshot of 20120329 won't start. > > It's not quite right here either. Xwin starts up OK, but I can't get > an xterm going from the menu (stack dump). But if I open a CMD window > and type "xterm -display localhost:0" then the xterm starts up OK. If the cygwin 1.7.12 snapshot breaks the package XWin, you probably want to report that in the 1.7.12 snapshot call for testing thread, so the people who can fix problems with that will notice. -- 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 Sun Apr 1 13:40:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sun, 01 Apr 2012 13:40:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F76DC6B.6070704@dronecode.org.uk> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> Message-ID: <4F785ADC.3050908@dronecode.org.uk> On 31/03/2012 11:28, Jon TURNEY wrote: > On 30/03/2012 12:36, Jon TURNEY wrote: >> For me, the problem of texworks hanging only occurs very intermittently. It >> seems to be blocked deep in QtCore, waiting for the spawned process to >> terminate (which has already happened). > > Attaching to the texworks process, I get a backtrace like this: > > (gdb) bt > #0 0x7c90e514 in ntdll!LdrAccessResource () from > /cygdrive/c/WINDOWS/system32/ntdll.dll > #1 0x7c90df4a in ntdll!ZwWaitForMultipleObjects () from > /cygdrive/c/WINDOWS/system32/ntdll.dll > #2 0x7c809590 in KERNEL32!CreateFileMappingA () from > /cygdrive/c/WINDOWS/system32/kernel32.dll > #3 0x7c80a115 in WaitForMultipleObjects () from > /cygdrive/c/WINDOWS/system32/kernel32.dll > #4 0x610ce614 in select_stuff::wait(_types_fd_set*, _types_fd_set*, > _types_fd_set*, unsigned long) () > from /usr/bin/cygwin1.dll > #5 0x610cf02b in cygwin_select () from /usr/bin/cygwin1.dll > #6 0x610d33d5 in _sigfe () from /usr/bin/cygwin1.dll > #7 0x0022b87c in ?? () > #8 0x6d445820 in cygQtCore-4!_ZN15QProcessManager11qt_metacastEPKc () from > /usr/bin/cygQtCore-4.dll > #9 0x6d446e97 in cygQtCore-4!_ZN15QProcessPrivate15waitForFinishedEi () from > /usr/bin/cygQtCore-4.dll > #10 0x6d40fb85 in cygQtCore-4!_ZN8QProcess15waitForFinishedEi () from > /usr/bin/cygQtCore-4.dll > #11 0x6d41286c in cygQtCore-4!_ZN8QProcess7executeERK7QStringRK11QStringList > () from /usr/bin/cygQtCore-4.dll >> I'm not sure how the X server changes could directly cause that to happen. I can reproduce that same problem with the same backtrace with X server 1.11.4-5, so I don't think this can be called a regression in 1.12.0-1. -- 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 yselkowitz@users.sourceforge.net Mon Apr 2 01:36:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 02 Apr 2012 01:36:00 -0000 Subject: [ANNOUNCEMENT] Updated: libcanberra-0.28-2 Message-ID: The following packages have been updated for the Cygwin distribution: *** libcanberra0-0.28-2 *** libcanberra-devel-0.28-2 *** libcanberra-gtk0-0.28-2 *** libcanberra-gtk-deve-0.28-2 *** libcanberra-gtk3_0-0.28-2 *** libcanberra-gtk3-devel-0.28-2 *** gtk2.0-canberra-module-0.28-2 *** gtk3-canberra-module-0.28-2 *** vala-libcanberra-0.28-2 *** vala-libcanberra-gtk-0.28-2 libcanberra is an implementation of the XDG Sound Theme and Name Specifications, for generating event sounds on free desktops, such as GNOME. It comes with several backends and is designed to be portable. This release adds support for PulseAudio and TDB caching. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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 cygwin-xfree@cemery.org.uk Mon Apr 2 08:32:00 2012 From: cygwin-xfree@cemery.org.uk (Craig) Date: Mon, 02 Apr 2012 08:32:00 -0000 Subject: Cannot launch ssh from X11 system tray icon In-Reply-To: <4F744A05.20808@dronecode.org.uk> References: <4F744A05.20808@dronecode.org.uk> Message-ID: On 29 March 2012 12:39, Jon TURNEY wrote: > On 23/03/2012 17:56, Craig wrote: > >> debug1: Sending command: xterm >> ? ? ? 0 [main] ssh 2184 select_stuff::wait: WaitForMultipleObjects failed >> debug1: channel 0: free: client-session, nchannels 1 >> select: Permission denied > >> >> So can anyone tell me why I get the select / waitForMultipleObjects error? > > This error is coming from inside the select() emulation in the cygwin DLL itself. > > I've no idea why this is failing, and apparently only when an ancestor is the > X server. ?You might want to ask about this on the main cygwin list, it might > get the attention of someone with more insight. > > One thing to consider trying is that it might be something to do with the > environment inherited by processes started directly from the start menu, > rather than something specific to the X server, i.e. try starting your test > script directly from a start menu shortcut in a similar way to the X server is > started... > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer Hi Jon, Thanks for getting back to me. So I can run this from the run box: C:\cygwin\bin\run bash -c "export DISPLAY=:0.0 ; /bin/ssh vulpix xterm" And I get an xterm. I have my XWin Server pinned to my start bar and so I made a shortcut with the above in it and pinned it to my start bar and the thing runs fine. Both use "run". I'm thinking it's to do with Windows permissions. Does The XWin Server do a process group change or something? Craig -- 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 2 09:44:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 02 Apr 2012 09:44:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-1 (TEST) In-Reply-To: References: Message-ID: <4F7974F9.1040500@dronecode.org.uk> On 14/03/2012 14:25, Jon TURNEY wrote: > The following packages have been updated in the Cygwin distribution: > > *** xorg-server-1.12.0-1 > *** xorg-server-dmx-1.12.0-1 > > These packages contain XWin and the other X.Org X11 servers. > > This is the first release of the xserver 1.12 series. It is currently > available as a test release, and will be made stable in approximately two > weeks if no major regressions are reported. These packages have been promoted from test to current. -- 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 kbrown@cornell.edu Mon Apr 2 12:05:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 02 Apr 2012 12:05:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F77221E.2010204@cornell.edu> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> Message-ID: <4F7995E0.8070403@cornell.edu> On 3/31/2012 11:26 AM, Ken Brown wrote: > On 3/31/2012 6:28 AM, Jon TURNEY wrote: >> On 30/03/2012 12:36, Jon TURNEY wrote: >>> On 29/03/2012 20:59, Ken Brown wrote: >>>> On 3/29/2012 8:14 AM, Jon TURNEY wrote: >>>>> >>>>> Not so good :-(. Thanks for testing it, anyway. >>>>> >>>>> I found a rather bad crash bug I'd introduced and fixed that, so >>>>> you might >>>>> want to try today's snapshot [1], but I'm not confident that I >>>>> fixed the >>>>> problem you saw, so a backtrace would be helpful if you still get >>>>> crashes. >>>> >>>> OK, I'm running it now and have attached gdb to it. The good news is >>>> that >>>> I've been running it for a couple hours with no crash, and I've used >>>> texworks >>>> and have opened many tex files and pdf files in it without a >>>> problem. The bad >>>> news is that texworks becomes unresponsive and has to be killed >>>> whenever I try >>>> to compile a tex file. I have no idea whether this is due to an X >>>> server >>>> problem or something completely different. Anyway, I'll post a >>>> backtrace if >>>> the server crashes. >>>> >>>> In case you want to try to reproduce the current problem, start >>>> texworks, open >>>> a tex file (such as the file test1.tex whose contents I listed at the >>>> beginning of this thread), and click on the icon at the left end of the >>>> toolbar (brown triangle on a green background). This is supposed to >>>> cause >>>> test1.tex to get compiled, but for me it just causes texworks to become >>>> unresponsive. This was working properly with the previous version of >>>> the X >>>> server (until the server crashed). >>> >>> Thanks for testing this X server snapshot. >>> >>> For me, the problem of texworks hanging only occurs very >>> intermittently. It >>> seems to be blocked deep in QtCore, waiting for the spawned process to >>> terminate (which has already happened). >> >> Attaching to the texworks process, I get a backtrace like this: >> >> (gdb) bt >> #0 0x7c90e514 in ntdll!LdrAccessResource () from >> /cygdrive/c/WINDOWS/system32/ntdll.dll >> #1 0x7c90df4a in ntdll!ZwWaitForMultipleObjects () from >> /cygdrive/c/WINDOWS/system32/ntdll.dll >> #2 0x7c809590 in KERNEL32!CreateFileMappingA () from >> /cygdrive/c/WINDOWS/system32/kernel32.dll >> #3 0x7c80a115 in WaitForMultipleObjects () from >> /cygdrive/c/WINDOWS/system32/kernel32.dll >> #4 0x610ce614 in select_stuff::wait(_types_fd_set*, _types_fd_set*, >> _types_fd_set*, unsigned long) () >> from /usr/bin/cygwin1.dll >> #5 0x610cf02b in cygwin_select () from /usr/bin/cygwin1.dll >> #6 0x610d33d5 in _sigfe () from /usr/bin/cygwin1.dll >> #7 0x0022b87c in ?? () >> #8 0x6d445820 in cygQtCore-4!_ZN15QProcessManager11qt_metacastEPKc () >> from >> /usr/bin/cygQtCore-4.dll >> #9 0x6d446e97 in cygQtCore-4!_ZN15QProcessPrivate15waitForFinishedEi >> () from >> /usr/bin/cygQtCore-4.dll >> #10 0x6d40fb85 in cygQtCore-4!_ZN8QProcess15waitForFinishedEi () from >> /usr/bin/cygQtCore-4.dll >> #11 0x6d41286c in >> cygQtCore-4!_ZN8QProcess7executeERK7QStringRK11QStringList >> () from /usr/bin/cygQtCore-4.dll >> #12 0x0043a350 in ?? () >> #13 0x0047b8c5 in ?? () >> #14 0x6d46e733 in >> cygQtCore-4!_ZN11QMetaObject8activateEP7QObjectPKS_iPPv () >> from /usr/bin/cygQtCore-4.dll >> #15 0x6bc8b99b in cygQtGui-4!_ZN7QAction9triggeredEb () from >> /usr/bin/cygQtGui-4.dll >> #16 0x6bc8bb9a in cygQtGui-4!_ZN7QAction8activateENS_11ActionEventE () >> from >> /usr/bin/cygQtGui-4.dll >> #17 0x6c08dd06 in cygQtGui-4!_ZN11QToolButton14nextCheckStateEv () from >> /usr/bin/cygQtGui-4.dll >> #18 0x6bfe0185 in cygQtGui-4!_ZN22QAbstractButtonPrivate5clickEv () from >> /usr/bin/cygQtGui-4.dll >> #19 0x6bfe0426 in >> cygQtGui-4!_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent () from >> /usr/bin/cygQtGui-4.dll >> #20 0x6c08ddac in >> cygQtGui-4!_ZN11QToolButton17mouseReleaseEventEP11QMouseEvent () from >> /usr/bin/cygQtGui-4.dll >> #21 0x6bcd8769 in cygQtGui-4!_ZN7QWidget5eventEP6QEvent () from >> /usr/bin/cygQtGui-4.dll >> #22 0x6bc90fec in >> cygQtGui-4!_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent >> () from >> /usr/bin/cygQtGui-4.dll >> #23 0x6bc95e45 in >> cygQtGui-4!_ZN12QApplication6notifyEP7QObjectP6QEvent () >> from /usr/bin/cygQtGui-4.dll >> #24 0x6d45cefd in >> cygQtCore-4!_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent () >> from >> /usr/bin/cygQtCore-4.dll >> #25 0x6bc91d98 in >> cygQtGui-4!_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb >> >> () from /usr/bin/cygQtGui-4.dll >> #26 0x6bd007ed in >> cygQtGui-4!_ZN9QETWidget19translateMouseEventEPK7_XEvent () >> from /usr/bin/cygQtGui-4.dll >> #27 0x6bcff421 in >> cygQtGui-4!_ZN12QApplication15x11ProcessEventEP7_XEvent () >> from /usr/bin/cygQtGui-4.dll >> #28 0x6bd21f82 in cygQtGui-4!_ZN23QGuiEventDispatcherGlibC2EP7QObject >> () from >> /usr/bin/cygQtGui-4.dll >> #29 0x5efecb08 in g_main_context_dispatch () from >> /usr/bin/cygglib-2.0-0.dll >> #30 0x5efed208 in g_main_context_dispatch () from >> /usr/bin/cygglib-2.0-0.dll >> #31 0x5efed3cf in g_main_context_iteration () from >> /usr/bin/cygglib-2.0-0.dll >> #32 0x6d480671 in >> cygQtCore-4!_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE >> >> () >> from /usr/bin/cygQtCore-4.dll >> #33 0x6bd21cb7 in >> cygQtGui-4!_ZN23QGuiEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE >> >> () >> from /usr/bin/cygQtGui-4.dll >> #34 0x6d45c587 in >> cygQtCore-4!_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE >> () >> from /usr/bin/cygQtCore-4.dll >> #35 0x6d45c7f7 in >> cygQtCore-4!_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE () from >> /usr/bin/cygQtCore-4.dll >> #36 0x6d4605d6 in cygQtCore-4!_ZN16QCoreApplication4execEv () from >> /usr/bin/cygQtCore-4.dll >> #37 0x00402bbe in ?? () >> #38 0x61006d68 in _cygwin_exit_return () from /usr/bin/cygwin1.dll >> #39 0x00000001 in ?? () >> #40 0x20010100 in ?? () >> #41 0x00000000 in ?? () >> >> I'm guessing this is waiting for the pdftex process to terminate, but >> ps shows >> it as '(defunct)' already... > > I wanted to do some further tests, but I thought I should install the > latest Cygwin snapshot (2012-03-30) first. With that Cygwin snapshot, > the XWin snapshot of 20120329 won't start. This was apparently a cygwin1.dll problem. I've installed the 2012-04-01 cygwin1.dll snapshot, and XWin.20120329-git-6d4583d53c249549.exe starts again. I've resumed testing texworks. Here's one further detail: When texworks hangs and leaves a defunct pdftex process, pdftex hasn't actually completed its work successfully. It's supposed to produce a pdf file, but that doesn't happen. I wonder if there could be a race condition in which texworks is watching for a pdf file to appear while pdftex is trying to create that file. 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 jjreisert@alum.mit.edu Mon Apr 2 16:06:00 2012 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Mon, 02 Apr 2012 16:06:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F7995E0.8070403@cornell.edu> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> <4F7995E0.8070403@cornell.edu> Message-ID: On Mon, Apr 2, 2012 at 6:04 AM, Ken Brown wrote: > This was apparently a cygwin1.dll problem. ?I've installed the 2012-04-01 > cygwin1.dll > ?snapshot, and XWin.20120329-git-6d4583d53c249549.exe starts again. I've > resumed testing texworks. I had a similar experience. I could not get xterms to start using the 03/30 snapshot. I tried the 04/01 snapshot this morning and all seems back to normal. Also using the experimental 1.12 X server. -- 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 kbrown@cornell.edu Mon Apr 2 21:14:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 02 Apr 2012 21:14:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F7995E0.8070403@cornell.edu> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> <4F7995E0.8070403@cornell.edu> Message-ID: <4F7A16A1.5030100@cornell.edu> On 4/2/2012 8:04 AM, Ken Brown wrote: > On 3/31/2012 11:26 AM, Ken Brown wrote: >> On 3/31/2012 6:28 AM, Jon TURNEY wrote: >>> On 30/03/2012 12:36, Jon TURNEY wrote: >>>> On 29/03/2012 20:59, Ken Brown wrote: >>>>> On 3/29/2012 8:14 AM, Jon TURNEY wrote: >>>>>> >>>>>> Not so good :-(. Thanks for testing it, anyway. >>>>>> >>>>>> I found a rather bad crash bug I'd introduced and fixed that, so >>>>>> you might >>>>>> want to try today's snapshot [1], but I'm not confident that I >>>>>> fixed the >>>>>> problem you saw, so a backtrace would be helpful if you still get >>>>>> crashes. >>>>> >>>>> OK, I'm running it now and have attached gdb to it. The good news is >>>>> that >>>>> I've been running it for a couple hours with no crash, and I've used >>>>> texworks >>>>> and have opened many tex files and pdf files in it without a >>>>> problem. The bad >>>>> news is that texworks becomes unresponsive and has to be killed >>>>> whenever I try >>>>> to compile a tex file. I have no idea whether this is due to an X >>>>> server >>>>> problem or something completely different. Anyway, I'll post a >>>>> backtrace if >>>>> the server crashes. >>>>> >>>>> In case you want to try to reproduce the current problem, start >>>>> texworks, open >>>>> a tex file (such as the file test1.tex whose contents I listed at the >>>>> beginning of this thread), and click on the icon at the left end of >>>>> the >>>>> toolbar (brown triangle on a green background). This is supposed to >>>>> cause >>>>> test1.tex to get compiled, but for me it just causes texworks to >>>>> become >>>>> unresponsive. This was working properly with the previous version of >>>>> the X >>>>> server (until the server crashed). >>>> >>>> Thanks for testing this X server snapshot. >>>> >>>> For me, the problem of texworks hanging only occurs very >>>> intermittently. It >>>> seems to be blocked deep in QtCore, waiting for the spawned process to >>>> terminate (which has already happened). >>> >>> Attaching to the texworks process, I get a backtrace like this: >>> >>> (gdb) bt >>> #0 0x7c90e514 in ntdll!LdrAccessResource () from >>> /cygdrive/c/WINDOWS/system32/ntdll.dll >>> #1 0x7c90df4a in ntdll!ZwWaitForMultipleObjects () from >>> /cygdrive/c/WINDOWS/system32/ntdll.dll >>> #2 0x7c809590 in KERNEL32!CreateFileMappingA () from >>> /cygdrive/c/WINDOWS/system32/kernel32.dll >>> #3 0x7c80a115 in WaitForMultipleObjects () from >>> /cygdrive/c/WINDOWS/system32/kernel32.dll >>> #4 0x610ce614 in select_stuff::wait(_types_fd_set*, _types_fd_set*, >>> _types_fd_set*, unsigned long) () >>> from /usr/bin/cygwin1.dll >>> #5 0x610cf02b in cygwin_select () from /usr/bin/cygwin1.dll >>> #6 0x610d33d5 in _sigfe () from /usr/bin/cygwin1.dll >>> #7 0x0022b87c in ?? () >>> #8 0x6d445820 in cygQtCore-4!_ZN15QProcessManager11qt_metacastEPKc () >>> from >>> /usr/bin/cygQtCore-4.dll >>> #9 0x6d446e97 in cygQtCore-4!_ZN15QProcessPrivate15waitForFinishedEi >>> () from >>> /usr/bin/cygQtCore-4.dll >>> #10 0x6d40fb85 in cygQtCore-4!_ZN8QProcess15waitForFinishedEi () from >>> /usr/bin/cygQtCore-4.dll >>> #11 0x6d41286c in >>> cygQtCore-4!_ZN8QProcess7executeERK7QStringRK11QStringList >>> () from /usr/bin/cygQtCore-4.dll >>> #12 0x0043a350 in ?? () >>> #13 0x0047b8c5 in ?? () >>> #14 0x6d46e733 in >>> cygQtCore-4!_ZN11QMetaObject8activateEP7QObjectPKS_iPPv () >>> from /usr/bin/cygQtCore-4.dll >>> #15 0x6bc8b99b in cygQtGui-4!_ZN7QAction9triggeredEb () from >>> /usr/bin/cygQtGui-4.dll >>> #16 0x6bc8bb9a in cygQtGui-4!_ZN7QAction8activateENS_11ActionEventE () >>> from >>> /usr/bin/cygQtGui-4.dll >>> #17 0x6c08dd06 in cygQtGui-4!_ZN11QToolButton14nextCheckStateEv () from >>> /usr/bin/cygQtGui-4.dll >>> #18 0x6bfe0185 in cygQtGui-4!_ZN22QAbstractButtonPrivate5clickEv () from >>> /usr/bin/cygQtGui-4.dll >>> #19 0x6bfe0426 in >>> cygQtGui-4!_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent () >>> from >>> /usr/bin/cygQtGui-4.dll >>> #20 0x6c08ddac in >>> cygQtGui-4!_ZN11QToolButton17mouseReleaseEventEP11QMouseEvent () from >>> /usr/bin/cygQtGui-4.dll >>> #21 0x6bcd8769 in cygQtGui-4!_ZN7QWidget5eventEP6QEvent () from >>> /usr/bin/cygQtGui-4.dll >>> #22 0x6bc90fec in >>> cygQtGui-4!_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent >>> () from >>> /usr/bin/cygQtGui-4.dll >>> #23 0x6bc95e45 in >>> cygQtGui-4!_ZN12QApplication6notifyEP7QObjectP6QEvent () >>> from /usr/bin/cygQtGui-4.dll >>> #24 0x6d45cefd in >>> cygQtCore-4!_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent () >>> from >>> /usr/bin/cygQtCore-4.dll >>> #25 0x6bc91d98 in >>> cygQtGui-4!_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb >>> >>> >>> () from /usr/bin/cygQtGui-4.dll >>> #26 0x6bd007ed in >>> cygQtGui-4!_ZN9QETWidget19translateMouseEventEPK7_XEvent () >>> from /usr/bin/cygQtGui-4.dll >>> #27 0x6bcff421 in >>> cygQtGui-4!_ZN12QApplication15x11ProcessEventEP7_XEvent () >>> from /usr/bin/cygQtGui-4.dll >>> #28 0x6bd21f82 in cygQtGui-4!_ZN23QGuiEventDispatcherGlibC2EP7QObject >>> () from >>> /usr/bin/cygQtGui-4.dll >>> #29 0x5efecb08 in g_main_context_dispatch () from >>> /usr/bin/cygglib-2.0-0.dll >>> #30 0x5efed208 in g_main_context_dispatch () from >>> /usr/bin/cygglib-2.0-0.dll >>> #31 0x5efed3cf in g_main_context_iteration () from >>> /usr/bin/cygglib-2.0-0.dll >>> #32 0x6d480671 in >>> cygQtCore-4!_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE >>> >>> >>> () >>> from /usr/bin/cygQtCore-4.dll >>> #33 0x6bd21cb7 in >>> cygQtGui-4!_ZN23QGuiEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE >>> >>> >>> () >>> from /usr/bin/cygQtGui-4.dll >>> #34 0x6d45c587 in >>> cygQtCore-4!_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE >>> >>> () >>> from /usr/bin/cygQtCore-4.dll >>> #35 0x6d45c7f7 in >>> cygQtCore-4!_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE () >>> from >>> /usr/bin/cygQtCore-4.dll >>> #36 0x6d4605d6 in cygQtCore-4!_ZN16QCoreApplication4execEv () from >>> /usr/bin/cygQtCore-4.dll >>> #37 0x00402bbe in ?? () >>> #38 0x61006d68 in _cygwin_exit_return () from /usr/bin/cygwin1.dll >>> #39 0x00000001 in ?? () >>> #40 0x20010100 in ?? () >>> #41 0x00000000 in ?? () >>> >>> I'm guessing this is waiting for the pdftex process to terminate, but >>> ps shows >>> it as '(defunct)' already... > Here's one further detail: When texworks hangs and leaves a defunct > pdftex process, pdftex hasn't actually completed its work successfully. > It's supposed to produce a pdf file, but that doesn't happen. I wonder > if there could be a race condition in which texworks is watching for a > pdf file to appear while pdftex is trying to create that file. Much earlier in the thread I mentioned a warning "QFileSystemWatcher: failed to add paths: /home/kbrown". I've looked at the QtCore sources, and that warning is generated by the function QFileSystemWatcher::addPaths, in corelib/io/qfilesystemwatcher.cpp. If I'm understanding the code correctly, that function tries to use a "native" (system-specific) FileSystemWatcherEngine if possible. The function QFileSystemWatcherPrivate::createNativeEngine in the same file creates native engines on Windows, Linux, FreeBSD, Mac OS, and Symbian, but not on Cygwin. I don't know if it's worth pursuing this, but the failure of FileSystemWatcher could conceivably be the problem here. Do you know enough about Qt to have any ideas about how to proceed? Or Yaakov? 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 yselkowitz@users.sourceforge.net Mon Apr 2 22:50:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 02 Apr 2012 22:50:00 -0000 Subject: X server crash when running texworks In-Reply-To: <4F7A16A1.5030100@cornell.edu> References: <4F6E24CA.2000701@cornell.edu> <4F70C7BE.1070402@cornell.edu> <4F70CC57.6080607@dronecode.org.uk> <4F70D272.2040506@cornell.edu> <4F72F30A.4020401@dronecode.org.uk> <4F7303E1.107@cornell.edu> <4F7307B0.90400@cornell.edu> <4F745236.50809@dronecode.org.uk> <4F74BF22.3020109@cornell.edu> <4F759ABF.1090007@dronecode.org.uk> <4F76DC6B.6070704@dronecode.org.uk> <4F77221E.2010204@cornell.edu> <4F7995E0.8070403@cornell.edu> <4F7A16A1.5030100@cornell.edu> Message-ID: <4F7A2D26.8000103@users.sourceforge.net> On 2012-04-02 16:14, Ken Brown wrote: > Much earlier in the thread I mentioned a warning "QFileSystemWatcher: > failed to add paths: /home/kbrown". I've looked at the QtCore sources, > and that warning is generated by the function > QFileSystemWatcher::addPaths, in corelib/io/qfilesystemwatcher.cpp. If > I'm understanding the code correctly, that function tries to use a > "native" (system-specific) FileSystemWatcherEngine if possible. The > function QFileSystemWatcherPrivate::createNativeEngine in the same file > creates native engines on Windows, Linux, FreeBSD, Mac OS, and Symbian, > but not on Cygwin. Correct, as the Windows backend won't work OOTB with *NIX filesystem, and we don't support any of the other native backends. > I don't know if it's worth pursuing this, but the failure of > FileSystemWatcher could conceivably be the problem here. Do you know > enough about Qt to have any ideas about how to proceed? Or Yaakov? The only plausible solutions would be to either: * implement inotify[1] in Cygwin on top of Windows' Directory Change Notification APIs[2] (which would benefit a number of packages); * OR implement a FAM/Gamin-based QFileSystemWatcher backend. Yaakov [1] http://man7.org/linux/man-pages/man7/inotify.7.html [2] http://msdn.microsoft.com/en-us/library/windows/desktop/aa365261%28v=vs.85%29.aspx -- 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 Tue Apr 3 21:13:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Tue, 03 Apr 2012 21:13:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <1323043980.1644.6.camel@YAAKOV04> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> Message-ID: <4F7B6794.2010303@cornell.edu> On 12/4/2011 7:13 PM, Yaakov (Cygwin/X) wrote: > On Fri, 2011-12-02 at 08:01 -0500, Ken Brown wrote: >> This doesn't do it. Emacs still dies after a short time. I don't know >> if that means that there's something else going on, but I'll retest it >> after you package gvfs. In the meantime, I'll continue with my >> workaround of setting GSETTINGS_BACKEND=memory. Now that gvfs is available, I've built the latest emacs-24 pretest against gtk3 and removed the GSETTINGS_BACKEND=memory setting, but I still have the same problem. If I start emacs and then just walk away from it, after a while it will die with a segfault. (It may take an hour or more before this happens.) I've got a backtrace (attached), but it may not be useful because of optimization. I can rebuild without optimization if you think it would be helpful. In the meantime, if you want to try to reproduce the problem, you can get my build of emacs-24.0.95-2 by running setup.exe -K http://sanibeltranquility.com/cygwin/kbrown.gpg and adding http://sanibeltranquility.com/cygwin to the list of mirrors. I'm attaching cygcheck output in case you can spot something in my setup that's different from yours. Ken -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: cygcheck.out URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: emacs-backtrace URL: -------------- next part -------------- -- 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 yselkowitz@users.sourceforge.net Tue Apr 3 22:30:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 03 Apr 2012 22:30:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <4F7B6794.2010303@cornell.edu> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> Message-ID: <4F7B7A14.9030003@users.sourceforge.net> On 2012-04-03 16:11, Ken Brown wrote: > Now that gvfs is available, I've built the latest emacs-24 pretest > against gtk3 and removed the GSETTINGS_BACKEND=memory setting, but I > still have the same problem. If I start emacs and then just walk away > from it, after a while it will die with a segfault. (It may take an hour > or more before this happens.) And with gtk2? > I've got a backtrace (attached), but it may not be useful because of > optimization. I don't see anything in the backtrace which indicates that this is gtk3-related; I would guess it is a bug in either cygwin or emacs. Yaakov -- 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 Wed Apr 4 01:53:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Wed, 04 Apr 2012 01:53:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <4F7B7A14.9030003@users.sourceforge.net> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> <4F7B7A14.9030003@users.sourceforge.net> Message-ID: <4F7BA975.1090705@cornell.edu> On 4/3/2012 6:30 PM, Yaakov (Cygwin/X) wrote: > On 2012-04-03 16:11, Ken Brown wrote: >> Now that gvfs is available, I've built the latest emacs-24 pretest >> against gtk3 and removed the GSETTINGS_BACKEND=memory setting, but I >> still have the same problem. If I start emacs and then just walk away >> from it, after a while it will die with a segfault. (It may take an hour >> or more before this happens.) > > And with gtk2? There's no problem when emacs is built with gtk2. There's also no problem with gtk3, provided I set GSETTINGS_BACKEND=memory. I'll probably just have to stick with gtk2 for the next emacs release. 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 yselkowitz@users.sourceforge.net Wed Apr 4 03:56:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 04 Apr 2012 03:56:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <4F7BA975.1090705@cornell.edu> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> <4F7B7A14.9030003@users.sourceforge.net> <4F7BA975.1090705@cornell.edu> Message-ID: <4F7BC642.3090909@users.sourceforge.net> On 2012-04-03 20:52, Ken Brown wrote: > There's no problem when emacs is built with gtk2. There's also no > problem with gtk3, provided I set GSETTINGS_BACKEND=memory. I regularly run the entire GNOME desktop for hours (if not days) on end, so I really don't think that this is a bug in dconf or gvfs. > I'll probably just have to stick with gtk2 for the next emacs release. That's fine; gtk2 isn't going anywhere for a while. Yaakov -- 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 Wed Apr 4 14:15:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Wed, 04 Apr 2012 14:15:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <4F7BC642.3090909@users.sourceforge.net> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> <4F7B7A14.9030003@users.sourceforge.net> <4F7BA975.1090705@cornell.edu> <4F7BC642.3090909@users.sourceforge.net> Message-ID: <4F7C5779.405@cornell.edu> On 4/3/2012 11:55 PM, Yaakov (Cygwin/X) wrote: > On 2012-04-03 20:52, Ken Brown wrote: >> There's no problem when emacs is built with gtk2. There's also no >> problem with gtk3, provided I set GSETTINGS_BACKEND=memory. > > I regularly run the entire GNOME desktop for hours (if not days) on end, > so I really don't think that this is a bug in dconf or gvfs. > >> I'll probably just have to stick with gtk2 for the next emacs release. > > That's fine; gtk2 isn't going anywhere for a while. Another option is to use gtk3 but to put the GSETTINGS_BACKEND workaround into the emacs startup code: setenv ("GSETTINGS_BACKEND", "memory", 1); I've been testing this, and it seems to work (but I won't be completely confident until I've had emacs running for a day or so). Do you see any downside? 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 jon.turney@dronecode.org.uk Wed Apr 4 17:35:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 04 Apr 2012 17:35:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-2 (TEST) Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-2 *** xorg-server-common-1.12.0-2 *** xorg-server-dmx-1.12.0-2 *** xorg-server-extra-1.12.0-2 *** xorg-server-devel-1.12.0-2 These packages contain XWin and the other X.Org X11 servers. Upstream is considering the removal of the Xephyr, Xfake, Xnest and Xvfb servers sometime after X11R7.7, to be replaced by invoking the Xorg server with the xf86-video-dummy or xf86-video-nested drivers [1]. To prepare for this transition, some packaging changes have been made: PACKAGING CHANGES: 1) The Xephyr, Xfake, Xnest and Xvfb servers have been moved to a separate xorg-server-extra package. 2) A new xorg-server-common package contains X server common files. This allows xorg-server-extra to be installed (e.g. for Xvfb) without installing xorg-server. 3) The xorg-server package now also contains the Xorg server, which can be used with the xf86-video-dummy and xf86-video-nested drivers to provide dummy and nested X servers. 4) The new xorg-server-devel package contains the SDK for building drivers and extensions for the Xorg server. Given setup limitations, some of the dependencies between these packages may not be correct until they are promoted from test to current. Also, I've made an effort to finish off a lot of my half-completed patches, so this package contains numerous changes to cygwin-specific code. This package is currently available as a test release, and will be made stable in approximately one week if no major regressions are reported. The following cygwin-specific changes have been made since 1.12.0-1: * In multiwindow mode, the native window icon now updates if the X window _NEW_WM_ICON icon hint changes * In multiwindow mode, the native window styling now updates if the X window styling hints change * The _NET_WM_STATE_SKIP_TASKBAR hint is now implemented in multiwindow mode * A crash caused by a race condition in the conversion of the window icon from an X property to a Windows icon has been fixed (Reported by Ken Brown) * In multiwindow mode, the native window now flashes on the taskbar if the X window's urgency hint is set * A bug which could cause the X server to use 100% of a core while waiting for the X clipboard contents to be converted has been fixed [2] * Fake XINERAMA data is now generated describing the native monitors when multiplemonitor mode is enabled, allowing XINERAMA-aware X applications to correctly place their windows so they don't get split between monitors. * A couple of timing-sensitive failures in clipboard handling have been fixed. * Lots of debugging improvements, correctness changes and obsolete cruft removed. * Make it possible to build the Xorg server for Cygwin (Thanks to Yaakov Selkowitz for patches) 11cb1f55368dfeb7a8cc51e4662b9a5c *xorg-server-1.12.0-2.tar.bz2 1a28579b4a5aa98b1cccb9c835f683c5 *xorg-server-common-1.12.0-2.tar.bz2 bb8c7f768ecd0710d149e248e19e9ffa *xorg-server-devel-1.12.0-2.tar.bz2 898b2b6eb92b74e5932c2863b97f4562 *xorg-server-dmx-1.12.0-2.tar.bz2 017d3fbb83b29536b2981260cd4a16c9 *xorg-server-extra-1.12.0-2.tar.bz2 920a7aad32e70cc3615a931346cc76de *xorg-server-1.12.0-2-src.tar.bz2 [1] http://lists.x.org/archives/xorg-devel/2012-March/030059.html [2] This one was just terrible, see http://cgit.freedesktop.org/~jturney/xserver/commit&id=475d248cef2c84e56458f9faa4d95157ed904f8b -- 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 cygwin-xfree@cemery.org.uk Wed Apr 4 21:16:00 2012 From: cygwin-xfree@cemery.org.uk (Craig) Date: Wed, 04 Apr 2012 21:16:00 -0000 Subject: Cannot launch ssh from X11 system tray icon In-Reply-To: References: <4F744A05.20808@dronecode.org.uk> Message-ID: Installing 1.12.0-1 made the issue go away. :-) Craig -- 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 yselkowitz@users.sourceforge.net Wed Apr 4 22:13:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 04 Apr 2012 22:13:00 -0000 Subject: Problems with emacs built against gtk3 In-Reply-To: <4F7C5779.405@cornell.edu> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> <4F7B7A14.9030003@users.sourceforge.net> <4F7BA975.1090705@cornell.edu> <4F7BC642.3090909@users.sourceforge.net> <4F7C5779.405@cornell.edu> Message-ID: <4F7CC76B.1030301@users.sourceforge.net> On 2012-04-04 09:15, Ken Brown wrote: > Another option is to use gtk3 but to put the GSETTINGS_BACKEND > workaround into the emacs startup code: > > setenv ("GSETTINGS_BACKEND", "memory", 1); > > I've been testing this, and it seems to work (but I won't be completely > confident until I've had emacs running for a day or so). Do you see any > downside? This is intended solely for testing and debugging. Settings will not be saved from one invocation to the next, so that's a pretty big downside. Yaakov -- 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 jesus.10@etb.net.co Thu Apr 5 04:01:00 2012 From: jesus.10@etb.net.co (=?windows-1251?Q?=CE=EA=F1=E0=ED=E0__=DD=ED=E3=EE=E2=E0=F2=EE=E2=E0?=) Date: Thu, 05 Apr 2012 04:01:00 -0000 Subject: =?windows-1251?Q??= Message-ID: <7577881564.2012045080111@etb.net.co> ???????????????? ?????????? ?????? ?????????????????????????????? ???????? ?????????? ??????????.! ?????????????? ???? ?????? ???? ???????????????????? pshjzdan.smtp.ru?????????????????????????????? ?????????? ???????? ??????!!! ???????? ????????????????...) -- 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 moss@cs.umass.edu Thu Apr 5 15:55:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Thu, 05 Apr 2012 15:55:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series Message-ID: <4F7DC041.6070500@cs.umass.edu> Dear Jon (et al.) -- Something seems to have changed between the last 1.11 release and the 1.12.0 (up through the 1.12.0-2 release made yesterday). The window for StartXWin, which is minimized, did not previously result in an X icon in the taskbar, but now does, and it is distinct from the stack of X icons for my several launched xterms. I feel it is clutter and want to suppress it, but I don't know how at this point. Separately, going from 1.12.0-1 to 1.12.0-2 changed my xemacs icon, to one that is nearly transparent (there's something there, but very hard to discern). In the past xemacs gave its own icon (which I could never find or override). Here are possibly relevant facts about my setup: 1) How I start things: StartWXin is a Windows short cut, set to run as a "Normal Window", started from directory C:\cygwin\bin, with this command ("Target"): C:\cygwin\bin\run.exe /bin/bash -l -c "/bin/startxwin -- -unixkill -clipboard -multimonitors -resize -engine 1 -emulate3buttons 100 -wm -auth /home/Eliot/.Xauthority" 2) My .startxwinrc file contains: #!/bin/bash xrdb -merge ${HOME}/.Xdefaults xmodmap ${HOME}/.Xmodmap UC="${USER} console" xterm +tb -geometry 110x43+4+0 -T "${USER}" -n "${USER}" -name "${USER}" -bg rgbi:.0/.2/.2 -ls & xterm +tb -geometry 110x43-10+0 -T "${UC}" -n "${UC}" -name "${UC}" -bg rgbi:.5/.0/.1 -ls & xterm +tb -maximized -T task -n task -name task -bg rgbi:.05/.05/.05 -ls -e rlwrap -a -- task shell & xemacs -T xemacs -n xemacs -name xemacs1 & 3) My .XWinrc contains: MENU systray { elnux1 EXEC "xterm -display %display% -ls -title elnux1 -bg rgbi:.1/.10/.1 -e /usr/bin/ssh moss@elnux1.cs.umass.edu" elnux7 EXEC "xterm -display %display% -ls -title elnux7 -bg rgbi:.1/.10/.1 -e /usr/bin/ssh moss@elnux7.cs.umass.edu" roc EXEC "xterm -display %display% -ls -title roc -bg rgbi:.2/.20/.0 -e /usr/bin/ssh moss@roc.cs.umass.edu" swarm EXEC "xterm -display %display% -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh moss@swarm.cs.umass.edu" deepgreen EXEC "xterm -display %display% -ls -title deepgreen -bg rgbi:.0/.03/.0 -e /usr/bin/ssh moss@deepgreen.cs.umass.edu" balder EXEC "xterm -display %display% -ls -title balder -bg rgbi:.2/.00/.0 -e /usr/bin/ssh moss@balder.cs.umass.edu" SEPARATOR console EXEC "xterm -display %display% +tb -geometry 110x43-10+0 -T 'Eliot console' -n 'Eliot console' -name 'Eliot console' -bg rgbi:.5/.0/.1 -ls" login EXEC "xterm -display %display% +tb -geometry 110x43+4+0 -T 'Eliot' -n 'Eliot' -name 'Eliot' -bg rgbi:.0/.2/.2 -ls" task EXEC "xterm -display %display% -ls -title task -bg rgbi:.05/.05/.05 -maximized -e rlwrap -a -- task shell" xterm EXEC "xterm -display %display% -ls -title xterm" SEPARATOR xemacs EXEC "xemacs" xpdf EXEC "xpdf" SEPARATOR "Reload .XWinrc" RELOAD } ROOTMENU systray STYLES { console MINIMIZE Eliot MINIMIZE xemacs1 MINIMIZE } ====== These various commands / files all seem to be seen and used. And by the way, the xemacs1 MINIMIZE does not seem to work -- it always starts maximized and I have to minimize it manually. Hints on that? Regards -- Eliot Moss -- 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 moss@cs.umass.edu Thu Apr 5 16:11:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Thu, 05 Apr 2012 16:11:00 -0000 Subject: Reload .XWinrc kills X server Message-ID: <4F7DC41B.3060000@cs.umass.edu> Dear Jon (et al.) -- On xorg-server 1.12.0-2, doing a reload of .XWinrc via the .XWinrc menu cases an exception that kills the X server. I does put up an error window saying what happened (a segmentation fault). Regards -- Eliot Moss -- 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 Fri Apr 6 17:01:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 06 Apr 2012 17:01:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F7DC041.6070500@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> Message-ID: <4F7F2174.6060209@dronecode.org.uk> On 05/04/2012 16:54, Eliot Moss wrote: > Something seems to have changed between the last 1.11 release and > the 1.12.0 (up through the 1.12.0-2 release made yesterday). Thanks for testing! > The window for StartXWin, which is minimized, did not previously > result in an X icon in the taskbar, but now does, and it is > distinct from the stack of X icons for my several launched > xterms. I feel it is clutter and want to suppress it, but I > don't know how at this point. I guess the window you are seeing is the terminal window in which bash is being run? It's the job of the run command to hide that window, and why it should suddenly stop doing so when the XWin at the bottom of the process tree changes, I have no idea. This might perhaps be related to a bug in cygwin 1.7.12 where cygwin executables were wrongly handled as native, non-cygwin executables? > Separately, going from 1.12.0-1 to 1.12.0-2 changed my xemacs > icon, to one that is nearly transparent (there's something > there, but very hard to discern). In the past xemacs gave > its own icon (which I could never find or override). Thanks for pointing this out. I'd introduced a couple of bugs into the fallback icon conversion code for a bitmap pointed to by WM_HINTS (which is only used when a NET_WM_ICON property isn't present) I've applied a couple of fixes, so hopefully this works better now. I've uploaded a snapshot at [2]. Perhaps you could try that out and see if that improves things for you? I suspect that the 'XE' icon from /usr/share/xemacs-21.4.22/etc/xemacs-icon.xpm is baked into the Xemacs executable. If Xemacs itself doesn't provide a way to change it, you could override it for multiwindow mode by using the ICONS directive in XWinrc. > xemacs -T xemacs -n xemacs -name xemacs1 & > STYLES { > console MINIMIZE > Eliot MINIMIZE > xemacs1 MINIMIZE > } > > These various commands / files all seem to be seen and used. And by the way, > the xemacs1 MINIMIZE does not seem to work -- it always starts maximized and I > have to minimize it manually. Hints on that? Using -name to set the xemacs resource name does not set the window class name, apparently by design [1], so this style directive will not match the window title or window class name of your xemacs window. Fortunately, you could probably achieve the same effect by adding the '-iconic' command line option to the xemacs invocation. On 05/04/2012 17:11, Eliot Moss wrote: > On xorg-server 1.12.0-2, doing > a reload of .XWinrc via the .XWinrc menu cases an > exception that kills the X server. I does put up > an error window saying what happened (a > segmentation fault). This was also related to the icon conversion changes and should be fixed in the latest snapshot. [1] http://www.nada.kth.se/cgi-bin/info?%28xemacs-faq.info%29Q3.1.7 [2] ftp://cygwin.com/pub/cygwinx/XWin.20120406-git-b309f093d6e90201.exe.bz2 -- 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 Apr 6 17:22:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Fri, 06 Apr 2012 17:22:00 -0000 Subject: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] In-Reply-To: <4F7CC76B.1030301@users.sourceforge.net> References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4F7B6794.2010303@cornell.edu> <4F7B7A14.9030003@users.sourceforge.net> <4F7BA975.1090705@cornell.edu> <4F7BC642.3090909@users.sourceforge.net> <4F7C5779.405@cornell.edu> <4F7CC76B.1030301@users.sourceforge.net> Message-ID: <4F7F2649.3070005@cornell.edu> On 4/4/2012 6:12 PM, Yaakov (Cygwin/X) wrote: > On 2012-04-04 09:15, Ken Brown wrote: >> Another option is to use gtk3 but to put the GSETTINGS_BACKEND >> workaround into the emacs startup code: >> >> setenv ("GSETTINGS_BACKEND", "memory", 1); >> >> I've been testing this, and it seems to work (but I won't be completely >> confident until I've had emacs running for a day or so). Do you see any >> downside? > > This is intended solely for testing and debugging. Settings will not be > saved from one invocation to the next, so that's a pretty big downside. OK, that was a bad idea. I'm going to try to debug this problem. I was wrong when I said that the problem doesn't occur with gtk2. I based that statement on earlier tests; but I did those tests several months ago, when I started this thread, and I probably didn't have dconf-service installed at the time. Now I can reproduce the problem with both gtk2 and gtk3. But the problem doesn't occur if I build emacs with the configure option --without-gsettings. I've changed the subject line accordingly. By the way, emacs (starting with emacs-24) will use both GSettings and GConf if they're available. But there doesn't appear to be any problem using GConf alone. Here's my most recent debugging session. This is from a build using gtk2 and GSettings (but not GConf): GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special) [...] Reading symbols from /home/kbrown/src/emacs/test/src/emacs...done. (gdb) r -Q Starting program: /home/kbrown/src/emacs/test/src/emacs -Q [New Thread 12220.0x950] [...] [New Thread 12220.0x330c] Program received signal SIGSEGV, Segmentation fault. 0x00289d7a in ?? () (gdb) bt full #0 0x00289d7a in ?? () No symbol table info available. #1 0x007bd264 in __morecore () No symbol table info available. warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.) warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.) warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.) warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.) warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.) #2 0x00000001 in ?? () warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.) wsock_started = true wsadata = {wVersion = 514, wHighVersion = 514, szDescription = "WinSock 2.0", '\000' , szSystemStatus = "Running", '\000' , iMaxSockets = 0, iMaxUdpDg = 0, lpVendorInfo = 0x0} #3 0x00606175 in calloc (nmemb=4294867296, size=8) at gmalloc.c:1547 result = 0x0 #4 0x00000000 in ?? () No symbol table info available. This looks very strange to me, especially the part about WinSock. Where could that have come from? Here are the steps for reproducing the problem: 1. Install the following packages and their dependencies: gnutls-devel libdbus1-devel libdbus1_3 libgif-devel libgtk2.0-devel libgtk3-devel libMagick-devel libMagickCore5 librsvg2-devel libSM-devel libXpm-devel [These might not all be necessary for reproducing the problem, but they're used in my build or as runtime dependencies of my build.] 2. Build emacs with GSettings support but not GConf support: wget ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-24.0.95.tar.gz tar -xf emacs-24.0.95.tar.gz cd emacs-24.0.95 ./configure --without-gconf && make [Note: By default, the build will use gtk2. The option "--with-x-toolkit=gtk3" will make it use gtk3.] 3. Start the X server using the Start Menu shortcut, with no ~/.startxwinrc. 4. In the resulting xterm window: eval `dbus-launch --sh-syntax` cd emacs-24.0.95/src ./emacs -Q & 5. Ignore emacs; it will eventually crash. This could take one or more hours, but it happens every time on my system. It happens much faster if I don't disable GConf support. It would be extremely helpful if someone could try to reproduce this. At the very least, I'd like to rule out the possibility that it's caused by BLODA on my system. 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 angelo.graziosi@alice.it Fri Apr 6 19:22:00 2012 From: angelo.graziosi@alice.it (Angelo Graziosi) Date: Fri, 06 Apr 2012 19:22:00 -0000 Subject: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] Message-ID: <4F7F427C.3070900@alice.it> Hi Ken, Ken Brown wrote: > Now I can reproduce the problem with both gtk2 and gtk3 If you remember I flagged this on 24.11.2011 with a private mail. After the upgrading to GNOME 3.2, not only the gtk3 build was unstable but also the old gtk2 builds were unstable... Since then I am using this target C:\cygwin-2\bin\run.exe bash -l -c 'GSETTINGS_BACKEND=memory emacs -display 127.0.0.1:0.0 2>/dev/null &' to start Emacs from a link on desktop, and it works both with gtk2 and with gtk3 builds. Notice, I do not use Cygwin service (dbus,... etc.) Any way I will try to follow your recipe to reproduce the problem, but I am sure it is still there.. > Here are the steps for reproducing the problem: Ciao, Angelo. -- 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 moss@cs.umass.edu Sat Apr 7 04:01:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Sat, 07 Apr 2012 04:01:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F7F2174.6060209@dronecode.org.uk> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> Message-ID: <4F7FBBEF.1040204@cs.umass.edu> On 4/6/2012 1:01 PM, Jon TURNEY wrote: > On 05/04/2012 16:54, Eliot Moss wrote: >> Something seems to have changed between the last 1.11 release and >> the 1.12.0 (up through the 1.12.0-2 release made yesterday). >> The window for StartXWin, which is minimized, did not previously >> result in an X icon in the taskbar, but now does, and it is >> distinct from the stack of X icons for my several launched >> xterms. I feel it is clutter and want to suppress it, but I >> don't know how at this point. > > I guess the window you are seeing is the terminal window in which bash is > being run? It's the job of the run command to hide that window, and why it > should suddenly stop doing so when the XWin at the bottom of the process tree > changes, I have no idea. Yes, which is why I, too, was surprised. > This might perhaps be related to a bug in cygwin 1.7.12 where cygwin > executables were wrongly handled as native, non-cygwin executables? I just installed 1.7.13, and the behavior is still there. It goes away when something completes, which happens when all the windows started by .startxwinrc are gone. If I kill it, then all those initial windows die. Perhaps this is all normal, *except* that the run window is displayed. >> Separately, going from 1.12.0-1 to 1.12.0-2 changed my xemacs >> icon, to one that is nearly transparent (there's something >> there, but very hard to discern). In the past xemacs gave >> its own icon (which I could never find or override). > > Thanks for pointing this out. I'd introduced a couple of bugs into the > fallback icon conversion code for a bitmap pointed to by WM_HINTS (which is > only used when a NET_WM_ICON property isn't present) > > I've applied a couple of fixes, so hopefully this works better now. I've > uploaded a snapshot at [2]. Perhaps you could try that out and see if that > improves things for you? Yes! Now the xemacs icon is back to the way it used to be. > I suspect that the 'XE' icon from > /usr/share/xemacs-21.4.22/etc/xemacs-icon.xpm is baked into the Xemacs > executable. If Xemacs itself doesn't provide a way to change it, you could > override it for multiwindow mode by using the ICONS directive in XWinrc. Maybe; if I find one I like :-) ... >> These various commands / files all seem to be seen and used. And by the way, >> the xemacs1 MINIMIZE does not seem to work -- it always starts maximized and I >> have to minimize it manually. Hints on that? > > Using -name to set the xemacs resource name does not set the window class > name, apparently by design [1], so this style directive will not match the > window title or window class name of your xemacs window. > > Fortunately, you could probably achieve the same effect by adding the > '-iconic' command line option to the xemacs invocation. Actually, -iconic does not work; neither does it work to set the iconic resource to true. Seems to be an xemacs thing. In fact, here is a quote from the FAQ: "Ugh, this stuff is such an incredible mess that I've about given up getting it to work. The principal problem is numerous window-manager bugs... " However, I find that the .XWinrc MINIMIZE style *does* work ... but of course only for windows I create later. And the class name is "emacs", not "xemacs", hence a STYLE entry of: emacs MINIMIZE ... Does this suggest to you any other way that might work to get an iconified xemacs from the .startxwinrc file? > On 05/04/2012 17:11, Eliot Moss wrote: >> On xorg-server 1.12.0-2, doing >> a reload of .XWinrc via the .XWinrc menu cases an >> exception that kills the X server. I does put up >> an error window saying what happened (a >> segmentation fault). > > This was also related to the icon conversion changes and should be fixed in > the latest snapshot. That is indeed now fixed. Thanks for all the fixes! E > [1] http://www.nada.kth.se/cgi-bin/info?%28xemacs-faq.info%29Q3.1.7 > [2] ftp://cygwin.com/pub/cygwinx/XWin.20120406-git-b309f093d6e90201.exe.bz2 -- 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 etiqueta@maladiretabairro.com.br Sat Apr 7 07:47:00 2012 From: etiqueta@maladiretabairro.com.br (Ruas ou Bairros) Date: Sat, 07 Apr 2012 07:47:00 -0000 Subject: =?windows-1252?Q?Envie_Mala_Direta_s=F3_para_as_Ruas_ou_Bairros_que_desejar.?= Message-ID: <4139-2201246774715296@micro> Etiquetas em diversos materiais. Etiquetas prontas para envio de Mala Direta, ? s? colar nos envelopes. Nosso diferencial: Voce pode enviar s? para as RUAS ou BAIRROS que escolher. Garantido pelo Pag Seguro Uol. www.jcmiranda.com.br -- 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 7 16:19:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 07 Apr 2012 16:19:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F7FBBEF.1040204@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> Message-ID: <4F806901.2010507@dronecode.org.uk> On 07/04/2012 05:00, Eliot Moss wrote: > On 4/6/2012 1:01 PM, Jon TURNEY wrote: >> On 05/04/2012 16:54, Eliot Moss wrote: >>> Something seems to have changed between the last 1.11 release and >>> the 1.12.0 (up through the 1.12.0-2 release made yesterday). > >>> The window for StartXWin, which is minimized, did not previously >>> result in an X icon in the taskbar, but now does, and it is >>> distinct from the stack of X icons for my several launched >>> xterms. I feel it is clutter and want to suppress it, but I >>> don't know how at this point. >> >> I guess the window you are seeing is the terminal window in which bash is >> being run? It's the job of the run command to hide that window, and why it >> should suddenly stop doing so when the XWin at the bottom of the process tree >> changes, I have no idea. > > Yes, which is why I, too, was surprised. > >> This might perhaps be related to a bug in cygwin 1.7.12 where cygwin >> executables were wrongly handled as native, non-cygwin executables? > > I just installed 1.7.13, and the behavior is still there. > It goes away when something completes, which happens when > all the windows started by .startxwinrc are gone. If I kill > it, then all those initial windows die. Perhaps this is all > normal, *except* that the run window is displayed. All I can really say is that it works for me. If run isn't doing it's job for you, I don't know why. You might like to take a look at using the xlaunch package to start your Xserver and see if that behaves any better. >>> These various commands / files all seem to be seen and used. And by the way, >>> the xemacs1 MINIMIZE does not seem to work -- it always starts maximized and I >>> have to minimize it manually. Hints on that? >> >> Using -name to set the xemacs resource name does not set the window class >> name, apparently by design [1], so this style directive will not match the >> window title or window class name of your xemacs window. >> >> Fortunately, you could probably achieve the same effect by adding the >> '-iconic' command line option to the xemacs invocation. > > Actually, -iconic does not work; neither does it work to set the iconic > resource to true. Seems to be an xemacs thing. In fact, here is a quote > from the FAQ: > > "Ugh, this stuff is such an incredible mess that I've about given up getting > it to work. The principal problem is numerous window-manager bugs... " :-) > However, I find that the .XWinrc MINIMIZE style *does* work ... but of course > only for windows I create later. And the class name is "emacs", not "xemacs", > hence a STYLE entry of: emacs MINIMIZE ... > > Does this suggest to you any other way that might work to get an iconified > xemacs from the .startxwinrc file? We seem to be talking past each other here. The .XWinrc you attached does not specify a style for the 'emacs' class. > STYLES { > console MINIMIZE > Eliot MINIMIZE > xemacs1 MINIMIZE > } Adding 'emacs MINIMIZE' seems to work for me (although it does appear that the window is created normal and then minimized, which a bit ugly, but that's a consequence of the order we do things at window creation time) -- 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 moss@cs.umass.edu Sat Apr 7 16:46:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Sat, 07 Apr 2012 16:46:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F806901.2010507@dronecode.org.uk> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> Message-ID: <4F806F46.2040007@cs.umass.edu> > All I can really say is that it works for me. If run isn't doing it's job for > you, I don't know why. > > You might like to take a look at using the xlaunch package to start your > Xserver and see if that behaves any better. Ok ... >> Does this suggest to you any other way that might work to get an iconified >> xemacs from the .startxwinrc file? > > We seem to be talking past each other here. The .XWinrc you attached does not > specify a style for the 'emacs' class. Yes; I changed it, and was reporting on the changed .XWinrc. > Adding 'emacs MINIMIZE' seems to work for me (although it does appear that the > window is created normal and then minimized, which a bit ugly, but that's a > consequence of the order we do things at window creation time) Right, but this affects only windows launched manually from the XWin menu, not ones launched from .startxwinrc. Maybe xlaunch can help with both issues :-) ... I'll look into it ... Thanks! Eliot -- 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 7 17:04:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 07 Apr 2012 17:04:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-3 (TEST) Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-3 *** xorg-server-common-1.12.0-3 *** xorg-server-dmx-1.12.0-3 *** xorg-server-extra-1.12.0-3 *** xorg-server-devel-1.12.0-3 These packages contain XWin and the other X.Org X11 servers. This package is currently available as a test release, and will be made stable in approximately one week if no major regressions are reported. The following cygwin-specific changes have been made since 1.12.0-2: * Fix WM_HINTS bitmap icon conversion (Reported by Eliot Moss) * Fix a crash in icon regeneration on XWinrc reload (Reported by Eliot Moss) ac3e4e1d7b759b638330b2cebddc58d6 *xorg-server-1.12.0-3.tar.bz2 50ca03394b4740410359052307e7f3e0 *xorg-server-common-1.12.0-3.tar.bz2 3a5b860bbeea10cb753190f073ebb378 *xorg-server-devel-1.12.0-3.tar.bz2 36b39a094485836eef8de5b99b53a2d8 *xorg-server-dmx-1.12.0-3.tar.bz2 f41c5ad483013ac22f44652ed20d0197 *xorg-server-extra-1.12.0-3.tar.bz2 79f8452f1cb5b4983c6d49b058e8d243 *xorg-server-1.12.0-3-src.tar.bz2 -- 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 moss@cs.umass.edu Sat Apr 7 17:44:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Sat, 07 Apr 2012 17:44:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-3 (TEST) In-Reply-To: References: Message-ID: <4F807CD6.6030109@cs.umass.edu> Thank you, Jon. I am having more success in getting my initial windows looking the way I think they should when I use xlaunch. However, at present on my system xlaunch has one show stopper: When I start XWin with it, XWin cannot start any items from the XWin menu (the one set up by .XWinrc). I click and nothing appears to happen. The Exit button (etc.) are active. Regards -- Eliot -- 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 7 17:45:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 07 Apr 2012 17:45:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F806F46.2040007@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> Message-ID: <4F807D4E.9030207@dronecode.org.uk> On 07/04/2012 17:45, Eliot Moss wrote: >>> Does this suggest to you any other way that might work to get an iconified >>> xemacs from the .startxwinrc file? >> >> We seem to be talking past each other here. The .XWinrc you attached does not >> specify a style for the 'emacs' class. > > Yes; I changed it, and was reporting on the changed .XWinrc. > >> Adding 'emacs MINIMIZE' seems to work for me (although it does appear that the >> window is created normal and then minimized, which a bit ugly, but that's a >> consequence of the order we do things at window creation time) > > Right, but this affects only windows launched manually from the > XWin menu, not ones launched from .startxwinrc. I'm not sure if you are labouring under a misapprehension due to poor documentation, or reporting a bug here. The STYLE directive adjusts the window styling of all windows which match the specified class or window name, it shouldn't matter how the application which created that window was started, be it from the XWin menu, from ~/.startxwinrc or from a terminal. If it does matter how the application was started, then that is a bug. -- 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 moss@cs.umass.edu Sat Apr 7 17:53:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Sat, 07 Apr 2012 17:53:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series In-Reply-To: <4F807D4E.9030207@dronecode.org.uk> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> Message-ID: <4F807F21.2030500@cs.umass.edu> On 4/7/2012 1:45 PM, Jon TURNEY wrote: > On 07/04/2012 17:45, Eliot Moss wrote: > I'm not sure if you are labouring under a misapprehension due to poor > documentation, or reporting a bug here. > > The STYLE directive adjusts the window styling of all windows which match the > specified class or window name, it shouldn't matter how the application which > created that window was started, be it from the XWin menu, from ~/.startxwinrc > or from a terminal. If it does matter how the application was started, then > that is a bug. I think I was confused. I had tried to apply STYLE MINIMIZE based on a misunderstanding of how xemacs named its windows. When I use STYLE emacs MINIMIZE, it matches the window name and seems to work all the time. Of course this means that manually launched ones also start minimized, which wasn't my intent, but is livable. It does seem that xemacs is deeply confused about this whole how-to-start thing, as its FAQ observes :-) ... Thanks -- E -- 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 angelo.graziosi@alice.it Sat Apr 7 22:11:00 2012 From: angelo.graziosi@alice.it (Angelo Graziosi) Date: Sat, 07 Apr 2012 22:11:00 -0000 Subject: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] In-Reply-To: <4F7F427C.3070900@alice.it> References: <4F7F427C.3070900@alice.it> Message-ID: <4F80BB85.503@alice.it> Il 06/04/2012 21.22, Angelo Graziosi ha scritto: > > Any way I will try to follow your recipe to reproduce the problem, but I > am sure it is still there.. No, it isn't! I have run Emacs for more than 14 hours and I haven't see any problem. I have done that strictly following your recipe... Ciao, Angelo. -- 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 Sun Apr 8 11:18:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Sun, 08 Apr 2012 11:18:00 -0000 Subject: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] In-Reply-To: <4F80BB85.503@alice.it> References: <4F7F427C.3070900@alice.it> <4F80BB85.503@alice.it> Message-ID: <4F81740E.3090003@cornell.edu> On 4/7/2012 6:11 PM, Angelo Graziosi wrote: > Il 06/04/2012 21.22, Angelo Graziosi ha scritto: > >> >> Any way I will try to follow your recipe to reproduce the problem, but I >> am sure it is still there.. > > No, it isn't! > > I have run Emacs for more than 14 hours and I haven't see any problem. I > have done that strictly following your recipe... Hi Angelo, That's great news. Thank you very much for testing. Now I just have to figure out why it doesn't work on my system. Would you mind sending me your cygcheck output off-list so I can see how my setup differs from yours? I wonder if I need some GNOME-related package. Or it could be BLODA. What anti-virus software do you use (if any)? Thanks. 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 angelo.graziosi@alice.it Sun Apr 8 14:10:00 2012 From: angelo.graziosi@alice.it (Angelo Graziosi) Date: Sun, 08 Apr 2012 14:10:00 -0000 Subject: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] In-Reply-To: <4F80BB85.503@alice.it> References: <4F7F427C.3070900@alice.it> <4F80BB85.503@alice.it> Message-ID: <4F819C48.2070603@alice.it> Ken Brown wrote: > Would you mind sending me your cygcheck output Attached... > What anti-virus software do you use (if any)? Microsoft Security Essential (MSE)... I would be glad if someone could teach me how do not use an AV on Windows... ;-) Ciao, Angelo. -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out.bz2 Type: application/octet-stream Size: 18448 bytes Desc: not available URL: -------------- next part -------------- -- 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 Bennett.Tony@con-way.com Mon Apr 9 15:54:00 2012 From: Bennett.Tony@con-way.com (Bennett, Tony) Date: Mon, 09 Apr 2012 15:54:00 -0000 Subject: FW: RE: Cut and Paste between X and WindowsXP sometimes fails In-Reply-To: <9E085D377965634187A85638358AE61101A117CA9A@DCXPRCL017.cnf.prod.cnf.com> References: <9E085D377965634187A85638358AE611019DFABBFC@DCXPRCL017.cnf.prod.cnf.com> <4F3BC068.7060108@dronecode.org.uk> <9E085D377965634187A85638358AE611019E094E1B@DCXPRCL017.cnf.prod.cnf.com> <4F3FCF3C.8090001@dronecode.org.uk> <9E085D377965634187A85638358AE61101A117CA9A@DCXPRCL017.cnf.prod.cnf.com> Message-ID: <9E085D377965634187A85638358AE61101BCEE1050@DCXPRCL017.cnf.prod.cnf.com> Jon, The fix continues to work well... ...will this fix be integrated into X soon...??? -tony -----Original Message----- From: Jon TURNEY Sent: Saturday, February 18, 2012 8:18 AM Subject: Re: FW: RE: Cut and Paste between X and WindowsXP sometimes fails On 15/02/2012 16:26, Bennett, Tony wrote: > Given that I'd have to "build" xclipboard for the host that I'm XDMCPing to, > and that host is running AIX... Sadly, I may just have to "live" with the problem. > > Is there any hope that the issue will be corrected in the foreseeable future...??? Well, looking at the rate of progress on fd.o bug #5735, it seems reasonable to hope that it will be fixed in a year or two :-) I've applied the patch I've suggested there to today's snapshot, uploaded a at [1]. Perhaps you could try that out and see if that improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20120218-git-c3b936a38812f88b.exe.bz2 ----------------------------- Jon, I downloaded, bunzip2, and installed the new version of Xwin. I restarted Xwin using the new version. I ran some preliminary cut and paste tests, and it seems to work correctly... i.e. I can perform multiple "cut from Xwin & Paste to WinXP", without intervening "cut from WinXP & Paste to Xwin" without error. I will continue running the new version while I perform my daily work, and will advise you if I have a recurrence of the problem. Thanks a lot for this temporary fix. -tony -- 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/ From kbrown@cornell.edu Mon Apr 9 21:34:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 09 Apr 2012 21:34:00 -0000 Subject: Problems with emacs built with gsettings support In-Reply-To: <4F80BB85.503@alice.it> References: <4F7F427C.3070900@alice.it> <4F80BB85.503@alice.it> Message-ID: <4F8355E4.60609@cornell.edu> On 4/7/2012 6:11 PM, Angelo Graziosi wrote: > Il 06/04/2012 21.22, Angelo Graziosi ha scritto: > >> >> Any way I will try to follow your recipe to reproduce the problem, but I >> am sure it is still there.. > > No, it isn't! > > I have run Emacs for more than 14 hours and I haven't see any problem. I > have done that strictly following your recipe... I can confirm that it seems to work fine on Windows XP. But I have two Windows 7 computers on which it still consistently fails. I'm searching for BLODA, but in the meantime, it would be helpful if someone else could test it on Windows 7. I'd like to know if it's a general problem on Windows 7 or something specific to my systems. The recipe is in http://cygwin.com/ml/cygwin-xfree/2012-04/msg00024.html Thanks. 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 angelo.graziosi@alice.it Mon Apr 9 22:41:00 2012 From: angelo.graziosi@alice.it (Angelo Graziosi) Date: Mon, 09 Apr 2012 22:41:00 -0000 Subject: Problems with emacs built with gsettings support In-Reply-To: <4F819C48.2070603@alice.it> References: <4F7F427C.3070900@alice.it> <4F80BB85.503@alice.it> <4F819C48.2070603@alice.it> Message-ID: <4F836587.3000607@alice.it> Ken Brown wrote: > But I have two Windows 7 computers on which it still consistently fails. I'm searching for BLODA, but in the meantime, it would be helpful if someone else could test it on Windows 7 I am afraid, I haven't a Windows 7 box :-( Ciao, Angelo. -- 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 moss@cs.umass.edu Wed Apr 11 10:24:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Wed, 11 Apr 2012 10:24:00 -0000 Subject: Issue with XWin under xlaunch Message-ID: <4F855BAC.7010809@cs.umass.edu> Dear Jon (et al.) -- Perhaps this problem report was buried in the discussion of the taskbar appearance issue and was therefore overlooked .... When I start XWin using xlaunch, trying to the start programs from the .XWinrc popup menu (right-click on the X icon, left-click on the program's entry in the menu), programs do not start. I get only those programs started by my script that I told xlaunch to run. I would like to use xlaunch, since it solves the issue I had with the startxwin taskbar icon being visible (when I claim it should not be, and it didn't use to be), but not being able to start additional programs makes this approach less useable. Looking at this from outside, it is hard to say whether the real issue is in xlaunch, in XWin, or the result of some misunderstanding between them. Regards -- Eliot Moss -- 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 moss@cs.umass.edu Wed Apr 11 10:34:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Wed, 11 Apr 2012 10:34:00 -0000 Subject: Initial xemacs iconization (was Re: Taskbar appearance changes between xorg-server 11 series and 12.0 series) In-Reply-To: <4F807F21.2030500@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> Message-ID: <4F855E33.4000803@cs.umass.edu> In the end, I was able to address my xemacs initial window appearance under cygwin xfree in this way: 1) First, xemacs does not handle -iconic or the iconized resource properly. I found it best not to set them. 2) The command line -name argument will override all the X resources, so if not really what I wanted (I'd have to create a whole new set of settings -- might be useful for some users or under other circumstances). 3) The window name / title argument was what I ended up using, thus: xemacs -T xemacs Since the default class name for xemacs windows is emacs, I can match all windows in .XWinrc using emacs, and thus minimize them all using: STYLES { emacs MINIMIZE } If I want to minimize just the one window created in (3) above, I can write: STYLES { xemacs MINIMIZE } It's all logical in its own idiosyncratic way, I suppose ... Eliot -- 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 moss@cs.umass.edu Wed Apr 11 10:40:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Wed, 11 Apr 2012 10:40:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F807F21.2030500@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> Message-ID: <4F855F7E.10202@cs.umass.edu> Dear Jon (et al.): Here's an interesting new bit of evidence. When playing around with xlaunch configurations and such, I ran startxwin several times this morning. ONCE, X came up without the iconized StartXWin window (i.e., things displayed as they used to before I upgraded xorg-server). This makes me suspect that there may be some kind of timing-related behavior. Perhaps the relevant code did not change between releases, but other changes affected relative timing of various actions, exposing a latent bug or race condition. I am happy to switch the xlaunch, though, if the separate issue with XWin when started under xlaunch can be resolved. Regards, and thanks again for your efforts in maintaining this complex beast! Eliot Moss -- 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 doris.luo@derferchemical.com Thu Apr 12 08:17:00 2012 From: doris.luo@derferchemical.com (eileen) Date: Thu, 12 Apr 2012 08:17:00 -0000 Subject: chemicals material just need Message-ID: <20120412161613203566122@derferchemical.com> Dear Sir/Ms, Have a nice day !Glad to hear that you're on the market for Chemicals. We specialize in this field from 1998, with good quality and pretty competitive price.Should you have any questions, pls do not hesitate to contact me. Tks &br Your sincerely Eileen Company: Xi'an Derfer Chemical Co., LtdAddress: 2-1-1904 of TianLunMingZhu Mansion, No.60 Zhuque Avenue,Xi?an ,Shanxi,China Tel: 86-029-68982833 Fax: 86-029-68982833 Email:doris.luo@derferchemical.comMSN: xiaoying891127@live.cnWebsite: www.derferchemical.com -------------- From M.Aitchison@cyberXpress.co.nz Thu Apr 12 21:49:00 2012 From: M.Aitchison@cyberXpress.co.nz (Mark Aitchison) Date: Thu, 12 Apr 2012 21:49:00 -0000 Subject: Using Infra-red (or any) remote controls with cygwin?? Message-ID: <4F874DE3.90609@cyberXpress.co.nz> Is there any way to use a remote control (e.g. an infra-red remote that comes with a TV tuner) with cygwin applications? Preferably so that arrow and number keys can be used with standard X11 applications (even better if odd keys like "Red" can be remapped), but I'd settle for any way to act on some keypresses from a distance on some box about the size of a remote rather than a full-sized keyboard. Any suggestions?? Mark Aitchison, New Zealand. -- 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 charles.e.sheridan@ericsson.com Fri Apr 13 02:30:00 2012 From: charles.e.sheridan@ericsson.com (Charles Sheridan) Date: Fri, 13 Apr 2012 02:30:00 -0000 Subject: Workaround & Possible Cause - "Failed to activate core device - Could not invoke xkbcomp" on Failed X Server Launch Message-ID: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se> Hi all, This week, after upgrading my Cygwin installation for the first time since ~April of 2011, X server startup failed, with the below oft-reported entries at the end of /cywin/var/log/xwin/Xwin.0.log -- ... [ 10092.016] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 10092.235] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm [ 10092.235] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 10092.313] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm [ 10092.313] XKB: Failed to compile keymap [ 10092.313] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 10092.313] Fatal server error: [ 10092.313] Failed to activate core devices. [ 10092.313] Server terminated with error (1). Closing log file. This occurs on startup attempts from Xwin, startx, & startxwin. I have not previously seen X server startup failure, over 10 years of Cygwin-X use on several different mswin machines. X server startup failure persists after Cygwin re-installation following an HP Vista Enterprise laptop reboot, without any Cygwin processes running, and despite post-install run of several recommended variations on `rebaseall` -- `rebaseall -b 0x77000000` under both ash & dash, and without the -b arg. => WORKAROUND: The new "Xlaunch" in the All Programs/Cygwin-X dir off the Windows Start Button starts X without issue. => POSSIBLE CAUSE: The same Xwin.0.log errors are reported in several X windows fora for platforms other than Cygwin. The first link below is a long entry in a Debian forum concluding that the issue relates to a problematic memory module, that can be bypassed via the "nopat" option to XWin. I couldn't get the Cygwin XWin cmd to recognize this option. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646987 This link is a Google search on "x server nopat option" http://www.google.com/webhp?rlz=1C1CHFX_enUS410US410&sourceid=chrome-instant&ix=seb&ie=UTF-8#hl=en&rlz=1C1CHFX_enUS410US410&sclient=psy-ab&q=x+server+nopat+option&oq=x+server+nopat+option&aq=f&aqi=&aql=&gs_l=hp.3...21501l55842l0l56000l42l29l0l2l2l7l149l2856l13j15l29l0.frgbld.&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.,cf.osb&fp=af73696fe4de10c7&ix=seb&biw=1180&bih=914 The attached cygcheck.out.edited has removed the env vars/aliases from my Cygwin session. Regards, Charles Sheridan -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out.edited Type: application/octet-stream Size: 264102 bytes Desc: cygcheck.out.edited URL: -------------- next part -------------- -- 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 Fri Apr 13 12:57:00 2012 From: JOEL.MOOTS@L-3com.com (JOEL.MOOTS@L-3com.com) Date: Fri, 13 Apr 2012 12:57:00 -0000 Subject: Using Infra-red (or any) remote controls with cygwin?? In-Reply-To: <4F874DE3.90609@cyberXpress.co.nz> References: <4F874DE3.90609@cyberXpress.co.nz> Message-ID: <615935CE76907149AFEC6599C969D4D5099FB5BC@XCGTXH01.corp.eos.l-3com.com> > Is there any way to use a remote control (e.g. an infra-red remote that > comes with a TV tuner) with cygwin applications? > Preferably so that arrow and number keys can be used with standard X11 > applications (even better if odd keys like "Red" can be remapped), but > I'd settle for any way to act on some keypresses from a distance on some > box about the size of a remote rather than a full-sized keyboard. Any > suggestions?? I believe lirc has a Windows equivalent, so assuming you have an IR receiver, you could try that out (I haven't but don't see why it wouldn't work for Cygwin/X applications too). Alternatively, you could just buy one of those remote-sized, wireless, usb keyboards. -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 joerg_ml@bitplanet.de Sat Apr 14 15:29:00 2012 From: joerg_ml@bitplanet.de (=?iso-8859-1?Q?J=F6rg_Mensmann?=) Date: Sat, 14 Apr 2012 15:29:00 -0000 Subject: [PATCH] Fix command line arguments for multiple monitors Message-ID: Hi, placing the X server on a specific monitor using something like "-screen 0 @2" is broken since November. The attached patch restores the old behaviour. ciao J?rg -------------- next part -------------- A non-text attachment was scrubbed... Name: xwin-multi-monitor-fix.patch Type: text/x-patch Size: 1090 bytes Desc: not available URL: -------------- next part -------------- -- 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 Sun Apr 15 12:20:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Sun, 15 Apr 2012 12:20:00 -0000 Subject: Problems with emacs built with gsettings support In-Reply-To: <4F8355E4.60609@cornell.edu> References: <4F7F427C.3070900@alice.it> <4F80BB85.503@alice.it> <4F8355E4.60609@cornell.edu> Message-ID: <4F8ABCFC.7050103@cornell.edu> I haven't made in progress in trying to debug this problem. I think I will probably have to build the next release of emacs without GSettings support. (This is a shame, but it's not a regression; emacs has never had the possibility of supporting GSettings prior to emacs-24.) If there are any emacs users out there who care about this, read on. First, here's a summary of what I know. Everything I say is independent of whether I build emacs with gtk2 or gtk3. * If emacs is built with GSettings support, it seems to work fine on Windows XP. * It also works fine on my 64-bit Windows 7 systems if I export GSETTINGS_BACKEND=memory * It fails on my Windows 7 systems otherwise. The failure consists of emacs crashing with a segmentation fault shortly after it starts. This could happen after a few minutes or a few hours, but it always happens. * I haven't found any indication that this is a BLODA problem, but I can't rule it out either. It would be very helpful if other people could try it on Windows 7. Here are the steps for testing, which are simpler than what I posted earlier in the thread: 1. Install my test build of emacs-X11-24.0.95-7 by running setup.exe -K http://sanibeltranquility.com/cygwin/kbrown.gpg and adding http://sanibeltranquility.com/cygwin to the list of mirrors. This was built with gtk3, so you'll have to let setup install a bunch of dependencies unless you already have libgtk3_0 installed. 2. Start the X server using the Start Menu shortcut, with no ~/.startxwinrc. 3. In the resulting xterm window: eval `dbus-launch --sh-syntax` emacs -Q & 4. Wait a few hours, if necessary, to see if emacs crashes. You can use it or just leave it alone (but don't use it for anything important). 5. Send a note to the list reporting success or failure, with details about your system. 6. If it fails, you can rerun setup.exe to restore your previous version of emacs. Or, if you'd like, you can install my build of emacs-X11-24.0.95-6, which was built without GSettings support. Thanks in advance to anyone who is willing to test. 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 magl@Safe-mail.net Mon Apr 16 08:19:00 2012 From: magl@Safe-mail.net (magl@Safe-mail.net) Date: Mon, 16 Apr 2012 08:19:00 -0000 Subject: Glyph substitution Message-ID: Glyph substitution doesn't works on cygwin using fontconfig, xft. Missing glyphs won't get replaced from ones existing in other fonts. Couldn't figure out why. Freshly installed cygwin. Anyone can report, that it should work? -- 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 16 13:46:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 16 Apr 2012 13:46:00 -0000 Subject: dbus-launch --exit-with-session fails when run from .startxwinrc Message-ID: <4F8C224B.3090103@cornell.edu> The following problem occurs on my 64-bit Windows 7 system but not on my XP system. I start the X server using the Start Menu shortcut [modified to add -emulate3buttons] and a .startxwinrc with the following contents: eval `dbus-launch --sh-syntax --exit-with-session` xterm Running ps in the resulting xterm window shows no dbus-launch or dbus-daemon process. But I can give the same dbus-launch command in the xterm window, and the processes start as expected. I'm attaching cygcheck output and the XWin log. My hope in reporting this is that the problem I'm seeing (and the difference between XP and Win7) is somehow related to the emacs problem I've been trying to solve: http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html Ken P.S. You'll see in the cygcheck output that I'm running a Cygwin snapshot; but nothing changes if I revert to cygwin-1.7.13-1. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: cygcheck.out URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: XWin.0.log URL: -------------- next part -------------- -- 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 16 13:50:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 16 Apr 2012 13:50:00 -0000 Subject: dbus-launch --exit-with-session fails when run from .startxwinrc In-Reply-To: <4F8C224B.3090103@cornell.edu> References: <4F8C224B.3090103@cornell.edu> Message-ID: <4F8C2388.7090900@cornell.edu> On 4/16/2012 9:44 AM, Ken Brown wrote: > The following problem occurs on my 64-bit Windows 7 system but not on my > XP system. > > I start the X server using the Start Menu shortcut [modified to add > -emulate3buttons] and a .startxwinrc with the following contents: > > eval `dbus-launch --sh-syntax --exit-with-session` > xterm > > Running ps in the resulting xterm window shows no dbus-launch or > dbus-daemon process. But I can give the same dbus-launch command in the > xterm window, and the processes start as expected. I'm attaching > cygcheck output and the XWin log. > > My hope in reporting this is that the problem I'm seeing (and the > difference between XP and Win7) is somehow related to the emacs problem > I've been trying to solve: > > http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html > > Ken > > P.S. You'll see in the cygcheck output that I'm running a Cygwin > snapshot; but nothing changes if I revert to cygwin-1.7.13-1. I forgot to say that if I remove "--exit-with-session" from the command line in my .startxwinrc, then a dbus-daemon process does start. 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 cygwin@tlinx.org Tue Apr 17 05:21:00 2012 From: cygwin@tlinx.org (Linda Walsh) Date: Tue, 17 Apr 2012 05:21:00 -0000 Subject: Glyph substitution In-Reply-To: References: Message-ID: <4F8CFDBC.5000405@tlinx.org> magl@Safe-mail.net wrote: > Glyph substitution doesn't works on cygwin using fontconfig, xft. > Missing glyphs won't get replaced from ones existing in other fonts. > Couldn't figure out why. > Freshly installed cygwin. > Anyone can report, that it should work? ---- What would make you think it should work? I.e. where are you reading that it should work? Sounds neat...if it did... -- 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 konrad.schwarz@siemens.com Tue Apr 17 07:55:00 2012 From: konrad.schwarz@siemens.com (Schwarz, Konrad) Date: Tue, 17 Apr 2012 07:55:00 -0000 Subject: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues) Message-ID: <9B10FEAACF062F48A095880A451FF0590727D95C07@DEMCHP99E84MSX.ww902.siemens.net> Hello, an easy work around for the problem that cscope and its variant mlcscope cannot deal with paths containing spaces under Cygwin is to replace such paths with their DOS short name equivalents, since these do not contain spaces. The error surfaces as the error message mlcscope: cannot read trailer offset from file ./cscope.out and in that mlcscope recreates the program database each time it is started. When starting cscope using relative paths (the most frequent case), eliminating spaces must be done for the current working directory. The cygpath utility comes in handy for this. E.g., invoking mlcscope as (cd $(cygpath -u $(cygpath -d "$PWD"));mlcscope -b) solves the problem. In the above line, the inner call to cygpath converts the working directory to DOS format, the outer call converts the result to Cygwin format; preserving the short names of DOS, but replacing backslashes with forward slashes, for example. Unfortunately, it is not possible to combine the -u and -d flags in a single invocation of cygpath; this would be a useful extension. Regards, Konrad Schwarz P.S.: Sorry for resurrecting an old thread from Jan 2007. However, this thread seems to be the only place the problem was discussed. -- 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 Tue Apr 17 08:07:00 2012 From: marco.atzeri@gmail.com (marco atzeri) Date: Tue, 17 Apr 2012 08:07:00 -0000 Subject: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues) In-Reply-To: <9B10FEAACF062F48A095880A451FF0590727D95C07@DEMCHP99E84MSX.ww902.siemens.net> References: <9B10FEAACF062F48A095880A451FF0590727D95C07@DEMCHP99E84MSX.ww902.siemens.net> Message-ID: <4F8D24B9.2070505@gmail.com> On 4/17/2012 9:55 AM, Schwarz, Konrad wrote: > Hello, > > an easy work around for the problem that cscope and its variant mlcscope > cannot deal with paths containing spaces under Cygwin is to replace such paths > with their DOS short name equivalents, since these do not contain spaces. the easy solution is to not use paths with space in cygwin > > Regards, > Konrad Schwarz > > > P.S.: Sorry for resurrecting an old thread from Jan 2007. However, this thread > seems to be the only place the problem was discussed. the right way is to open a new thread, not resurrecting the dead. Things are changed in 5 years 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 jon.turney@dronecode.org.uk Tue Apr 17 10:02:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 17 Apr 2012 10:02:00 -0000 Subject: [PATCH] Fix command line arguments for multiple monitors In-Reply-To: References: Message-ID: <4F8D3FBE.50007@dronecode.org.uk> On 14/04/2012 16:28, J??rg Mensmann wrote: > placing the X server on a specific monitor using something like > "-screen 0 @2" is broken since November. The attached patch restores the > old behaviour. Thanks very much for investigating this issue and for the patch. I'll include this in the next X server build. > This happened since commit 3ead1d810b0e157078db39712e02ea6dc85216d8, > because EnumDisplayMonitor() returns FALSE if its callback function > returns FALSE (which is not clearly documented), and QueryMonitor() > would then also return FALSE. I don't observe this behaviour on my test machine, EnumDisplayMonitor() returns TRUE, so I'd be interested to know what version of Windows you are using. I am a little concerned that I can't find any evidence using google of anyone else reporting having the MonitorEnumProc callback function return FALSE to terminate the enumeration causes EnumDisplayMonitor() to return 0, indicating failure, so maybe there is something else going on here... -- 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 Apr 17 10:51:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 17 Apr 2012 10:51:00 -0000 Subject: Workaround & Possible Cause - "Failed to activate core device - Could not invoke xkbcomp" on Failed X Server Launch In-Reply-To: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se> References: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se> Message-ID: <4F8D4B2A.6010208@dronecode.org.uk> On 13/04/2012 03:30, Charles Sheridan wrote: > This week, after upgrading my Cygwin installation for the first time since ~April of 2011, X server startup failed, with the below oft-reported entries at the end of /cywin/var/log/xwin/Xwin.0.log -- > > ... > [ 10092.016] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 > [ 10092.235] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm > [ 10092.235] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 10092.313] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm > [ 10092.313] XKB: Failed to compile keymap > [ 10092.313] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. > [ 10092.313] > Fatal server error: > [ 10092.313] Failed to activate core devices. > [ 10092.313] Server terminated with error (1). Closing log file. > > This occurs on startup attempts from Xwin, startx, & startxwin. > > I have not previously seen X server startup failure, over 10 years of Cygwin-X use on several different mswin machines. > > X server startup failure persists after Cygwin re-installation following an HP Vista Enterprise laptop reboot, without any Cygwin processes running, and despite post-install run of several recommended variations on `rebaseall` -- `rebaseall -b 0x77000000` under both ash & dash, and without the -b arg. > > => WORKAROUND: The new "Xlaunch" in the All Programs/Cygwin-X dir off the Windows Start Button starts X without issue. > > => POSSIBLE CAUSE: The same Xwin.0.log errors are reported in several X windows fora for platforms other than Cygwin. The first link below is a long entry in a Debian forum concluding that the issue relates to a problematic memory module, that can be bypassed via the "nopat" option to XWin. I couldn't get the Cygwin XWin cmd to recognize this option. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646987 Read more carefully. "nopat" is a linux kernel option, which is being used there to work-around a kernel bug. So all that bug tells you is when running the xkbcomp program at xserver startup fails, you get these error messages. -- 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 Apr 17 11:43:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 17 Apr 2012 11:43:00 -0000 Subject: FW: RE: Cut and Paste between X and WindowsXP sometimes fails In-Reply-To: <9E085D377965634187A85638358AE61101BCEE1050@DCXPRCL017.cnf.prod.cnf.com> References: <9E085D377965634187A85638358AE611019DFABBFC@DCXPRCL017.cnf.prod.cnf.com> <4F3BC068.7060108@dronecode.org.uk> <9E085D377965634187A85638358AE611019E094E1B@DCXPRCL017.cnf.prod.cnf.com> <4F3FCF3C.8090001@dronecode.org.uk> <9E085D377965634187A85638358AE61101A117CA9A@DCXPRCL017.cnf.prod.cnf.com> <9E085D377965634187A85638358AE61101BCEE1050@DCXPRCL017.cnf.prod.cnf.com> Message-ID: <4F8D5764.3060902@dronecode.org.uk> On 09/04/2012 16:53, Bennett, Tony wrote: > The fix continues to work well... > ...will this fix be integrated into X soon...??? Thanks for testing. Unfortunately, this fix seems to break other clipboard uses (In my testing, copying from a native Firefox to cygwin X emacs didn't work anymore), so I need to find the time to look at it some more before I can include it. -- 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 Apr 17 11:51:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 17 Apr 2012 11:51:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F855F7E.10202@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> <4F855F7E.10202@cs.umass.edu> Message-ID: <4F8D594B.50505@dronecode.org.uk> On 11/04/2012 11:39, Eliot Moss wrote: > When playing around with xlaunch configurations and such, > I ran startxwin several times this morning. ONCE, X came > up without the iconized StartXWin window (i.e., things > displayed as they used to before I upgraded xorg-server). > > This makes me suspect that there may be some kind of > timing-related behavior. Perhaps the relevant code did > not change between releases, but other changes affected > relative timing of various actions, exposing a latent > bug or race condition. I'm still not entirely sure what process in running in this window you complain of. Can you be say what the title and contents of this window are? I'm also not sure if this problem is related to he X server at all. Can you try creating a shortcut which runs the following command, for example, and see if the bash window is always successfully hidden? C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "sleep 10" -- 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 marc.girod@gmail.com Tue Apr 17 16:49:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Tue, 17 Apr 2012 16:49:00 -0000 Subject: startx with different displays Message-ID: <33702991.post@talk.nabble.com> I have intermittent problems to start XWin. My client would wait for an accessible server. In recent times, when this happens with :0, I try to use :1 instead, which usually works. Today, the two processes interferred. I was waiting on :0, and as I started a sttrax session on :1, both clients rose up, both reporting DISPLAY=:1! Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33702991.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 Apr 17 17:41:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 17 Apr 2012 17:41:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-4 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-4 *** xorg-server-common-1.12.0-4 *** xorg-server-dmx-1.12.0-4 *** xorg-server-extra-1.12.0-4 *** xorg-server-devel-1.12.0-4 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.12.0-3: * Fix a problem which could prevent multiple monitor support from working on some systems (Thanks to J??rg Mensmann for patch) * If a window has had its taskbar button removed (e.g. by the _NET_WM_STATE_SKIP_TASKBAR hint), disable its minimize button to prevent it becoming lost (Thanks to Colin Harrison for patch) 134fcc78f06512dac97ba3ff8b601b52 *xorg-server-1.12.0-4.tar.bz2 6639dda222775a2046246cfa5c6f1aaf *xorg-server-common-1.12.0-4.tar.bz2 71aff2a88b9860269da2899910a69740 *xorg-server-devel-1.12.0-4.tar.bz2 677e7b631aca77cf1ce14d5de571679e *xorg-server-dmx-1.12.0-4.tar.bz2 224d9f4af8d68d556f91853e8e6cfcc5 *xorg-server-extra-1.12.0-4.tar.bz2 6fcb163089f7b78530ee1e145725ffc5 *xorg-server-1.12.0-4-src.tar.bz2 -- 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 joerg_ml@bitplanet.de Tue Apr 17 20:09:00 2012 From: joerg_ml@bitplanet.de (=?iso-8859-1?Q?J=F6rg_Mensmann?=) Date: Tue, 17 Apr 2012 20:09:00 -0000 Subject: [PATCH] Fix command line arguments for multiple monitors In-Reply-To: <4F8D3FBE.50007@dronecode.org.uk> (Jon TURNEY's message of "Tue, 17 Apr 2012 11:02:38 +0100") References: <4F8D3FBE.50007@dronecode.org.uk> Message-ID: Jon TURNEY wrote: > I'll include this in the next X server build. Thanks! > I don't observe this behaviour on my test machine, EnumDisplayMonitor() > returns TRUE, so I'd be interested to know what version of Windows you are using. The problem appeared on a Windows 7 machine with two monitors connected. I will run some additional tests to find out what exactly makes the function return FALSE in this case. ciao J?rg -- 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 Tue Apr 17 23:15:00 2012 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Tue, 17 Apr 2012 23:15:00 -0000 Subject: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues) In-Reply-To: <4F8D24B9.2070505@gmail.com> References: <9B10FEAACF062F48A095880A451FF0590727D95C07@DEMCHP99E84MSX.ww902.siemens.net> <4F8D24B9.2070505@gmail.com> Message-ID: On Tue, Apr 17, 2012 at 2:07 AM, marco atzeri wrote: > the easy solution is to not use paths with space in cygwin Not so easy. Cygwin inherits the Windows path, and I have several directories in my Windows PATH with spaces in them. -- 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 agravivek@gmail.com Wed Apr 18 04:44:00 2012 From: agravivek@gmail.com (Vivek Agarwal) Date: Wed, 18 Apr 2012 04:44:00 -0000 Subject: "cscope -d" can't find trailer offset if path contains space (was: vim mlcscope interface issues) In-Reply-To: References: <9B10FEAACF062F48A095880A451FF0590727D95C07@DEMCHP99E84MSX.ww902.siemens.net> <4F8D24B9.2070505@gmail.com> Message-ID: On 4/18/12, Jim Reisert AD1C wrote: > On Tue, Apr 17, 2012 at 2:07 AM, marco atzeri wrote: > >> the easy solution is to not use paths with space in cygwin > > Not so easy. Cygwin inherits the Windows path, and I have several > directories in my Windows PATH with spaces in them. > > -- > 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/ > > -- Thanks & Regards, Vivek Agarwal -- 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 moss@cs.umass.edu Wed Apr 18 08:13:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Wed, 18 Apr 2012 08:13:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F8D594B.50505@dronecode.org.uk> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> <4F855F7E.10202@cs.umass.edu> <4F8D594B.50505@dronecode.org.uk> Message-ID: <4F8E77A0.1000809@cs.umass.edu> On 4/17/2012 7:51 AM, Jon TURNEY wrote: > On 11/04/2012 11:39, Eliot Moss wrote: > I'm still not entirely sure what process in running in this window you > complain of. Can you be say what the title and contents of this window are? Thank you for following up, Jon! The title of the window in question is StartXWin. It has no perceivable content - I cannot de-iconize it. Its only real evidence on the screen is the task bar icon. > I'm also not sure if this problem is related to he X server at all. Can you > try creating a shortcut which runs the following command, for example, and see > if the bash window is always successfully hidden? > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "sleep 10" I see no window (well, it flashes for a brief moment) and no icon. The bash runs -- I can see it in the task manager, and then it goes away after the appointed 10 seconds. My StartXWin shortcut has: Shortcut panel: target: C:\cygwin\bin\run.exe /bin/bash -l -c "/bin/startxwin -- -unixkill -clipboard -multimonitors -resize -engine 1 -emulate3buttons 100 -wm -auth /home/Eliot/.Xauthority" Start in: C:\cygwin\bin Shortcut key: none Run: Normal window Comment: blank Advanced...: Run as admin not checked General panel: nothing interesting Compatibility panel: nothing checked Security panel: nothing adjusted Other panels have nothing adjustable This is starting to look like some kind of race as xorg-server is starting .. Regards -- Eliot -- 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 joerg_ml@bitplanet.de Wed Apr 18 18:49:00 2012 From: joerg_ml@bitplanet.de (=?iso-8859-1?Q?J=F6rg_Mensmann?=) Date: Wed, 18 Apr 2012 18:49:00 -0000 Subject: [PATCH] Fix command line arguments for multiple monitors In-Reply-To: (=?iso-8859-1?Q?=22J=F6rg?= Mensmann"'s message of "Tue, 17 Apr 2012 22:09:34 +0200") References: <4F8D3FBE.50007@dronecode.org.uk> Message-ID: Hi, I've now completed some additional tests, and it seems that the return value of EnumDisplayMonitors() really depends on the return value of its callback on my system. Here is the minimal test case: static wBOOL CALLBACK getMonitorInfoTestTRUE(HMONITOR hMonitor, HDC hdc, LPRECT rect, LPARAM _data) { return TRUE; } static wBOOL CALLBACK getMonitorInfoTestFALSE(HMONITOR hMonitor, HDC hdc, LPRECT rect, LPARAM _data) { return FALSE; } Inserted into QueryMonitor(): wBOOL result; result = EnumDisplayMonitors(NULL, NULL, getMonitorInfoTestTRUE, (LPARAM) data); ErrorF("getMonitorInfoTestTRUE returns: %d\n", (int)result); result = EnumDisplayMonitors(NULL, NULL, getMonitorInfoTestFALSE, (LPARAM) data); ErrorF("getMonitorInfoTestFALSE returns: %d\n", (int)result); When running "Xwin.exe :0 -screen 0 @1" this prints: getMonitorInfoTestTRUE returns: 1 getMonitorInfoTestFALSE returns: 0 I get the same results even when only one monitor is connected. If you can't reproduce this on your machine, then maybe it is related to the graphics driver. My configuration is NVIDIA 285.62 on Windows 7 (64-bit). ciao J?rg -- 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 moss@cs.umass.edu Thu Apr 19 10:01:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Thu, 19 Apr 2012 10:01:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F8E77A0.1000809@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> <4F855F7E.10202@cs.umass.edu> <4F8D594B.50505@dronecode.org.uk> <4F8E77A0.1000809@cs.umass.edu> Message-ID: <4F8FE26E.2030002@cs.umass.edu> On 4/18/2012 4:13 AM, Eliot Moss wrote: > On 4/17/2012 7:51 AM, Jon TURNEY wrote: >> On 11/04/2012 11:39, Eliot Moss wrote: > Thank you for following up, Jon! > > The title of the window in question is StartXWin. > It has no perceivable content - I cannot de-iconize it. > Its only real evidence on the screen is the task bar icon. I'm not sure whether I've passed on the sequence of things that happens in terms of what is visible: 1) As StartXWin starts, the screen flashes briefly, a common artifact of run.exe. 2) Then the icon is *not* visible. 3) xorg-server starts and displays its icon, and the StartXWin icon appears. I am not sure whether there is a perceivable ordering here. I'll perhaps try it a few times to see. This suggests that it is something about xorg-server starting and trying to decide which icons to display. IIRC, the StartXWin icon appears before my xterm icons do, but then STartXWin is already running, and the xterms get fired off by the .startxwinrc file. Best -- Eliot -- 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 h.p.kiehl@fz-juelich.de Thu Apr 19 10:50:00 2012 From: h.p.kiehl@fz-juelich.de (Kiehl, Horst) Date: Thu, 19 Apr 2012 10:50:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F8FE26E.2030002@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> <4F855F7E.10202@cs.umass.edu> <4F8D594B.50505@dronecode.org.uk> <4F8E77A0.1000809@cs.umass.edu> <4F8FE26E.2030002@cs.umass.edu> Message-ID: <4094A9D4E3EC2544B795DFEA610AE88C180E37CED6@IBT040.ibt-w2k.kfa-juelich.de> Eliot Moss wrote: > On 4/18/2012 4:13 AM, Eliot Moss wrote: >> On 4/17/2012 7:51 AM, Jon TURNEY wrote: >>> On 11/04/2012 11:39, Eliot Moss wrote: >> The title of the window in question is StartXWin. >> It has no perceivable content - I cannot de-iconize it. >> Its only real evidence on the screen is the task bar icon. > >I'm not sure whether I've passed on the sequence of things >that happens in terms of what is visible: > >1) As StartXWin starts, the screen flashes briefly, a common >artifact of run.exe. > >2) Then the icon is *not* visible. > >3) xorg-server starts and displays its icon, and the StartXWin icon >appears. I am not sure whether there is a perceivable ordering >here. I'll perhaps try it a few times to see. > >This suggests that it is something about xorg-server starting and >trying to decide which icons to display. IIRC, the StartXWin icon >appears before my xterm icons do, but then STartXWin is already >running, and the xterms get fired off by the .startxwinrc file. I have xorg-server 1.12.0-4; I observed similar behaviour. There was a separate taskbar icon, apparently without a window, and the xterm with a shell that was started because I used startxwin (without specifying an X client); the xterm had its own taskbar icon. When I closed that xterm, its icon and also the "startxwin icon" disappeared (with XWin continuing to run, as expected). Also, since I use 1.12.0-x, the XWin -displayfd option does not work anymore for me: Started through startxwin, XWin doesn't complete starting (after " Trying to create socket for display number 0" is displayed); started directly from bash, XWin crashes due to a "Segmentation fault" right after this point. (I didn't report this because I haven't tested it on other machines yet.) Best regards, Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5734 bytes Desc: not available URL: From moss@cs.umass.edu Thu Apr 19 11:04:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Thu, 19 Apr 2012 11:04:00 -0000 Subject: Taskbar appearance changes between xorg-server 11 series and 12.0 series (more) In-Reply-To: <4F8FE26E.2030002@cs.umass.edu> References: <4F7DC041.6070500@cs.umass.edu> <4F7F2174.6060209@dronecode.org.uk> <4F7FBBEF.1040204@cs.umass.edu> <4F806901.2010507@dronecode.org.uk> <4F806F46.2040007@cs.umass.edu> <4F807D4E.9030207@dronecode.org.uk> <4F807F21.2030500@cs.umass.edu> <4F855F7E.10202@cs.umass.edu> <4F8D594B.50505@dronecode.org.uk> <4F8E77A0.1000809@cs.umass.edu> <4F8FE26E.2030002@cs.umass.edu> Message-ID: <4F8FF10E.8090703@cs.umass.edu> On 4/19/2012 6:01 AM, Eliot Moss wrote: > On 4/18/2012 4:13 AM, Eliot Moss wrote: >> On 4/17/2012 7:51 AM, Jon TURNEY wrote: >>> On 11/04/2012 11:39, Eliot Moss wrote: > 1) As StartXWin starts, the screen flashes briefly, a common > artifact of run.exe. > > 2) Then the icon is *not* visible. > > 3) xorg-server starts and displays its icon, and the StartXWin icon > appears. I am not sure whether there is a perceivable ordering > here. I'll perhaps try it a few times to see. I tried some more: The StartXWin and xorg-server icons come up simultaneously as far as my eye perceives. xterm and xemacs icons, for jobs started by startxwin, come up later. Once those things finish that StartXwin started, the StartXWin icon remains, *until* I right click the xorg-server icon to get its menu -- then the StartXWin icon goes away (presumably xorg-server is just then perceiving the termination of StartXWin). In hope that these various details are helpful in narrowing down the location in the code that may be at issue -- Eliot -- 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 ynnor@mm.st Fri Apr 20 10:43:00 2012 From: ynnor@mm.st (Ronald Fischer) Date: Fri, 20 Apr 2012 10:43:00 -0000 Subject: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory Message-ID: <1334918608.30888.140661064975773.553D6443@webmail.messagingengine.com> My setup so far (which is working well), was to use Xming as X-Server and putty for logging into our Solaris hosts via ssh. Since I have Cygwin installed, I thought I could use its ssh equally well, so I exported the ssh key from putty to the format understood by ssh, and used the following bash command to login to the Solaris host: DISPLAY=:0.0 TERM=xterm ssh -p 22 -K -X -i MyPrivateKeyFile MyUserName@SolarisHost When I now try to start an X application, I get an error message like this connect /tmp/.X11-unix/X0: No such file or directory XIO: fatal IO error 131 (Connection reset by peer) on X server "SolarisHost:239.0" after 0 requests (0 known processed) with 0 events remaining. Further investigation reveals the following: (1) I start my putty login, and find that on the remote host DISPLAY is set to (say): SolarisHost:261.0 Starting X applications works fine. (2) I start my open ssh login from Cygwin, and find that the DISPLAY variable is set to a different value, for example SolarisHost:239.0 . Starting X applications does not work. (3) In the latter shell, I export DISPLAY=SolarisHost:261.0 . Starting X applications now works. The fact that each login produces a different value for DISPLAY, is normal behaviour. Even when starting several putty sessions, each gets a different value for DISPLAY, and X apps work in all of them. It seems that by doing the ssh connection via putty, something is done which is missing from my ssh started from Cygwin. BTW, I also tried to use -Y instead of -X in my ssh invocation, but with no effect. Ronald -- Ronald Fischer + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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 Fri Apr 20 18:54:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 20 Apr 2012 18:54:00 -0000 Subject: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory In-Reply-To: <1334918608.30888.140661064975773.553D6443@webmail.messagingengine.com> References: <1334918608.30888.140661064975773.553D6443@webmail.messagingengine.com> Message-ID: <4F91B0C1.2000905@dronecode.org.uk> On 20/04/2012 11:43, Ronald Fischer wrote: > My setup so far (which is working well), was to use Xming as X-Server > and putty for logging into our Solaris hosts via ssh. Since I have > Cygwin installed, I thought I could use its ssh equally well, so I > exported the ssh key from putty to the format understood by ssh, and > used the following bash command to login to the Solaris host: > > DISPLAY=:0.0 TERM=xterm ssh -p 22 -K -X -i MyPrivateKeyFile > MyUserName@SolarisHost > > When I now try to start an X application, I get an error message like > this > > connect /tmp/.X11-unix/X0: No such file or directory > XIO: fatal IO error 131 (Connection reset by peer) on X server > "SolarisHost:239.0" > after 0 requests (0 known processed) with 0 events remaining. I think I know what's going on here. cygwin ssh understands DISPLAY=:0.0 to mean to connect to the X server for display 0 via a local (UNIX domain) socket, named /tmp/.X11-unix/X0 The Xming X server, not being a cygwin application, cannot listen on that socket. The solution should be to use DISPLAY=localhost:0.0 instead, which means to connect to the X server for display 0 via TCP/IP, which the Xming X server should be listening on. See FAQ 1.6 [1] for more details. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#display-and-screen -- 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 ynnor@mm.st Mon Apr 23 08:55:00 2012 From: ynnor@mm.st (Ronald Fischer) Date: Mon, 23 Apr 2012 08:55:00 -0000 Subject: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory In-Reply-To: <4F91B0C1.2000905@dronecode.org.uk> References: <1334918608.30888.140661064975773.553D6443@webmail.messagingengine.com> <4F91B0C1.2000905@dronecode.org.uk> Message-ID: <1335171307.8031.140661066049181.482D47B5@webmail.messagingengine.com> On Fri, Apr 20, 2012, at 19:53, Jon TURNEY wrote: > On 20/04/2012 11:43, Ronald Fischer wrote: > > My setup so far (which is working well), was to use Xming as X-Server > > and putty for logging into our Solaris hosts via ssh. Since I have > > Cygwin installed, I thought I could use its ssh equally well, so I > > exported the ssh key from putty to the format understood by ssh, and > > used the following bash command to login to the Solaris host: > > > > DISPLAY=:0.0 TERM=xterm ssh -p 22 -K -X -i MyPrivateKeyFile > > MyUserName@SolarisHost > > > > When I now try to start an X application, I get an error message like > > this > > > > connect /tmp/.X11-unix/X0: No such file or directory > > XIO: fatal IO error 131 (Connection reset by peer) on X server > > "SolarisHost:239.0" > > after 0 requests (0 known processed) with 0 events remaining. > > I think I know what's going on here. > > The solution should be to use DISPLAY=localhost:0.0 instead, which means > to > connect to the X server for display 0 via TCP/IP, which the Xming X > server > should be listening on. Nice idea, but the result is, that I just get a different error message. Now it becomes: connect localhost port 6000: Connection refused X connection to SolarisHost:217.0 broken (explicit kill or server shutdown). >From the FAQ, I see that port 6000 is the default. Could it be that I need to specify somehow a non-standard port? Ronald -- Ronald Fischer + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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 marc.girod@gmail.com Mon Apr 23 09:34:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Mon, 23 Apr 2012 09:34:00 -0000 Subject: startx with different displays In-Reply-To: <33702991.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> Message-ID: <33732045.post@talk.nabble.com> Hi, I try a fresh start, not being clear about my complete failure to get any reply. I use XWin and GNU emacs (X11 version). My startup script is: /usr/bin/startx /usr/bin/emacs -g 90x37+150+0 -- /usr/bin/X :0 -multiwindow -clipboard This used to work for a few years, but recently started to loop and fail (plus 2 glitches). First the loop effect: after starting the server process (transcript not displayed in the first occurrence), which ends in: winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. ...the transcript gets into: waiting for X server to begin accepting connections . .. .. This eventually times out, unless sometimes gets a reply. However, recently, I have started to try different displays in parallel, e.g.: bash --login -c "/usr/bin/startx /usr/bin/emacs -g 90x37+150+0 -- /usr/bin/X :2 -multiwindow -clipboard" I have started to use higher and higher numbers. The effect is that one of then (today: 5) will unblock all the others, so that I got today 5 instances of GNU emacs, all reported a DISPLAY of ":5". The two glitches: Before starting the server, I get: /usr/bin/startx: line 47: 2188 Segmentation fault (core dumped) expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1 At connecting, the first line is: xinit: XFree86_VT property unexpectedly has 0 items instead of 1 I notice that I have an old startx~, which helps me to see what has changed in recent versions of startx: bin> diff startx~ startx 34a35,43 > # Automatically determine an unused $DISPLAY > d=0 > while true ; do > [ -e /tmp/.X$d-lock ] || break > d=$(($d + 1)) > done > defaultdisplay=":$d" > unset d > 79c88 < # if no client arguments either, use rc file instead --- > # For compatibility reasons, only use startxrc if there were no client > command line arguments 92,93d100 < < clientargs=$defaultclientargs 96a104,108 > # if no client arguments, use defaults > if [ x"$clientargs" = x ]; then > clientargs=$defaultclientargs > fi > 101c113 < # if no server arguments or display either, use defaults --- > # For compatibility reasons, only use xserverrc if there were no > server command line arguments 103d114 < # For compatibility reasons, only use xserverrc if there were no server command line arguments 109,111d119 < < serverargs=$defaultserverargs < display=$defaultdisplay 114a123,132 > # if no server arguments, use defaults > if [ x"$serverargs" = x ]; then > serverargs=$defaultserverargs > fi > > # if no display, use default > if [ x"$display" = x ]; then > display=$defaultdisplay > fi > 155a174 > touch "$xserverauthfile" bin> ll startx startx~ -rwxr-xr-x 1 emagiro root 4917 Jan 30 03:12 startx -rwxr-xr-x 1 emagiro root 4540 Aug 22 2011 startx~ bin> ll /tmp/.X* -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:38 /tmp/.X0-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:40 /tmp/.X1-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:42 /tmp/.X2-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:43 /tmp/.X3-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:44 /tmp/.X4-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:45 /tmp/.X5-lock /tmp/.X11-unix: total 38 drwxrwxrwt+ 1 root root 0 Apr 23 09:45 . drwxrwxrwt+ 1 emagiro root 0 Apr 23 09:45 .. srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:38 X0 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:40 X1 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:42 X2 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:43 X3 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:44 X4 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:45 X5 I don't attempt here to interpret these facts myself. I am of course mostly annoyed by the failure to connect to the XWin server using the first port. Can anybody shed light on a possible explanation? I used Gmane and uploaded my cygcheck.out. Thanks, Marc http://old.nabble.com/file/p33732045/cygcheck.out cygcheck.out -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33732045.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 marc.girod@gmail.com Mon Apr 23 09:48:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Mon, 23 Apr 2012 09:48:00 -0000 Subject: startx with different displays In-Reply-To: <33732045.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> Message-ID: <33732071.post@talk.nabble.com> Marc Girod wrote: > > I used Gmane and uploaded my cygcheck.out. > Incidentally, I saw there: Warning: There are multiple cygwin1.dlls on your path So, I checked: bin> for d in $(echo $PATH | tr : '\n'); do if [ -r $d/cygwin1.dll ]; then echo $d; fi; done /usr/bin /usr/bin bin> echo $PATH | tr : '\n' /usr/local/bin /usr/bin /usr/local/bin /usr/bin /cygdrive/c/Windows/system32 /cygdrive/c/Windows /cygdrive/c/Windows/System32/Wbem /cygdrive/c/strawberry/c/bin /cygdrive/c/strawberry/perl/site/bin /cygdrive/c/strawberry/perl/bin /cygdrive/c/Program Files/WIDCOMM/Bluetooth Software /cygdrive/c/Program Files/Rational/common /cygdrive/c/Program Files/Rational/ClearCase/bin /cygdrive/c/Program Files/Rational/ClearCase/etc /cygdrive/c/Program Files/Rational/ClearCase/etc/utils /cygdrive/c/Sysinternals /cygdrive/c/Program Files/Microsoft Windows Performance Toolkit I plead non guilty of the duplication of /usr/local/bin:/usr/bin in $PATH. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33732071.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 MBardiaux@mediaxim.be Mon Apr 23 11:56:00 2012 From: MBardiaux@mediaxim.be (Michel Bardiaux) Date: Mon, 23 Apr 2012 11:56:00 -0000 Subject: XWin 1.12.0-4 crash Message-ID: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD8@bespdc01.mediaxim.local> Nothing much to add to the 2 attached files - except that my X worked fine until the last update. Will try reverting to previous version. Greetings, (s) M. Bardiaux -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 86876 bytes Desc: cygcheck.out URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 87695 bytes Desc: XWin.0.log URL: -------------- next part -------------- -- 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 23 12:17:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 23 Apr 2012 12:17:00 -0000 Subject: XWin 1.12.0-4 crash In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD8@bespdc01.mediaxim.local> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD8@bespdc01.mediaxim.local> Message-ID: <4F954858.2020202@dronecode.org.uk> On 23/04/2012 12:55, Michel Bardiaux wrote: > Nothing much to add to the 2 attached files - except that my X worked > fine until the last update. Will try reverting to previous version. >From the log timestamps, this looks like a crash at startup. Is that correct? Thanks very much for reporting this problem. There should be an XWin.exe.stackdump file produced by the crash, if you could attach that, that would be helpful. Even more helpful would be following the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. If your crash is at startup, you will need to modify the instruction slightly, start X using 'gdb --args XWin -multiwindow' rather than trying to attach to a running XWin. [1] http://x.cygwin.com/devel/backtrace.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 Mon Apr 23 12:22:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 23 Apr 2012 12:22:00 -0000 Subject: [PATCH] Fix command line arguments for multiple monitors In-Reply-To: References: <4F8D3FBE.50007@dronecode.org.uk> Message-ID: <4F954969.3030304@dronecode.org.uk> On 18/04/2012 19:48, J??rg Mensmann wrote: > I've now completed some additional tests, and it seems that the return > value of EnumDisplayMonitors() really depends on the return value of its > callback on my system. Here is the minimal test case: Thanks for the test case. Yes, you are quite correct. I wasn't testing what I thought I was testing, so, in fact, I do see the same behaviour as you. Mystery solved :-) -- 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 23 12:31:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 23 Apr 2012 12:31:00 -0000 Subject: Glyph substitution In-Reply-To: References: Message-ID: <4F954B92.7030509@dronecode.org.uk> On 16/04/2012 09:19, magl@Safe-mail.net wrote: > Glyph substitution doesn't works on cygwin using fontconfig, xft. > Missing glyphs won't get replaced from ones existing in other fonts. > Couldn't figure out why. > Freshly installed cygwin. > Anyone can report, that it should work? This is a complex topic, and "It doesn't work" is not very helpful in diagnosing the problem So, again, see http://cygwin.com/problems.html I believe that a modern application using pango and xft should be capable of doing some glyph substitution. xedit not so much :-) Some facts which might be considered relevant: 1) Which application you are using? 2) Which glyph you are expecting to get substituted? 3) Which font you are using which doesn't have that font? 4) Which font you expect the subsituted glyph to come from? 5) Some evidence that this works correctly for the same software on other OS, and is a Cygwin specific problem? -- 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 MBardiaux@mediaxim.be Mon Apr 23 13:04:00 2012 From: MBardiaux@mediaxim.be (Michel Bardiaux) Date: Mon, 23 Apr 2012 13:04:00 -0000 Subject: XWin 1.12.0-4 crash Message-ID: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> Yes, it is a crash at startup. I could not find XWin.exe.stackdump anywhere on my hard drive. I have attached the bat script (renamed into .txt) used to start cygwin/X, maybe I need to modify it. Would it work to add CYGWIN='error_start=c:\cygwin\bin\dumper.exe' in the system environment (meaning, via the control panel), to have a core file that I could then open with gdb? -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: besdev01 - mgt.txt URL: -------------- next part -------------- -- 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 23 13:51:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 23 Apr 2012 13:51:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F855BAC.7010809@cs.umass.edu> References: <4F855BAC.7010809@cs.umass.edu> Message-ID: <4F955E58.8060403@dronecode.org.uk> On 11/04/2012 11:23, Eliot Moss wrote: > When I start XWin using xlaunch, trying to the start > programs from the .XWinrc popup menu (right-click on > the X icon, left-click on the program's entry in the > menu), programs do not start. I get only those programs > started by my script that I told xlaunch to run. > > I would like to use xlaunch, since it solves the issue > I had with the startxwin taskbar icon being visible > (when I claim it should not be, and it didn't use to > be), but not being able to start additional programs > makes this approach less useable. > > Looking at this from outside, it is hard to say whether > the real issue is in xlaunch, in XWin, or the result of > some misunderstanding between them. At the moment, the output from processes started from the notification area icon doesn't go anywhere useful, which can make it hard to debug problems with processes started this way. I've added some code to capture stdout and stderr from these subprocesses to the X server log, and to more clearly diagnose problems which could occur while fork/exec-ing them. Perhaps you could try the snapshot at [1] and see if this gives a bit more information about why these processes are failing? [1] ftp://cygwin.com/pub/cygwinx/XWin.20120423-git-638383315ef51e46.exe.bz2 -- 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 reply-to-list-only-lh@cygwin.com Mon Apr 23 14:55:00 2012 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Mon, 23 Apr 2012 14:55:00 -0000 Subject: startx with different displays In-Reply-To: <33732071.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> Message-ID: <4F956D3E.5000408@cygwin.com> On 4/23/2012 5:47 AM, Marc Girod wrote: > Incidentally, I saw there: > > Warning: There are multiple cygwin1.dlls on your path > > So, I checked: > > bin> for d in $(echo $PATH | tr : '\n'); do if [ -r $d/cygwin1.dll ]; then > echo $d; fi; done > /usr/bin > /usr/bin > bin> echo $PATH | tr : '\n' > /usr/local/bin > /usr/bin > /usr/local/bin > /usr/bin > /cygdrive/c/Windows/system32 > /cygdrive/c/Windows > /cygdrive/c/Windows/System32/Wbem > /cygdrive/c/strawberry/c/bin > /cygdrive/c/strawberry/perl/site/bin > /cygdrive/c/strawberry/perl/bin > /cygdrive/c/Program Files/WIDCOMM/Bluetooth Software > /cygdrive/c/Program Files/Rational/common > /cygdrive/c/Program Files/Rational/ClearCase/bin > /cygdrive/c/Program Files/Rational/ClearCase/etc > /cygdrive/c/Program Files/Rational/ClearCase/etc/utils > /cygdrive/c/Sysinternals > /cygdrive/c/Program Files/Microsoft Windows Performance Toolkit > > I plead non guilty of the duplication of /usr/local/bin:/usr/bin in $PATH. Get rid of the real dups. You only need the one in /usr/bin. -- 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 kbrown@cornell.edu Mon Apr 23 15:04:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 23 Apr 2012 15:04:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F955E58.8060403@dronecode.org.uk> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> Message-ID: <4F956F70.4080900@cornell.edu> On 4/23/2012 9:51 AM, Jon TURNEY wrote: > On 11/04/2012 11:23, Eliot Moss wrote: >> When I start XWin using xlaunch, trying to the start >> programs from the .XWinrc popup menu (right-click on >> the X icon, left-click on the program's entry in the >> menu), programs do not start. I get only those programs >> started by my script that I told xlaunch to run. >> >> I would like to use xlaunch, since it solves the issue >> I had with the startxwin taskbar icon being visible >> (when I claim it should not be, and it didn't use to >> be), but not being able to start additional programs >> makes this approach less useable. >> >> Looking at this from outside, it is hard to say whether >> the real issue is in xlaunch, in XWin, or the result of >> some misunderstanding between them. > > At the moment, the output from processes started from the notification area > icon doesn't go anywhere useful, which can make it hard to debug problems with > processes started this way. > > I've added some code to capture stdout and stderr from these subprocesses to > the X server log, and to more clearly diagnose problems which could occur > while fork/exec-ing them. Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc? I'm hoping it might help with the problem I reported in http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html BTW, I tried the snapshot at ftp://cygwin.com/pub/cygwinx/XWin.20120423-git-638383315ef51e46.exe.bz2 and the resulting log has a lot of messages like this: winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) Is that to be expected, or does it indicate a real problem? 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 moss@cs.umass.edu Mon Apr 23 16:42:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Mon, 23 Apr 2012 16:42:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F955E58.8060403@dronecode.org.uk> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> Message-ID: <4F95864B.1090802@cs.umass.edu> Ok -- by perusing the log I figured it out ... In the past, .XWinrc names of files such as "xterm" worked just fine. Apparently something changed about the PATH used, and "xterm" was not being found. When I write /usr/bin/xterm, it starts up. You can see the first case and the second in the attached log file. So, I think xlaunch is ok, but this was a surprising difference :-) ... Regards -- Eliot Moss -------------- next part -------------- InitConnectionLimits: MaxClients = 255 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.12.0.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Snapshot: 20120423-git-638383315ef51e46 XWin was started with the following command line: XWin :0 -multiwindow -clipboard -nowgl -ac -unixkill -clipboard -resize -engine 1 -emulate3buttons 100 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1280 h 800 winInitializeScreenDefaults - native DPI x 96 y 96 ddxProcessArgument - arg: :0 ddxProcessArgument - arg: -multiwindow ddxProcessArgument - arg: -clipboard ddxProcessArgument - arg: -nowgl ddxProcessArgument - arg: -ac ddxProcessArgument - arg: -unixkill ddxProcessArgument - arg: -clipboard ddxProcessArgument - arg: -resize ddxProcessArgument - arg: -engine ddxProcessArgument - arg: -emulate3buttons [727789.342] (II) xorg.conf is not supported [727789.342] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [727789.342] LoadPreferences: Loading /home/Eliot/.XWinrc [727789.358] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [727789.358] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [727789.358] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [727789.358] winDetectSupportedEngines - Returning, supported engines 0000001f [727789.358] winSetEngine - Multi Window or Rootless => ShadowGDI [727789.358] winScreenInit - Using Windows display depth of 32 bits per pixel [727789.389] winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 800 depth: 32 [727789.389] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [727789.389] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [727789.389] winInitMultiWindowWM - Calling pthread_mutex_lock () [727789.389] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [727789.389] MIT-SHM extension disabled due to lack of kernel support [727789.405] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [727789.436] (II) AIGLX: Loaded and initialized swrast [727789.436] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [727789.436] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [727789.514] winPositionWindowMultiWindow: (x, y) = (0, 0) [727789.514] immediately return since hWnd is NULL [727789.514] winMapWindowMultiWindow - pWin: 800bb6c0 [727789.514] winUpdateWindowsWindow [727789.529] System: `"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "/cygdrive/c/Users/Eliot/AppData/Local/Temp/xkb_J7a79Q" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/var/lib/xkb/server-0.xkm"' [727789.670] Loaded XKB keymap /var/lib/xkb/server-0.xkm, defined=0x7f [727789.670] winPointerWarpCursor - Discarding first warp: 640 400 [727789.670] (dix) initialising device 6 [727789.670] (--) 8 mouse buttons found [727789.670] (dix) initialising device 7 [727789.670] (--) Setting autorepeat to delay=500, rate=31 [727789.670] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [727789.670] (--) Found matching XKB configuration "English (USA)" [727789.670] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [727789.670] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [727789.670] (dix) enabling device 6 [727789.670] (dix) enabling device 7 [727789.670] client(0): Reserved pid(14444). [727789.670] client(0): Reserved cmdname(XWin) and cmdargs(:0 -multiwindow -clipboard -nowgl -ac -unixkill -clipboard -resize -engine 1 -emulate3buttons 100). [727789.670] winBlockHandler - pthread_mutex_unlock() [727789.670] winInitMultiWindowWM - pthread_mutex_lock () returned. [727789.670] winInitMultiWindowWM - pthread_mutex_unlock () returned. [727789.670] winInitMultiWindowWM - DISPLAY=:0.0 [727789.670] client(200000): Reserved pid(-1). [727789.670] client(200000): Reserved cmdname(NULL) and cmdargs(NULL). [727789.670] AllocNewConnection: client index = 1, socket fd = 7 [727789.670] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [727789.670] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [727789.670] winProcEstablishConnection - winInitClipboard returned. [727789.670] winMultiWindowXMsgProc - DISPLAY=:0.0 [727789.670] winClipboardProc - DISPLAY=:0.0 [727789.670] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [727789.670] client(400000): Reserved pid(-1). [727789.685] client(400000): Reserved cmdname(NULL) and cmdargs(NULL). [727789.685] AllocNewConnection: client index = 2, socket fd = 9 [727789.685] client(600000): Reserved pid(-1). [727789.685] client(600000): Reserved cmdname(NULL) and cmdargs(NULL). [727789.685] AllocNewConnection: client index = 3, socket fd = 11 [727789.685] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [727789.685] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [727789.685] winMultiWindowWMProc () [727789.685] winPositionWindowMultiWindow: (x, y) = (1, 1) [727789.685] immediately return since hWnd is NULL [727789.701] client(800000): Reserved pid(-1). [727789.701] client(800000): Reserved cmdname(NULL) and cmdargs(NULL). [727789.701] AllocNewConnection: client index = 4, socket fd = 13 [727790.980] client(a00000): Reserved pid(-1). [727790.980] client(a00000): Reserved cmdname(NULL) and cmdargs(NULL). [727790.980] AllocNewConnection: client index = 5, socket fd = 14 [727791.074] client(a00000): Released pid(-1). [727791.074] client(a00000): Released cmdline(NULL) and cmdargs(NULL). [727791.136] client(a00000): Reserved pid(-1). [727791.136] client(a00000): Reserved cmdname(NULL) and cmdargs(NULL). [727791.136] AllocNewConnection: client index = 5, socket fd = 14 [727791.168] client(a00000): Released pid(-1). [727791.168] client(a00000): Released cmdline(NULL) and cmdargs(NULL). [727791.246] client(a00000): Reserved pid(-1). [727791.246] client(a00000): Reserved cmdname(NULL) and cmdargs(NULL). [727791.246] AllocNewConnection: client index = 5, socket fd = 14 [727791.324] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.324] immediately return since hWnd is NULL [727791.324] MoveWindowMultiWindow to (0, 0) [727791.324] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.324] immediately return since hWnd is NULL [727791.324] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.324] immediately return since hWnd is NULL [727791.355] client(c00000): Reserved pid(-1). [727791.355] client(c00000): Reserved cmdname(NULL) and cmdargs(NULL). [727791.355] AllocNewConnection: client index = 6, socket fd = 15 [727791.355] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] winSendMessageToWM () [727791.355] winSendMessageToWM () [727791.355] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] winSendMessageToWM () [727791.355] Queue Size 2 2 [727791.355] winMultiWindowWMProc - 727791355 ms MSG: 1038 ID: 0 [727791.355] ResizeWindowMultiWindow to (0, 0) - 1121x651 [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] ResizeWindowMultiWindow to (0, 0) - 1121x651 [727791.355] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.355] immediately return since hWnd is NULL [727791.355] MoveWindowMultiWindow to (4, 0) [727791.355] winPositionWindowMultiWindow: (x, y) = (4, 0) [727791.355] immediately return since hWnd is NULL [727791.355] winPositionWindowMultiWindow: (x, y) = (4, 0) [727791.355] immediately return since hWnd is NULL [727791.370] winSendMessageToWM () [727791.370] winSendMessageToWM () [727791.386] Queue Size 3 3 [727791.386] winMultiWindowWMProc - 727791386 ms MSG: 1038 ID: 0 [727791.386] Queue Size 2 2 [727791.386] winMultiWindowWMProc - 727791386 ms MSG: 1038 ID: 0 [727791.386] Queue Size 1 1 [727791.386] winMultiWindowWMProc - 727791386 ms MSG: 1038 ID: 0 [727791.402] Queue Size 0 0 [727791.402] winMultiWindowWMProc - 727791402 ms MSG: 1038 ID: 0 [727791.433] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.433] immediately return since hWnd is NULL [727791.433] MoveWindowMultiWindow to (0, 0) [727791.433] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.433] immediately return since hWnd is NULL [727791.433] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.433] immediately return since hWnd is NULL [727791.448] client(e00000): Reserved pid(-1). [727791.448] client(e00000): Reserved cmdname(NULL) and cmdargs(NULL). [727791.448] AllocNewConnection: client index = 7, socket fd = 16 [727791.448] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winSendMessageToWM () [727791.448] winSendMessageToWM () [727791.448] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winSendMessageToWM () [727791.448] ResizeWindowMultiWindow to (0, 0) - 1121x651 [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winSendMessageToWM () [727791.448] ResizeWindowMultiWindow to (0, 0) - 1121x651 [727791.448] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.448] immediately return since hWnd is NULL [727791.448] MoveWindowMultiWindow to (151, 0) [727791.448] winPositionWindowMultiWindow: (x, y) = (151, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winPositionWindowMultiWindow: (x, y) = (151, 0) [727791.448] immediately return since hWnd is NULL [727791.448] winSendMessageToWM () [727791.448] Queue Size 4 4 [727791.448] winMultiWindowWMProc - 727791448 ms MSG: 1038 ID: 0 [727791.495] Queue Size 3 3 [727791.495] winMultiWindowWMProc - 727791495 ms MSG: 1038 ID: 0 [727791.495] Queue Size 2 2 [727791.495] winMultiWindowWMProc - 727791495 ms MSG: 1038 ID: 0 [727791.495] Queue Size 1 1 [727791.495] winMultiWindowWMProc - 727791495 ms MSG: 1038 ID: 0 [727791.495] Queue Size 0 0 [727791.495] winMultiWindowWMProc - 727791495 ms MSG: 1038 ID: 0 [727791.604] winPositionWindowMultiWindow: (x, y) = (152, 1) [727791.604] immediately return since hWnd is NULL [727791.620] winPositionWindowMultiWindow: (x, y) = (152, 1) [727791.620] immediately return since hWnd is NULL [727791.620] winSendMessageToWM () [727791.620] winSendMessageToWM () [727791.620] Queue Size 0 0 [727791.620] winMultiWindowWMProc - 727791620 ms MSG: 1038 ID: 0 [727791.620] winPositionWindowMultiWindow: (x, y) = (152, 1) [727791.620] immediately return since hWnd is NULL [727791.620] winPositionWindowMultiWindow: (x, y) = (405, 6) [727791.620] immediately return since hWnd is NULL [727791.620] winPositionWindowMultiWindow: (x, y) = (291, 6) [727791.620] immediately return since hWnd is NULL [727791.620] winPositionWindowMultiWindow: (x, y) = (157, 6) [727791.620] immediately return since hWnd is NULL [727791.620] Queue Size 0 0 [727791.620] winMultiWindowWMProc - 727791620 ms MSG: 1038 ID: 0 [727791.667] winPositionWindowMultiWindow: (x, y) = (5, 1) [727791.667] immediately return since hWnd is NULL [727791.667] winPositionWindowMultiWindow: (x, y) = (5, 1) [727791.667] immediately return since hWnd is NULL [727791.667] winSendMessageToWM () [727791.667] winSendMessageToWM () [727791.667] Queue Size 0 0 [727791.667] winMultiWindowWMProc - 727791667 ms MSG: 1038 ID: 0 [727791.682] winPositionWindowMultiWindow: (x, y) = (5, 1) [727791.682] immediately return since hWnd is NULL [727791.682] Queue Size 0 0 [727791.682] winMultiWindowWMProc - 727791682 ms MSG: 1038 ID: 0 [727791.682] winPositionWindowMultiWindow: (x, y) = (258, 6) [727791.682] immediately return since hWnd is NULL [727791.682] winPositionWindowMultiWindow: (x, y) = (144, 6) [727791.682] immediately return since hWnd is NULL [727791.682] winPositionWindowMultiWindow: (x, y) = (10, 6) [727791.682] immediately return since hWnd is NULL [727791.792] winMapWindowMultiWindow - pWin: 804d6418 [727791.792] winUpdateWindowsWindow [727791.792] winInitMultiWindowClass - Creating class: cygwin/x X rl [727791.792] winInitMultiWindowClass - Creating class: cygwin/x X child [727791.792] winGetWindowID - Window ID: 10485785 [727791.792] winReorderWindowsMultiWindow - exit because fRestacking == TRUE [727791.792] winAdjustXWindow [727791.792] return because already adjusted [727791.792] winGetWindowID - Window ID: 10485785 [727791.792] winSendMessageToWM () [727791.792] Queue Size 0 0 [727791.792] winMultiWindowWMProc - 727791792 ms MSG: 1032 ID: 7081722 [727791.792] WM_WM_ACTIVATE [727791.807] winSendMessageToWM () [727791.807] Queue Size 0 0 [727791.807] winMultiWindowWMProc - 727791807 ms MSG: 1037 ID: 2664500 [727791.807] WM_WM_MAP3 [727791.807] winTopLevelWindowProc - WM_SIZE to 1121x651 (SIZE_RESTORED) - 727791807 ms [727791.807] winAdjustXWindow [727791.807] return because already adjusted [727791.807] winAdjustXWindow [727791.807] return because already adjusted [727791.807] -winUpdateWindowsWindow [727791.807] winMapWindowMultiWindow - pWin: 804d6c98 [727791.807] winUpdateWindowsWindow [727791.807] -winUpdateWindowsWindow [727791.807] winMapWindowMultiWindow - pWin: 804cb988 [727791.807] winUpdateWindowsWindow [727791.807] -winUpdateWindowsWindow [727791.807] winMapWindowMultiWindow - pWin: 804cba80 [727791.807] winUpdateWindowsWindow [727791.807] -winUpdateWindowsWindow [727791.807] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.807] immediately return since hWnd is NULL [727791.807] winMapWindowMultiWindow - pWin: 804e1088 [727791.807] winUpdateWindowsWindow [727791.807] winGetWindowID - Window ID: 12582937 [727791.807] winReorderWindowsMultiWindow - exit because fRestacking == TRUE [727791.807] winGetWindowID - Window ID: 12582937 [727791.807] winReorderWindowsMultiWindow - exit because fRestacking == TRUE [727791.807] winAdjustXWindow [727791.807] return because already adjusted [727791.807] winGetWindowID - Window ID: 12582937 [727791.807] winSendMessageToWM () [727791.823] winSendMessageToWM () [727791.823] winTopLevelWindowProc - WM_SIZE to 1121x651 (SIZE_RESTORED) - 727791823 ms [727791.823] winAdjustXWindow [727791.823] return because already adjusted [727791.823] winAdjustXWindow [727791.823] return because already adjusted [727791.823] -winUpdateWindowsWindow [727791.823] winMapWindowMultiWindow - pWin: 804e1598 [727791.823] winUpdateWindowsWindow [727791.823] -winUpdateWindowsWindow [727791.823] winMapWindowMultiWindow - pWin: 804e53a8 [727791.823] winUpdateWindowsWindow [727791.823] -winUpdateWindowsWindow [727791.823] winMapWindowMultiWindow - pWin: 804e55d0 [727791.823] winUpdateWindowsWindow [727791.823] -winUpdateWindowsWindow [727791.838] GetWindowName [727791.838] MoveWindowMultiWindow to (0, 0) [727791.838] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.838] immediately return since hWnd is NULL [727791.838] winSendMessageToWM () [727791.838] winSendMessageToWM () [727791.838] winSendMessageToWM () [727791.838] winSendMessageToWM () [727791.854] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.854] immediately return since hWnd is NULL [727791.870] winAdjustXWindow [727791.870] immediately return because the window is iconized [727791.870] MoveWindowMultiWindow to (0, 0) [727791.870] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.870] winPositionWindowMultiWindow - (727791870 ms)drawable (0, 0)-(1121, 651) [727791.870] winPositionWindowMultiWindow - (727791870 ms)rcNew (0, 0)-(1121, 651) [727791.870] winPositionWindowMultiWindow - (727791870 ms)rcOld (0, 743)-(160, 770) [727791.870] (727791870 ms)rcClient (0, 0)-(0, 0) [727791.870] winPositionWindowMultiWindow - Need to move [727791.870] MoveWindow to (0, 0) - 1121x651 [727791.870] winAdjustXWindow [727791.870] immediately return because the window is iconized [727791.870] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (6, 6) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (140, 6) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (254, 6) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.870] immediately return since hWnd is NULL [727791.870] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.870] immediately return since hWnd is NULL [727791.870] CopyWindowMultiWindow [727791.870] winTopLevelWindowProc - WM_SIZE to 0x0 (SIZE_MINIMIZED) - 727791870 ms [727791.870] winAdjustXWindow [727791.870] immediately return because the window is iconized [727791.885] winAdjustXWindow [727791.885] immediately return because the window is iconized [727791.885] winAdjustXWindow [727791.885] immediately return because the window is iconized [727791.885] winAdjustXWindow [727791.885] immediately return because the window is iconized [727791.885] Queue Size 5 5 [727791.885] winMultiWindowWMProc - 727791885 ms MSG: 1032 ID: 0 [727791.885] WM_WM_ACTIVATE [727791.885] Queue Size 4 4 [727791.885] winMultiWindowWMProc - 727791885 ms MSG: 1037 ID: 2664500 [727791.885] WM_WM_MAP3 [727791.885] GetWindowName [727791.916] winAdjustXWindow [727791.916] immediately return because the window is iconized [727791.916] MoveWindowMultiWindow to (0, 0) [727791.916] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.916] winPositionWindowMultiWindow - (727791916 ms)drawable (0, 0)-(1121, 651) [727791.916] winPositionWindowMultiWindow - (727791916 ms)rcNew (0, 0)-(1121, 651) [727791.916] winPositionWindowMultiWindow - (727791916 ms)rcOld (0, 743)-(160, 770) [727791.916] (727791916 ms)rcClient (0, 0)-(0, 0) [727791.916] winPositionWindowMultiWindow - Need to move [727791.916] MoveWindow to (0, 0) - 1121x651 [727791.916] winAdjustXWindow [727791.916] immediately return because the window is iconized [727791.916] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (6, 6) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (140, 6) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (254, 6) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.916] immediately return since hWnd is NULL [727791.916] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.916] immediately return since hWnd is NULL [727791.916] CopyWindowMultiWindow [727791.932] winTopLevelWindowProc - WM_SIZE to 0x0 (SIZE_MINIMIZED) - 727791932 ms [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] Queue Size 3 3 [727791.932] winMultiWindowWMProc - 727791932 ms MSG: 1038 ID: 0 [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.932] winAdjustXWindow [727791.932] immediately return because the window is iconized [727791.948] Queue Size 2 2 [727791.948] winMultiWindowWMProc - 727791948 ms MSG: 1038 ID: 0 [727791.948] winAdjustXWindow [727791.948] immediately return because the window is iconized [727791.948] winAdjustXWindow [727791.948] immediately return because the window is iconized [727791.948] winAdjustXWindow [727791.948] immediately return because the window is iconized [727791.963] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] winSendMessageToWM () [727791.963] winSendMessageToWM () [727791.963] ResizeWindowMultiWindow to (0, 0) - 16x21 [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] winSendMessageToWM () [727791.963] ResizeWindowMultiWindow to (0, 0) - 1051x561 [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] winSendMessageToWM () [727791.963] ResizeWindowMultiWindow to (0, 0) - 1051x561 [727791.963] winPositionWindowMultiWindow: (x, y) = (0, 0) [727791.963] immediately return since hWnd is NULL [727791.963] MoveWindowMultiWindow to (1, 1) [727791.963] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.963] immediately return since hWnd is NULL [727791.963] winPositionWindowMultiWindow: (x, y) = (1, 1) [727791.963] immediately return since hWnd is NULL [727791.963] winSendMessageToWM () [727791.963] Queue Size 6 6 [727791.963] winMultiWindowWMProc - 727791963 ms MSG: 1038 ID: 0 [727791.963] winAdjustXWindow [727791.963] immediately return because the window is iconized [727791.963] winAdjustXWindow [727791.963] immediately return because the window is iconized [727791.963] winAdjustXWindow [727791.963] immediately return because the window is iconized [727791.979] Queue Size 5 5 [727791.979] winMultiWindowWMProc - 727791979 ms MSG: 1038 ID: 0 [727791.994] winAdjustXWindow [727791.994] immediately return because the window is iconized [727791.994] winAdjustXWindow [727791.994] immediately return because the window is iconized [727791.994] winAdjustXWindow [727791.994] immediately return because the window is iconized [727791.994] Queue Size 4 4 [727791.994] winMultiWindowWMProc - 727791994 ms MSG: 1038 ID: 0 [727791.994] Queue Size 3 3 [727791.994] winMultiWindowWMProc - 727791994 ms MSG: 1038 ID: 0 [727791.994] Queue Size 2 2 [727791.994] winMultiWindowWMProc - 727791994 ms MSG: 1038 ID: 0 [727792.010] Queue Size 1 1 [727792.010] winMultiWindowWMProc - 727792010 ms MSG: 1038 ID: 0 [727792.010] Queue Size 0 0 [727792.010] winMultiWindowWMProc - 727792010 ms MSG: 1038 ID: 0 [727792.166] winPositionWindowMultiWindow: (x, y) = (2, 2) [727792.166] immediately return since hWnd is NULL [727792.166] winPositionWindowMultiWindow: (x, y) = (2, 2) [727792.166] immediately return since hWnd is NULL [727792.166] winSendMessageToWM () [727792.166] winSendMessageToWM () [727792.166] Queue Size 0 0 [727792.166] winMultiWindowWMProc - 727792166 ms MSG: 1038 ID: 0 [727792.166] winPositionWindowMultiWindow: (x, y) = (2, 2) [727792.166] immediately return since hWnd is NULL [727792.166] winPositionWindowMultiWindow: (x, y) = (255, 7) [727792.166] immediately return since hWnd is NULL [727792.166] winPositionWindowMultiWindow: (x, y) = (141, 7) [727792.166] immediately return since hWnd is NULL [727792.166] winPositionWindowMultiWindow: (x, y) = (7, 7) [727792.166] immediately return since hWnd is NULL [727792.166] Queue Size 0 0 [727792.166] winMultiWindowWMProc - 727792166 ms MSG: 1038 ID: 0 [727792.275] winMapWindowMultiWindow - pWin: 804d0ce8 [727792.275] winUpdateWindowsWindow [727792.275] winGetWindowID - Window ID: 14680089 [727792.275] winReorderWindowsMultiWindow - exit because fRestacking == TRUE [727792.275] winAdjustXWindow [727792.275] return because already adjusted [727792.275] winGetWindowID - Window ID: 14680089 [727792.275] winSendMessageToWM () [727792.275] Queue Size 0 0 [727792.275] winMultiWindowWMProc - 727792275 ms MSG: 1032 ID: 7081722 [727792.275] WM_WM_ACTIVATE [727792.275] winSendMessageToWM () [727792.275] Queue Size 0 0 [727792.275] winMultiWindowWMProc - 727792275 ms MSG: 1037 ID: 2664500 [727792.275] WM_WM_MAP3 [727792.275] winTopLevelWindowProc - WM_SIZE to 1051x561 (SIZE_RESTORED) - 727792275 ms [727792.275] winAdjustXWindow [727792.275] return because already adjusted [727792.275] winAdjustXWindow [727792.275] return because already adjusted [727792.275] -winUpdateWindowsWindow [727792.275] winMapWindowMultiWindow - pWin: 804cd880 [727792.275] winUpdateWindowsWindow [727792.275] -winUpdateWindowsWindow [727792.291] winMapWindowMultiWindow - pWin: 804e6000 [727792.291] winUpdateWindowsWindow [727792.291] -winUpdateWindowsWindow [727792.291] winMapWindowMultiWindow - pWin: 804cdc60 [727792.291] winUpdateWindowsWindow [727792.291] -winUpdateWindowsWindow [727792.291] client(1000000): Reserved pid(-1). [727792.291] client(1000000): Reserved cmdname(NULL) and cmdargs(NULL). [727792.291] AllocNewConnection: client index = 8, socket fd = 17 [727792.291] GetWindowName [727792.291] winSendMessageToWM () [727792.291] winSendMessageToWM () [727792.306] winAdjustXWindow [727792.306] immediately return because the window is iconized [727792.306] MoveWindowMultiWindow to (0, 0) [727792.306] winPositionWindowMultiWindow: (x, y) = (0, 0) [727792.306] winPositionWindowMultiWindow - (727792306 ms)drawable (0, 0)-(1051, 561) [727792.306] winPositionWindowMultiWindow - (727792306 ms)rcNew (0, 0)-(1051, 561) [727792.306] winPositionWindowMultiWindow - (727792306 ms)rcOld (0, 743)-(160, 770) [727792.306] (727792306 ms)rcClient (0, 0)-(0, 0) [727792.306] winPositionWindowMultiWindow - Need to move [727792.306] MoveWindow to (0, 0) - 1051x561 [727792.306] winAdjustXWindow [727792.306] immediately return because the window is iconized [727792.306] winPositionWindowMultiWindow: (x, y) = (0, 0) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (1, 1) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (6, 6) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (140, 6) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (254, 6) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (1, 1) [727792.306] immediately return since hWnd is NULL [727792.306] winPositionWindowMultiWindow: (x, y) = (1, 1) [727792.306] immediately return since hWnd is NULL [727792.306] CopyWindowMultiWindow [727792.322] winTopLevelWindowProc - WM_SIZE to 0x0 (SIZE_MINIMIZED) - 727792322 ms [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] Queue Size 1 1 [727792.322] winMultiWindowWMProc - 727792322 ms MSG: 1038 ID: 0 [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.322] winAdjustXWindow [727792.322] immediately return because the window is iconized [727792.338] Queue Size 0 0 [727792.338] winMultiWindowWMProc - 727792338 ms MSG: 1038 ID: 0 [727792.338] winAdjustXWindow [727792.338] immediately return because the window is iconized [727792.338] winAdjustXWindow [727792.338] immediately return because the window is iconized [727792.338] winAdjustXWindow [727792.338] immediately return because the window is iconized [727792.790] winPositionWindowMultiWindow: (x, y) = (1, 1) [727792.790] immediately return since hWnd is NULL [727792.790] MoveWindowMultiWindow to (0, 0) [727792.790] winPositionWindowMultiWindow: (x, y) = (0, 0) [727792.790] immediately return since hWnd is NULL [727804.038] winPositionWindowMultiWindow: (x, y) = (1, 1) [727804.038] immediately return since hWnd is NULL [727804.038] winPositionWindowMultiWindow: (x, y) = (1, 1) [727804.038] immediately return since hWnd is NULL [727804.038] winPositionWindowMultiWindow: (x, y) = (2, 2) [727804.038] immediately return since hWnd is NULL [727804.038] winPositionWindowMultiWindow: (x, y) = (1, 31) [727804.038] immediately return since hWnd is NULL [727804.038] winMapWindowMultiWindow - pWin: 80532140 [727804.038] winUpdateWindowsWindow [727804.038] winGetWindowID - Window ID: 16777300 [727804.038] winAdjustXWindow [727804.038] return because already adjusted [727804.038] winGetWindowID - Window ID: 16777300 [727804.038] winSendMessageToWM () [727804.038] Queue Size 0 0 [727804.038] winMultiWindowWMProc - 727804038 ms MSG: 1032 ID: 7081722 [727804.038] WM_WM_ACTIVATE [727804.053] winSendMessageToWM () [727804.053] Queue Size 0 0 [727804.053] winMultiWindowWMProc - 727804053 ms MSG: 1037 ID: 2664500 [727804.053] WM_WM_MAP3 [727804.053] winTopLevelWindowProc - WM_SIZE to 1123x735 (SIZE_RESTORED) - 727804053 ms [727804.053] winAdjustXWindow [727804.053] return because already adjusted [727804.053] winAdjustXWindow [727804.053] return because already adjusted [727804.053] -winUpdateWindowsWindow [727804.053] winMapWindowMultiWindow - pWin: 805323c0 [727804.053] winUpdateWindowsWindow [727804.053] -winUpdateWindowsWindow [727804.053] winMapWindowMultiWindow - pWin: 805325f0 [727804.053] winUpdateWindowsWindow [727804.053] -winUpdateWindowsWindow [727804.053] winMapWindowMultiWindow - pWin: 805324d0 [727804.053] winUpdateWindowsWindow [727804.053] -winUpdateWindowsWindow [727804.053] MoveWindowMultiWindow to (0, 0) [727804.053] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.053] winPositionWindowMultiWindow - (727804053 ms)drawable (0, 0)-(1123, 735) [727804.053] winPositionWindowMultiWindow - (727804053 ms)rcNew (0, 0)-(1123, 735) [727804.053] winPositionWindowMultiWindow - (727804053 ms)rcOld (1, 1)-(1124, 736) [727804.053] (727804053 ms)rcClient (0, 0)-(1123, 735) [727804.053] winPositionWindowMultiWindow - Need to move [727804.053] MoveWindow to (0, 0) - 1123x735 [727804.053] winAdjustXWindow [727804.053] return because already adjusted [727804.053] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.053] immediately return since hWnd is NULL [727804.053] winPositionWindowMultiWindow: (x, y) = (0, 30) [727804.053] immediately return since hWnd is NULL [727804.053] winPositionWindowMultiWindow: (x, y) = (1, 1) [727804.053] immediately return since hWnd is NULL [727804.053] CopyWindowMultiWindow [727804.053] GetWindowName [727804.069] winAdjustXWindow [727804.069] immediately return because the window is iconized [727804.069] winTopLevelWindowProc - WM_SIZE to 0x0 (SIZE_MINIMIZED) - 727804069 ms [727804.069] winAdjustXWindow [727804.069] immediately return because the window is iconized [727804.069] winAdjustXWindow [727804.069] immediately return because the window is iconized [727804.069] winAdjustXWindow [727804.069] immediately return because the window is iconized [727804.069] winAdjustXWindow [727804.069] immediately return because the window is iconized [727804.334] winUnmapWindowMultiWindow - pWin: 805324d0 [727804.365] ResizeWindowMultiWindow to (0, 30) - 1123x668 [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 30) [727804.365] immediately return since hWnd is NULL [727804.365] ResizeWindowMultiWindow to (0, 0) - 1123x668 [727804.365] winSendMessageToWM () [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.365] winSendMessageToWM () [727804.365] Queue Size 0 0 [727804.365] immediately return since hWnd is NULL [727804.365] winMultiWindowWMProc - 727804365 ms MSG: 1038 ID: 0 [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 30) [727804.365] immediately return since hWnd is NULL [727804.365] winPositionWindowMultiWindow: (x, y) = (1, 1) [727804.365] immediately return since hWnd is NULL [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.365] winPositionWindowMultiWindow - (727804365 ms)drawable (0, 0)-(1123, 668) [727804.365] winPositionWindowMultiWindow - (727804365 ms)rcNew (-8, -30)-(1131, 676) [727804.365] winPositionWindowMultiWindow - (727804365 ms)rcOld (-32000, -32000)-(-31840, -31973) [727804.365] (727804365 ms)rcClient (0, 0)-(0, 0) [727804.365] winPositionWindowMultiWindow - Need to move [727804.365] MoveWindow to (-8, -30) - 1139x706 [727804.365] winAdjustXWindow [727804.365] immediately return because the window is iconized [727804.365] winSendMessageToWM () [727804.365] winSendMessageToWM () [727804.365] ResizeWindowMultiWindow to (0, 0) - 1123x668 [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 30) [727804.365] immediately return since hWnd is NULL [727804.365] winPositionWindowMultiWindow: (x, y) = (1, 1) [727804.365] immediately return since hWnd is NULL [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.365] immediately return since hWnd is NULL [727804.365] MoveWindowMultiWindow to (0, 0) [727804.365] winPositionWindowMultiWindow: (x, y) = (0, 0) [727804.365] immediately return since hWnd is NULL [727804.365] CopyWindowMultiWindow [727804.365] winAdjustXWindow [727804.365] immediately return because the window is iconized [727804.365] winAdjustXWindow [727804.365] immediately return because the window is iconized [727804.365] winAdjustXWindow [727804.365] immediately return because the window is iconized [727804.365] Queue Size 2 2 [727804.365] winMultiWindowWMProc - 727804365 ms MSG: 1034 ID: 0 [727804.381] Queue Size 1 1 [727804.381] winMultiWindowWMProc - 727804381 ms MSG: 1038 ID: 0 [727804.381] winAdjustXWindow [727804.381] immediately return because the window is iconized [727804.381] winAdjustXWindow [727804.381] immediately return because the window is iconized [727804.381] winAdjustXWindow [727804.381] immediately return because the window is iconized [727804.381] Queue Size 0 0 [727804.381] winMultiWindowWMProc - 727804381 ms MSG: 1038 ID: 0 [727804.381] winPositionWindowMultiWindow: (x, y) = (1104, 4) [727804.381] immediately return since hWnd is NULL [727804.381] winMapWindowMultiWindow - pWin: 805338f0 [727804.381] winUpdateWindowsWindow [727804.381] -winUpdateWindowsWindow [727804.381] winAdjustXWindow [727804.381] immediately return because the window is iconized [727804.396] winAdjustXWindow [727804.396] immediately return because the window is iconized [727804.396] winAdjustXWindow [727804.396] immediately return because the window is iconized [727848.279] executing 'xterm -display :0.0 -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh moss@swarm.cs.umass.edu', pid 13748 [727848.311] (pid 13748 stderr) /bin/sh: xterm: command not found [727897.061] winSendMessageToWM () [727897.061] Queue Size 0 0 [727897.061] winMultiWindowWMProc - 727897061 ms MSG: 1032 ID: 7081722 [727897.061] WM_WM_ACTIVATE [727897.061] winAdjustXWindow [727897.061] ConfigureWindow to (8, 30) - 1107x697 [727897.061] ResizeWindowMultiWindow to (8, 30) - 1107x697 [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (1112, 34) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (9, 31) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] winPositionWindowMultiWindow - (727897061 ms)drawable (8, 30)-(1115, 727) [727897.061] winPositionWindowMultiWindow - (727897061 ms)rcNew (0, 0)-(1123, 735) [727897.061] winPositionWindowMultiWindow - (727897061 ms)rcOld (0, 0)-(1123, 735) [727897.061] (727897061 ms)rcClient (0, 0)-(1107, 697) [727897.061] winPositionWindowMultiWindow - Not need to move [727897.061] CopyWindowMultiWindow [727897.061] winTopLevelWindowProc - WM_SIZE to 1107x697 (SIZE_RESTORED) - 727897061 ms [727897.061] winAdjustXWindow [727897.061] return because already adjusted [727897.061] winSendMessageToWM () [727897.061] Queue Size 0 0 [727897.061] winMultiWindowWMProc - 727897061 ms MSG: 1032 ID: 2663208 [727897.061] WM_WM_ACTIVATE [727897.061] ResizeWindowMultiWindow to (0, 0) - 1107x697 [727897.061] winPositionWindowMultiWindow: (x, y) = (1112, 34) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (9, 31) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] ResizeWindowMultiWindow to (0, 0) - 1107x697 [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] ResizeWindowMultiWindow to (8, 30) - 1103x683 [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (1112, 34) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (9, 31) [727897.061] immediately return since hWnd is NULL [727897.061] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.061] winPositionWindowMultiWindow - (727897061 ms)drawable (8, 30)-(1111, 713) [727897.061] winPositionWindowMultiWindow - (727897061 ms)rcNew (0, 0)-(1119, 721) [727897.061] winPositionWindowMultiWindow - (727897061 ms)rcOld (0, 0)-(1123, 735) [727897.061] (727897061 ms)rcClient (0, 0)-(1107, 697) [727897.061] winPositionWindowMultiWindow - Need to move [727897.061] MoveWindow to (0, 0) - 1119x721 [727897.061] winTopLevelWindowProc - WM_SIZE to 1103x683 (SIZE_RESTORED) - 727897061 ms [727897.061] winAdjustXWindow [727897.061] return because already adjusted [727897.077] winSendMessageToWM () [727897.077] Queue Size 0 0 [727897.077] winMultiWindowWMProc - 727897077 ms MSG: 1038 ID: 0 [727897.077] ResizeWindowMultiWindow to (0, 0) - 1103x683 [727897.077] winPositionWindowMultiWindow: (x, y) = (1112, 34) [727897.077] immediately return since hWnd is NULL [727897.077] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.077] immediately return since hWnd is NULL [727897.077] winPositionWindowMultiWindow: (x, y) = (9, 31) [727897.077] immediately return since hWnd is NULL [727897.077] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.077] immediately return since hWnd is NULL [727897.077] ResizeWindowMultiWindow to (0, 0) - 1103x683 [727897.077] winPositionWindowMultiWindow: (x, y) = (8, 30) [727897.077] immediately return since hWnd is NULL [727897.092] winAdjustXWindow [727897.092] immediately return because the window is iconized [727897.092] MoveWindowMultiWindow to (0, 0) [727897.092] winPositionWindowMultiWindow: (x, y) = (0, 0) [727897.092] winPositionWindowMultiWindow - (727897092 ms)drawable (0, 0)-(1103, 683) [727897.092] winPositionWindowMultiWindow - (727897092 ms)rcNew (-8, -30)-(1111, 691) [727897.092] winPositionWindowMultiWindow - (727897092 ms)rcOld (-32000, -32000)-(-31840, -31973) [727897.092] (727897092 ms)rcClient (0, 0)-(0, 0) [727897.092] winPositionWindowMultiWindow - Need to move [727897.092] MoveWindow to (-8, -30) - 1119x721 [727897.092] winAdjustXWindow [727897.092] immediately return because the window is iconized [727897.092] winPositionWindowMultiWindow: (x, y) = (0, 0) [727897.092] immediately return since hWnd is NULL [727897.092] winPositionWindowMultiWindow: (x, y) = (1104, 4) [727897.092] immediately return since hWnd is NULL [727897.092] winPositionWindowMultiWindow: (x, y) = (0, 0) [727897.092] immediately return since hWnd is NULL [727897.092] winPositionWindowMultiWindow: (x, y) = (1, 1) [727897.092] immediately return since hWnd is NULL [727897.092] CopyWindowMultiWindow [727897.092] winTopLevelWindowProc - WM_SIZE to 0x0 (SIZE_MINIMIZED) - 727897092 ms [727897.092] winAdjustXWindow [727897.092] immediately return because the window is iconized [727897.108] winAdjustXWindow [727897.108] immediately return because the window is iconized [727897.108] winAdjustXWindow [727897.108] immediately return because the window is iconized [727897.108] winAdjustXWindow [727897.108] immediately return because the window is iconized [727897.108] ResizeWindowMultiWindow to (1084, 4) - 15x641 [727897.108] winPositionWindowMultiWindow: (x, y) = (1084, 4) [727897.108] immediately return since hWnd is NULL [727897.108] CopyWindowMultiWindow [727898.652] winSendMessageToWM () [727898.652] Queue Size 0 0 [727898.652] winMultiWindowWMProc - 727898652 ms MSG: 1032 ID: 7081722 [727898.652] WM_WM_ACTIVATE [727898.652] winAdjustXWindow [727898.652] ConfigureWindow to (8, 30) - 1103x683 [727898.652] MoveWindowMultiWindow to (8, 30) [727898.652] winPositionWindowMultiWindow: (x, y) = (8, 30) [727898.652] winPositionWindowMultiWindow - (727898652 ms)drawable (8, 30)-(1111, 713) [727898.652] winPositionWindowMultiWindow - (727898652 ms)rcNew (0, 0)-(1119, 721) [727898.652] winPositionWindowMultiWindow - (727898652 ms)rcOld (0, 0)-(1119, 721) [727898.652] (727898652 ms)rcClient (0, 0)-(1103, 683) [727898.652] winPositionWindowMultiWindow - Not need to move [727898.652] winPositionWindowMultiWindow: (x, y) = (8, 30) [727898.652] immediately return since hWnd is NULL [727898.652] winPositionWindowMultiWindow: (x, y) = (1092, 34) [727898.652] immediately return since hWnd is NULL [727898.652] winPositionWindowMultiWindow: (x, y) = (8, 30) [727898.652] immediately return since hWnd is NULL [727898.652] winPositionWindowMultiWindow: (x, y) = (9, 31) [727898.652] immediately return since hWnd is NULL [727898.652] CopyWindowMultiWindow [727898.668] winTopLevelWindowProc - WM_SIZE to 1103x683 (SIZE_RESTORED) - 727898668 ms [727898.668] winAdjustXWindow [727898.668] return because already adjusted [727898.668] winSendMessageToWM () [727898.668] Queue Size 0 0 [727898.668] winMultiWindowWMProc - 727898668 ms MSG: 1032 ID: 2663208 [727898.668] WM_WM_ACTIVATE [727903.317] winPositionWindowMultiWindow: (x, y) = (9, 31) [727903.317] immediately return since hWnd is NULL [727903.317] winPositionWindowMultiWindow: (x, y) = (10, 32) [727903.317] immediately return since hWnd is NULL [727903.317] winPositionWindowMultiWindow: (x, y) = (9, 31) [727903.317] immediately return since hWnd is NULL [727903.317] winPositionWindowMultiWindow: (x, y) = (9, 31) [727903.317] immediately return since hWnd is NULL [727903.332] MoveWindowMultiWindow to (26, 618) [727903.332] winPositionWindowMultiWindow: (x, y) = (34, 648) [727903.332] immediately return since hWnd is NULL [727903.332] winPositionWindowMultiWindow: (x, y) = (35, 649) [727903.332] immediately return since hWnd is NULL [727903.332] winMapWindowMultiWindow - pWin: 80569e50 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a2e8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] MoveWindowMultiWindow to (284, 618) [727903.332] winPositionWindowMultiWindow: (x, y) = (292, 648) [727903.332] immediately return since hWnd is NULL [727903.332] winPositionWindowMultiWindow: (x, y) = (292, 648) [727903.332] immediately return since hWnd is NULL [727903.332] winMapWindowMultiWindow - pWin: 8056a3c8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a848 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] ResizeWindowMultiWindow to (1084, 4) - 15x550 [727903.332] winPositionWindowMultiWindow: (x, y) = (1092, 34) [727903.332] immediately return since hWnd is NULL [727903.332] winUnmapWindowMultiWindow - pWin: 8056a3c8 [727903.332] winUnmapWindowMultiWindow - pWin: 8056a848 [727903.332] winUnmapWindowMultiWindow - pWin: 80569e50 [727903.332] winUnmapWindowMultiWindow - pWin: 8056a2e8 [727903.332] winMapWindowMultiWindow - pWin: 80569e50 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a2e8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a3c8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a848 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winUnmapWindowMultiWindow - pWin: 8056a3c8 [727903.332] winUnmapWindowMultiWindow - pWin: 8056a848 [727903.332] winUnmapWindowMultiWindow - pWin: 80569e50 [727903.332] winUnmapWindowMultiWindow - pWin: 8056a2e8 [727903.332] winMapWindowMultiWindow - pWin: 80569e50 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a2e8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a3c8 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.332] winMapWindowMultiWindow - pWin: 8056a848 [727903.332] winUpdateWindowsWindow [727903.332] -winUpdateWindowsWindow [727903.348] winUnmapWindowMultiWindow - pWin: 8056a3c8 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a848 [727903.348] winUnmapWindowMultiWindow - pWin: 80569e50 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a2e8 [727903.348] winMapWindowMultiWindow - pWin: 80569e50 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a2e8 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a3c8 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a848 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winUnmapWindowMultiWindow - pWin: 8056a3c8 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a848 [727903.348] winUnmapWindowMultiWindow - pWin: 80569e50 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a2e8 [727903.348] winMapWindowMultiWindow - pWin: 80569e50 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a2e8 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a3c8 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winMapWindowMultiWindow - pWin: 8056a848 [727903.348] winUpdateWindowsWindow [727903.348] -winUpdateWindowsWindow [727903.348] winUnmapWindowMultiWindow - pWin: 8056a3c8 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a848 [727903.348] winUnmapWindowMultiWindow - pWin: 80569e50 [727903.348] winUnmapWindowMultiWindow - pWin: 8056a2e8 [727903.363] ResizeWindowMultiWindow to (1084, 4) - 15x641 [727903.363] winPositionWindowMultiWindow: (x, y) = (1092, 34) [727903.363] immediately return since hWnd is NULL [727916.312] winUnmapWindowMultiWindow - pWin: 805338f0 [727916.327] ResizeWindowMultiWindow to (1084, 4) - 15x311 [727916.327] winPositionWindowMultiWindow: (x, y) = (1092, 34) [727916.327] immediately return since hWnd is NULL [727916.327] winMapWindowMultiWindow - pWin: 805338f0 [727916.327] winUpdateWindowsWindow [727916.327] -winUpdateWindowsWindow [727916.327] winPositionWindowMultiWindow: (x, y) = (1092, 364) [727916.327] immediately return since hWnd is NULL [727916.327] winMapWindowMultiWindow - pWin: 804d2630 [727916.327] winUpdateWindowsWindow [727916.327] -winUpdateWindowsWindow [727918.698] winUnmapWindowMultiWindow - pWin: 805338f0 [727918.698] winUnmapWindowMultiWindow - pWin: 804d2630 [727918.714] ResizeWindowMultiWindow to (1084, 4) - 15x641 [727918.714] winPositionWindowMultiWindow: (x, y) = (1092, 34) [727918.714] immediately return since hWnd is NULL [727918.714] winMapWindowMultiWindow - pWin: 804d2630 [727918.714] winUpdateWindowsWindow [727918.714] -winUpdateWindowsWindow [727964.407] LoadPreferences: Loading /home/Eliot/.XWinrc [727964.407] winSendMessageToWM () [727964.407] Queue Size 0 0 [727964.407] winSendMessageToWM () [727964.407] winMultiWindowWMProc - 727964407 ms MSG: 1034 ID: 1983157178 [727964.407] winSendMessageToWM () [727964.407] winSendMessageToWM () [727964.422] Queue Size 2 2 [727964.422] winMultiWindowWMProc - 727964422 ms MSG: 1034 ID: 1983157178 [727964.422] Queue Size 1 1 [727964.422] winMultiWindowWMProc - 727964422 ms MSG: 1034 ID: 1983157178 [727964.438] Queue Size 0 0 [727964.438] winMultiWindowWMProc - 727964438 ms MSG: 1034 ID: 1983157178 [727967.683] executing '/usr/bin/xterm -display :0.0 -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh moss@swarm.cs.umass.edu', pid 14428 [727967.745] client(1200000): Reserved pid(-1). [727967.745] client(1200000): Reserved cmdname(NULL) and cmdargs(NULL). [727967.745] AllocNewConnection: client index = 9, socket fd = 21 [727967.776] winPositionWindowMultiWindow: (x, y) = (1, 1) [727967.776] immediately return since hWnd is NULL [727967.776] MoveWindowMultiWindow to (0, 0) [727967.776] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.776] immediately return since hWnd is NULL [727967.776] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.776] immediately return since hWnd is NULL [727967.776] ResizeWindowMultiWindow to (0, 0) - 16x21 [727967.776] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.776] immediately return since hWnd is NULL [727967.776] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.776] immediately return since hWnd is NULL [727967.776] winSendMessageToWM () [727967.776] winSendMessageToWM () [727967.776] Queue Size 1 1 [727967.776] winMultiWindowWMProc - 727967776 ms MSG: 1038 ID: 0 [727967.776] ResizeWindowMultiWindow to (0, 0) - 16x21 [727967.776] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.776] immediately return since hWnd is NULL [727967.776] winSendMessageToWM () [727967.792] ResizeWindowMultiWindow to (0, 0) - 1221x711 [727967.792] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.792] immediately return since hWnd is NULL [727967.792] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.792] immediately return since hWnd is NULL [727967.792] winSendMessageToWM () [727967.792] ResizeWindowMultiWindow to (0, 0) - 1221x711 [727967.792] winPositionWindowMultiWindow: (x, y) = (0, 0) [727967.792] immediately return since hWnd is NULL [727967.792] winSendMessageToWM () [727967.792] Queue Size 3 3 [727967.792] winMultiWindowWMProc - 727967792 ms MSG: 1038 ID: 0 [727967.792] Queue Size 2 2 [727967.792] winMultiWindowWMProc - 727967792 ms MSG: 1038 ID: 0 [727967.792] Queue Size 1 1 [727967.792] winMultiWindowWMProc - 727967792 ms MSG: 1038 ID: 0 [727967.792] Queue Size 0 0 [727967.792] winMultiWindowWMProc - 727967792 ms MSG: 1038 ID: 0 [727967.917] winPositionWindowMultiWindow: (x, y) = (1, 1) [727967.917] immediately return since hWnd is NULL [727967.917] winPositionWindowMultiWindow: (x, y) = (1, 1) [727967.917] immediately return since hWnd is NULL [727967.917] winSendMessageToWM () [727967.917] winSendMessageToWM () [727967.917] Queue Size 0 0 [727967.917] winMultiWindowWMProc - 727967917 ms MSG: 1038 ID: 0 [727967.917] winPositionWindowMultiWindow: (x, y) = (1, 1) [727967.917] immediately return since hWnd is NULL [727967.917] winPositionWindowMultiWindow: (x, y) = (254, 6) [727967.917] immediately return since hWnd is NULL [727967.917] winPositionWindowMultiWindow: (x, y) = (140, 6) [727967.917] immediately return since hWnd is NULL [727967.917] winPositionWindowMultiWindow: (x, y) = (6, 6) [727967.917] immediately return since hWnd is NULL [727967.932] Queue Size 0 0 [727967.932] winMultiWindowWMProc - 727967932 ms MSG: 1038 ID: 0 [727967.979] winMapWindowMultiWindow - pWin: 80571798 [727967.979] winUpdateWindowsWindow [727967.979] winGetWindowID - Window ID: 18874393 [727967.979] winGetWindowID - Window ID: 18874393 [727967.979] winAdjustXWindow [727967.979] return because already adjusted [727967.979] winGetWindowID - Window ID: 18874393 [727967.979] winSendMessageToWM () [727967.979] Queue Size 0 0 [727967.979] winMultiWindowWMProc - 727967979 ms MSG: 1032 ID: 0 [727967.979] WM_WM_ACTIVATE [727967.979] winSendMessageToWM () [727967.979] Queue Size 0 0 [727967.979] winMultiWindowWMProc - 727967979 ms MSG: 1037 ID: 2664500 [727967.979] WM_WM_MAP3 [727967.995] winTopLevelWindowProc - WM_SIZE to 1221x711 (SIZE_RESTORED) - 727967995 ms [727967.995] winAdjustXWindow [727967.995] return because already adjusted [727967.995] winAdjustXWindow [727967.995] return because already adjusted [727967.995] -winUpdateWindowsWindow [727967.995] winMapWindowMultiWindow - pWin: 80571ff0 [727967.995] winUpdateWindowsWindow [727967.995] -winUpdateWindowsWindow [727967.995] winMapWindowMultiWindow - pWin: 80577400 [727967.995] winUpdateWindowsWindow [727967.995] -winUpdateWindowsWindow [727967.995] winMapWindowMultiWindow - pWin: 80577538 [727967.995] winUpdateWindowsWindow [727967.995] -winUpdateWindowsWindow [727967.995] winSendMessageToWM () [727967.995] GetWindowName [727968.010] winSendMessageToWM () [727968.026] winAdjustXWindow [727968.026] ConfigureWindow to (8, 30) - 1221x711 [727968.026] MoveWindowMultiWindow to (8, 30) [727968.026] winPositionWindowMultiWindow: (x, y) = (8, 30) [727968.026] winPositionWindowMultiWindow - (727968026 ms)drawable (8, 30)-(1229, 741) [727968.026] winPositionWindowMultiWindow - (727968026 ms)rcNew (0, 0)-(1237, 749) [727968.026] winPositionWindowMultiWindow - (727968026 ms)rcOld (0, 0)-(1237, 749) [727968.026] (727968026 ms)rcClient (0, 0)-(1221, 711) [727968.026] winPositionWindowMultiWindow - Not need to move [727968.026] winPositionWindowMultiWindow: (x, y) = (8, 30) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (9, 31) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (14, 36) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (148, 36) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (262, 36) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (9, 31) [727968.026] immediately return since hWnd is NULL [727968.026] winPositionWindowMultiWindow: (x, y) = (9, 31) [727968.026] immediately return since hWnd is NULL [727968.026] CopyWindowMultiWindow [727968.088] Queue Size 1 1 [727968.088] winMultiWindowWMProc - 727968088 ms MSG: 1038 ID: 0 [727968.104] Queue Size 0 0 [727968.104] winMultiWindowWMProc - 727968104 ms MSG: 1038 ID: 0 [727974.781] winUnmapWindowMultiWindow - pWin: 80571798 [727974.781] winSendMessageToWM () [727974.781] Queue Size 0 0 [727974.781] winMultiWindowWMProc - 727974781 ms MSG: 1032 ID: 160 [727974.781] WM_WM_ACTIVATE [727974.781] winUnmapWindowMultiWindow - pWin: 80571ff0 [727974.781] winUnmapWindowMultiWindow - pWin: 80577400 [727974.781] winUnmapWindowMultiWindow - pWin: 80577538 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80573d08 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80575cf8 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80575850 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80575788 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80577538 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80577400 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80571ff0 [727974.796] winDestroyWindowMultiWindow - pWin: 0x80571798 [727974.796] client(1200000): Released pid(-1). [727974.796] client(1200000): Released cmdline(NULL) and cmdargs(NULL). -------------- next part -------------- -- 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 moss@cs.umass.edu Mon Apr 23 16:46:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Mon, 23 Apr 2012 16:46:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F95864B.1090802@cs.umass.edu> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F95864B.1090802@cs.umass.edu> Message-ID: <4F95873A.4030006@cs.umass.edu> On 4/23/2012 12:41 PM, Eliot Moss wrote: > Ok -- by perusing the log I figured it out ... > > In the past, .XWinrc names of files such as "xterm" > worked just fine. Apparently something changed about > the PATH used, and "xterm" was not being found. When > I write /usr/bin/xterm, it starts up. You can see the > first case and the second in the attached log file. > > So, I think xlaunch is ok, but this was a surprising > difference :-) ... > > Regards -- Eliot Moss PS -- I can confirm that adding /usr/bin solves the problem with the current released XWin.exe as well as with the 20120423 snapshot you asked me to test. E -- 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 marc.girod@gmail.com Tue Apr 24 06:58:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Tue, 24 Apr 2012 06:58:00 -0000 Subject: startx with different displays In-Reply-To: <4F956D3E.5000408@cygwin.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> Message-ID: <33737835.post@talk.nabble.com> Larry Hall (Cygwin-X) wrote: > > Get rid of the real dups. You only need the one in /usr/bin. > I don't know how they got there. They are not in my normal path. Somehow my procedure to run cygcheck must have injected them. I add them in neither .bash_profile nor .bashrc. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33737835.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 Apr 24 11:40:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 24 Apr 2012 11:40:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F95864B.1090802@cs.umass.edu> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F95864B.1090802@cs.umass.edu> Message-ID: <4F96911C.30608@dronecode.org.uk> On 23/04/2012 17:41, Eliot Moss wrote: > Ok -- by perusing the log I figured it out ... > [727848.279] executing 'xterm -display :0.0 -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh moss@swarm.cs.umass.edu', pid 13748 > [727848.311] (pid 13748 stderr) /bin/sh: xterm: command not found > In the past, .XWinrc names of files such as "xterm" > worked just fine. Apparently something changed about > the PATH used, and "xterm" was not being found. When > I write /usr/bin/xterm, it starts up. You can see the > first case and the second in the attached log file. > > So, I think xlaunch is ok, but this was a surprising > difference :-) ... This is not intentional. I can't reproduce this, so I'm not quite sure what is causing this. What I am expecting to happen is that xlaunch is invoked via the start menu shortcut which it's package creates, which runs bash -l -c xlaunch, which reads /etc/profile, which sets PATH to include /usr/bin, which should be inherited by XWin and used when it execs /bin/sh -c 'your xterm command'. We try to create the login environment as far up the process hierarchy as possible, rather than starting the processes from the notification area menu with bash -l -c, as creating the login environment can be expensive. -- 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 Apr 24 11:54:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 24 Apr 2012 11:54:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F956F70.4080900@cornell.edu> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F956F70.4080900@cornell.edu> Message-ID: <4F96946A.4070406@dronecode.org.uk> On 23/04/2012 16:04, Ken Brown wrote: >> I've added some code to capture stdout and stderr from these subprocesses to >> the X server log, and to more clearly diagnose problems which could occur >> while fork/exec-ing them. > > Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc? I'm hoping it might help with the problem I reported in > > http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html Hmm.. not sure code is really needed. You can see the output from startxwin by running it from a terminal, or capture it by changing the shortcut which runs it to something like the following (perhaps we should do that by default) C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >>/var/log/xwin/startxwin.log 2>&1' -- 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 moss@cs.umass.edu Tue Apr 24 12:23:00 2012 From: moss@cs.umass.edu (Eliot Moss) Date: Tue, 24 Apr 2012 12:23:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F96911C.30608@dronecode.org.uk> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F95864B.1090802@cs.umass.edu> <4F96911C.30608@dronecode.org.uk> Message-ID: <4F969B17.7080407@cs.umass.edu> Ok, I can see that perhaps in some ways I was being foolish and could have figured out more of this myself. But here's something interesting. I tried this: - "Pin to Start Menu" of the supplied XLaunch short cut - Edit to change the command to: "/usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch" (since I want to start things, not build/edit a config file) The full line in the shortcut is: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/xlaunch.exe -run /home/Eliot/config.xlaunch" This works, without putting in the explicit /usr/bin/ everywhere in the .XWinrc file. BUT: I get the "extra" icon I don't want, this time for XLaunch rather than for StartXWin. So the "extra" icon seems to have to do with the bash that run.exe is starting and the fact that the bash is still there as parent to the still-running XLaunch (or StartXWin). Perhaps it is because the bash does not start the program under it in the same way that run.exe does? Regards -- EM -- 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 Tue Apr 24 13:27:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Tue, 24 Apr 2012 13:27:00 -0000 Subject: Issue with XWin under xlaunch In-Reply-To: <4F96946A.4070406@dronecode.org.uk> References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F956F70.4080900@cornell.edu> <4F96946A.4070406@dronecode.org.uk> Message-ID: <4F96A9FF.7090005@cornell.edu> On 4/24/2012 7:54 AM, Jon TURNEY wrote: > On 23/04/2012 16:04, Ken Brown wrote: >>> I've added some code to capture stdout and stderr from these subprocesses to >>> the X server log, and to more clearly diagnose problems which could occur >>> while fork/exec-ing them. >> >> Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc? I'm hoping it might help with the problem I reported in >> >> http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html > > Hmm.. not sure code is really needed. You can see the output from startxwin > by running it from a terminal, or capture it by changing the shortcut which > runs it to something like the following (perhaps we should do that by default) > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >>> /var/log/xwin/startxwin.log 2>&1' That doesn't help, but I'll reply to my original thread to explain why. I shouldn't have interjected my question into this thread. 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 kbrown@cornell.edu Tue Apr 24 13:51:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Tue, 24 Apr 2012 13:51:00 -0000 Subject: dbus-launch --exit-with-session fails when run from .startxwinrc In-Reply-To: <4F8C2388.7090900@cornell.edu> References: <4F8C224B.3090103@cornell.edu> <4F8C2388.7090900@cornell.edu> Message-ID: <4F96AFA3.8060704@cornell.edu> On 4/16/2012 9:50 AM, Ken Brown wrote: > On 4/16/2012 9:44 AM, Ken Brown wrote: >> The following problem occurs on my 64-bit Windows 7 system but not on my >> XP system. >> >> I start the X server using the Start Menu shortcut [modified to add >> -emulate3buttons] and a .startxwinrc with the following contents: >> >> eval `dbus-launch --sh-syntax --exit-with-session` >> xterm >> >> Running ps in the resulting xterm window shows no dbus-launch or >> dbus-daemon process. But I can give the same dbus-launch command in the >> xterm window, and the processes start as expected. I'm attaching >> cygcheck output and the XWin log. >> >> My hope in reporting this is that the problem I'm seeing (and the >> difference between XP and Win7) is somehow related to the emacs problem >> I've been trying to solve: >> >> http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html >> >> Ken >> >> P.S. You'll see in the cygcheck output that I'm running a Cygwin >> snapshot; but nothing changes if I revert to cygwin-1.7.13-1. > > I forgot to say that if I remove "--exit-with-session" from the command > line in my .startxwinrc, then a dbus-daemon process does start. I tried modifying the X server shortcut to read C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >> /var/log/xwin/startxwin.log 2>&1' as suggested in a different thread, but that provides no information. The resulting startxwin.log is virtually identical (with minor differences) to XWin.0.log. In particular, there's no indication of what's happening when .startxwinrc is processed. For starters, it would really be helpful if someone could try to reproduce my problem on a 64-bit Windows 7 system. At the moment, I don't even know if there is a bug somewhere or simply a problem with my own system. Here's the recipe: 1. Create a .startxwinrc file with the following contents: eval `dbus-launch --sh-syntax --exit-with-session` xterm 2. Start the X server using the Start Menu shortcut. 3. In the resulting xterm window, give the "ps" command. If things are working right, the output from ps should show a dbus-launch process and a dbus-daemon process. These processes do appear on my XP system but not on my Windows 7 system. 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 reply-to-list-only-lh@cygwin.com Tue Apr 24 17:33:00 2012 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Tue, 24 Apr 2012 17:33:00 -0000 Subject: startx with different displays In-Reply-To: <33737835.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> Message-ID: <4F96E3BC.4050800@cygwin.com> On 4/24/2012 2:58 AM, Marc Girod wrote: > > > Larry Hall (Cygwin-X) wrote: >> >> Get rid of the real dups. You only need the one in /usr/bin. >> > I don't know how they got there. They are not in my normal path. > Somehow my procedure to run cygcheck must have injected them. > I add them in neither .bash_profile nor .bashrc. Don't worry about the duplicated paths. I'm saying get rid of the actual duplicated DLLs. -- 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 marc.girod@gmail.com Tue Apr 24 21:13:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Tue, 24 Apr 2012 21:13:00 -0000 Subject: startx with different displays In-Reply-To: <4F96E3BC.4050800@cygwin.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> <4F96E3BC.4050800@cygwin.com> Message-ID: <33741843.post@talk.nabble.com> Larry Hall (Cygwin-X) wrote: > > Don't worry about the duplicated paths. I'm saying get rid of the > actual duplicated DLLs. > Sorry, but I have none. My understanding is that the report was only the result of the duplicated paths. Running cygcheck again doesn't find duplicated DLLs. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33741843.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 24 21:47:00 2012 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Tue, 24 Apr 2012 21:47:00 -0000 Subject: startx with different displays In-Reply-To: <33741843.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> <4F96E3BC.4050800@cygwin.com> <33741843.post@talk.nabble.com> Message-ID: <4F971F46.5090308@cygwin.com> On 4/24/2012 5:12 PM, Marc Girod wrote: > Larry Hall (Cygwin-X) wrote: >> >> Don't worry about the duplicated paths. I'm saying get rid of the >> actual duplicated DLLs. >> > > Sorry, but I have none. > My understanding is that the report was only the result of the duplicated > paths. > Running cygcheck again doesn't find duplicated DLLs. OK, good. -- 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 marc.girod@gmail.com Wed Apr 25 11:50:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Wed, 25 Apr 2012 11:50:00 -0000 Subject: startx with different displays In-Reply-To: <4F971F46.5090308@cygwin.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> <4F96E3BC.4050800@cygwin.com> <33741843.post@talk.nabble.com> <4F971F46.5090308@cygwin.com> Message-ID: <33745960.post@talk.nabble.com> Back to my original problem... I tried startxwin (as suggested by a colleague) and this one accepts to start XWin on DISPLAY :0 Are all my problems related to startx? I can see that defaulting to the highest display found in /tmp/.X* seems to comes from it... Does anybody use startx with success? Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33745960.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 25 16:22:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 25 Apr 2012 16:22:00 -0000 Subject: dbus-launch --exit-with-session fails when run from .startxwinrc In-Reply-To: <4F96AFA3.8060704@cornell.edu> References: <4F8C224B.3090103@cornell.edu> <4F8C2388.7090900@cornell.edu> <4F96AFA3.8060704@cornell.edu> Message-ID: <4F98249E.8010103@dronecode.org.uk> On 24/04/2012 14:50, Ken Brown wrote: > On 4/16/2012 9:50 AM, Ken Brown wrote: >> On 4/16/2012 9:44 AM, Ken Brown wrote: >>> The following problem occurs on my 64-bit Windows 7 system but not on my >>> XP system. >>> >>> I start the X server using the Start Menu shortcut [modified to add >>> -emulate3buttons] and a .startxwinrc with the following contents: >>> >>> eval `dbus-launch --sh-syntax --exit-with-session` >>> xterm >>> >>> Running ps in the resulting xterm window shows no dbus-launch or >>> dbus-daemon process. But I can give the same dbus-launch command in the >>> xterm window, and the processes start as expected. I'm attaching >>> cygcheck output and the XWin log. >>> >>> My hope in reporting this is that the problem I'm seeing (and the >>> difference between XP and Win7) is somehow related to the emacs problem >>> I've been trying to solve: >>> >>> http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html >>> >>> Ken >>> >>> P.S. You'll see in the cygcheck output that I'm running a Cygwin >>> snapshot; but nothing changes if I revert to cygwin-1.7.13-1. >> >> I forgot to say that if I remove "--exit-with-session" from the command >> line in my .startxwinrc, then a dbus-daemon process does start. > > I tried modifying the X server shortcut to read > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >>> /var/log/xwin/startxwin.log 2>&1' > > as suggested in a different thread, but that provides no information. The > resulting startxwin.log is virtually identical (with minor differences) to > XWin.0.log. > > In particular, there's no indication of what's happening when .startxwinrc is > processed. There's no output because ~/.startxwinrc generates no output. > For starters, it would really be helpful if someone could try to reproduce my > problem on a 64-bit Windows 7 system. At the moment, I don't even know if > there is a bug somewhere or simply a problem with my own system. Here's the > recipe: > > 1. Create a .startxwinrc file with the following contents: > > eval `dbus-launch --sh-syntax --exit-with-session` > xterm > > 2. Start the X server using the Start Menu shortcut. > > 3. In the resulting xterm window, give the "ps" command. If things are > working right, the output from ps should show a dbus-launch process and a > dbus-daemon process. > > These processes do appear on my XP system but not on my Windows 7 system. FWIW, it works on XP for me as well. I tried with the following ~/.startxwinrc: eval `dbus-launch --sh-syntax --exit-with-session | tee /dev/stderr` xterm ... which at least lets you see the pid of the dbus-daemon that is started. I'm not sure if --exit-with-session is correct with startxwin, since the startxwin process will not linger after it has started ~/.startxwinrc, and I don't know if stdin will remain open after it (and the process tree above it waiting for it) exits. I have this vague recollection that 'run' has to do different things on XP and W7, which might account for the different behaviour? -- 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 kbrown@cornell.edu Wed Apr 25 17:18:00 2012 From: kbrown@cornell.edu (Ken Brown) Date: Wed, 25 Apr 2012 17:18:00 -0000 Subject: dbus-launch --exit-with-session fails when run from .startxwinrc In-Reply-To: <4F98249E.8010103@dronecode.org.uk> References: <4F8C224B.3090103@cornell.edu> <4F8C2388.7090900@cornell.edu> <4F96AFA3.8060704@cornell.edu> <4F98249E.8010103@dronecode.org.uk> Message-ID: <4F9831C4.5060706@cornell.edu> On 4/25/2012 12:21 PM, Jon TURNEY wrote: > On 24/04/2012 14:50, Ken Brown wrote: >> On 4/16/2012 9:50 AM, Ken Brown wrote: >>> On 4/16/2012 9:44 AM, Ken Brown wrote: >>>> The following problem occurs on my 64-bit Windows 7 system but not on my >>>> XP system. >>>> >>>> I start the X server using the Start Menu shortcut [modified to add >>>> -emulate3buttons] and a .startxwinrc with the following contents: >>>> >>>> eval `dbus-launch --sh-syntax --exit-with-session` >>>> xterm >>>> >>>> Running ps in the resulting xterm window shows no dbus-launch or >>>> dbus-daemon process. But I can give the same dbus-launch command in the >>>> xterm window, and the processes start as expected. I'm attaching >>>> cygcheck output and the XWin log. >>>> >>>> My hope in reporting this is that the problem I'm seeing (and the >>>> difference between XP and Win7) is somehow related to the emacs problem >>>> I've been trying to solve: >>>> >>>> http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html >>>> >>>> Ken >>>> >>>> P.S. You'll see in the cygcheck output that I'm running a Cygwin >>>> snapshot; but nothing changes if I revert to cygwin-1.7.13-1. >>> >>> I forgot to say that if I remove "--exit-with-session" from the command >>> line in my .startxwinrc, then a dbus-daemon process does start. >> >> I tried modifying the X server shortcut to read >> >> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >>>> /var/log/xwin/startxwin.log 2>&1' >> >> as suggested in a different thread, but that provides no information. The >> resulting startxwin.log is virtually identical (with minor differences) to >> XWin.0.log. >> >> In particular, there's no indication of what's happening when .startxwinrc is >> processed. > > There's no output because ~/.startxwinrc generates no output. > >> For starters, it would really be helpful if someone could try to reproduce my >> problem on a 64-bit Windows 7 system. At the moment, I don't even know if >> there is a bug somewhere or simply a problem with my own system. Here's the >> recipe: >> >> 1. Create a .startxwinrc file with the following contents: >> >> eval `dbus-launch --sh-syntax --exit-with-session` >> xterm >> >> 2. Start the X server using the Start Menu shortcut. >> >> 3. In the resulting xterm window, give the "ps" command. If things are >> working right, the output from ps should show a dbus-launch process and a >> dbus-daemon process. >> >> These processes do appear on my XP system but not on my Windows 7 system. > > FWIW, it works on XP for me as well. > > I tried with the following ~/.startxwinrc: > > eval `dbus-launch --sh-syntax --exit-with-session | tee /dev/stderr` > xterm > > ... which at least lets you see the pid of the dbus-daemon that is started. > > I'm not sure if --exit-with-session is correct with startxwin, since the > startxwin process will not linger after it has started ~/.startxwinrc, and I > don't know if stdin will remain open after it (and the process tree above it > waiting for it) exits. I have this vague recollection that 'run' has to do > different things on XP and W7, which might account for the different behaviour? Ah, that must be it. On XP, presumably because of the way 'run' behaves, the sh process that runs .startxwinrc hangs around, so the dbus processes keep running. If I run startxwin from a terminal instead of via the shortcut (i.e., without using 'run'), I get the same behavior on XP as on W7. Thanks. 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 Carlo.DiCocco@dfs.ny.gov Wed Apr 25 18:22:00 2012 From: Carlo.DiCocco@dfs.ny.gov (Carlo.DiCocco@dfs.ny.gov) Date: Wed, 25 Apr 2012 18:22:00 -0000 Subject: Fatal Error (Segmentation Fault) only while viewing the LVM GUI Message-ID: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI displays fine. The LVM "system-config-lvm" GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. Please see below: airs0cld@2UA0070JZB ~ $ ssh -Y root@aorahdev root@aorahdev's password: Warning: No xauth data; using fake authentication data for X11 forwarding. Last login: Wed Apr 25 14:04:58 2012 from 2ua0070jzb.nysdoi.int The following command displays the GUI without any issue: [root@aorahdev ~]# xclock The following command displays the GUI without any issue: [root@aorahdev ~]# . oraenv ORACLE_SID = [root] ? oradshr [root@aorahdev ~]# dbca Warning: Cannot convert string "-b&h-lucida-medium-r-normal-sans-*-140-*-*-p-*-iso8859-1" to type FontStruct The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm The contents of the "XWin.0.log" file are as follows: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.12.0.0 OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32) Package: version 1.12.0-4 built 2012-04-17 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeScreenDefaults - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/2UA0070JZB:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [ 64084.203] (II) xorg.conf is not supported (II) xorg.conf is not supported [ 64084.203] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 64084.203] LoadPreferences: /home/airs0cld/.XWinrc not found LoadPreferences: /home/airs0cld/.XWinrc not found [ 64084.203] LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Loading /etc/X11/system.XWinrc [ 64084.203] LoadPreferences: Done parsing the configuration file... LoadPreferences: Done parsing the configuration file... [ 64084.203] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [ 64084.203] winDetectSupportedEngines - Windows NT, allowing PrimaryDD winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 64084.203] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 64084.203] winDetectSupportedEngines - Returning, supported engines 0000001f winDetectSupportedEngines - Returning, supported engines 0000001f [ 64084.203] winTaskbarInit - Could not get SHGetPropertyStoreForWindow address winTaskbarInit - Could not get SHGetPropertyStoreForWindow address [ 64084.203] winSetEngine - Multi Window or Rootless => ShadowGDI winSetEngine - Multi Window or Rootless => ShadowGDI [ 64084.203] winScreenInit - Using Windows display depth of 32 bits per pixel winScreenInit - Using Windows display depth of 32 bits per pixel [ 64084.218] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [ 64084.218] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 64084.218] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 64084.218] winInitMultiWindowWM - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () [ 64084.218] winMultiWindowXMsgProc - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 64084.218] MIT-SHM extension disabled due to lack of kernel support MIT-SHM extension disabled due to lack of kernel support [ 64084.218] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 64084.250] GL_VERSION: 1.5.0 - Build 7.14.10.4964 GL_VERSION: 1.5.0 - Build 7.14.10.4964 [ 64084.250] GL_VENDOR: Intel GL_VENDOR: Intel [ 64084.250] GL_RENDERER: Intel Eaglelake GL_RENDERER: Intel Eaglelake [ 64084.250] GL_EXTENSIONS: GL_ARB_depth_textureGL_EXTENSIONS: GL_ARB_depth_texture GL_ARB_fragment_programGL_ARB_fragment_program GL_ARB_multitextureGL_ARB_multitexture GL_ARB_occlusion_queryGL_ARB_occlusion_query [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_ARB_point_parametersGL_ARB_point_parameters GL_ARB_shadowGL_ARB_shadow GL_ARB_texture_border_clampGL_ARB_texture_border_clamp GL_ARB_texture_compressionGL_ARB_texture_compression [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_ARB_texture_cube_mapGL_ARB_texture_cube_map GL_ARB_texture_env_addGL_ARB_texture_env_add GL_ARB_texture_env_combineGL_ARB_texture_env_combine GL_ARB_texture_env_dot3GL_ARB_texture_env_dot3 [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_ARB_texture_env_crossbarGL_ARB_texture_env_crossbar GL_ARB_transpose_matrixGL_ARB_transpose_matrix GL_ARB_vertex_buffer_objectGL_ARB_vertex_buffer_object GL_ARB_vertex_programGL_ARB_vertex_program [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_ARB_window_posGL_ARB_window_pos GL_EXT_abgrGL_EXT_abgr GL_EXT_bgraGL_EXT_bgra GL_EXT_blend_colorGL_EXT_blend_color GL_EXT_blend_func_separateGL_EXT_blend_func_separate [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_blend_minmaxGL_EXT_blend_minmax GL_EXT_blend_subtractGL_EXT_blend_subtract GL_EXT_clip_volume_hintGL_EXT_clip_volume_hint GL_EXT_compiled_vertex_arrayGL_EXT_compiled_vertex_array [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_draw_range_elementsGL_EXT_draw_range_elements GL_EXT_fog_coordGL_EXT_fog_coord GL_EXT_multi_draw_arraysGL_EXT_multi_draw_arrays GL_EXT_packed_pixelsGL_EXT_packed_pixels [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_rescale_normalGL_EXT_rescale_normal GL_EXT_secondary_colorGL_EXT_secondary_color GL_EXT_separate_specular_colorGL_EXT_separate_specular_color GL_EXT_shadow_funcsGL_EXT_shadow_funcs [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_stencil_two_sideGL_EXT_stencil_two_side GL_ARB_texture_rectangleGL_ARB_texture_rectangle GL_EXT_texture_rectangleGL_EXT_texture_rectangle GL_EXT_stencil_wrapGL_EXT_stencil_wrap [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_texture_compression_s3tcGL_EXT_texture_compression_s3tc GL_EXT_texture_env_addGL_EXT_texture_env_add GL_EXT_texture_env_combineGL_EXT_texture_env_combine [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_EXT_texture_lod_biasGL_EXT_texture_lod_bias GL_EXT_texture_filter_anisotropicGL_EXT_texture_filter_anisotropic GL_EXT_texture3DGL_EXT_texture3D [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_3DFX_texture_compression_FXT1GL_3DFX_texture_compression_FXT1 GL_IBM_texture_mirrored_repeatGL_IBM_texture_mirrored_repeat GL_NV_blend_squareGL_NV_blend_square [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_NV_texgen_reflectionGL_NV_texgen_reflection GL_SGIS_generate_mipmapGL_SGIS_generate_mipmap GL_SGIS_texture_edge_clampGL_SGIS_texture_edge_clamp GL_SGIS_texture_lodGL_SGIS_texture_lod [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_WIN_swap_hintGL_WIN_swap_hint [ 64084.250] WGL_EXTENSIONS: WGL_ARB_buffer_regionWGL_EXTENSIONS: WGL_ARB_buffer_region WGL_ARB_extensions_stringWGL_ARB_extensions_string WGL_ARB_make_current_readWGL_ARB_make_current_read WGL_ARB_pixel_formatWGL_ARB_pixel_format [ 64084.250] WGL_EXTENSIONS: WGL_EXTENSIONS: WGL_ARB_pbufferWGL_ARB_pbuffer WGL_EXT_extensions_stringWGL_EXT_extensions_string WGL_EXT_swap_controlWGL_EXT_swap_control [ 64084.250] (II) AIGLX: enabled GLX_SGI_make_current_read (II) AIGLX: enabled GLX_SGI_make_current_read [ 64084.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 64084.250] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 64084.250] (II) AIGLX: enabled GLX_SGIX_pbuffer (II) AIGLX: enabled GLX_SGIX_pbuffer [ 64084.250] (II) AIGLX: Set GLX version to 1.3 (II) AIGLX: Set GLX version to 1.3 [ 64084.250] 30 fbConfigs 30 fbConfigs [ 64084.250] pxf vis fb render Ste aux accum MS drawable Group/ pxf vis fb render Ste aux accum MS drawable Group/ [ 64084.250] idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat [ 64084.250] ----------------------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------- [ 64084.250] 1 60 42 TrueColor 32 0 y . . . 8 8 8 8 0 0 0 0 0 0 0 0 0 y . y . . 2 1 60 42 TrueColor 32 0 y . . . 8 8 8 8 0 0 0 0 0 0 0 0 0 y . y . . 2 [ 64084.250] 2 61 43 TrueColor 32 0 y . y . 8 8 8 8 0 0 0 16 16 16 16 0 0 y . . . . 2 2 61 43 TrueColor 32 0 y . y . 8 8 8 8 0 0 0 16 16 16 16 0 0 y . . . . 2 [ 64084.250] 3 62 44 TrueColor 32 0 y . . . 8 8 8 8 16 0 0 0 0 0 0 0 0 y . y . . 2 3 62 44 TrueColor 32 0 y . . . 8 8 8 8 16 0 0 0 0 0 0 0 0 y . y . . 2 [ 64084.250] 4 41 45 TrueColor 32 0 y . y . 8 8 8 8 16 0 0 16 16 16 16 0 0 y . . . . 2 4 41 45 TrueColor 32 0 y . y . 8 8 8 8 16 0 0 16 16 16 16 0 0 y . . . . 2 [ 64084.250] 5 63 46 TrueColor 32 0 y . . . 8 8 8 8 24 8 0 0 0 0 0 0 0 y . y . . 2 5 63 46 TrueColor 32 0 y . . . 8 8 8 8 24 8 0 0 0 0 0 0 0 y . y . . 2 [ 64084.250] 6 21 47 TrueColor 32 0 y . y . 8 8 8 8 24 8 0 16 16 16 16 0 0 y . . . . 2 6 21 47 TrueColor 32 0 y . y . 8 8 8 8 24 8 0 16 16 16 16 0 0 y . . . . 2 [ 64084.250] 7 64 48 TrueColor 32 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 y y . . . 0 * 7 64 48 TrueColor 32 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 y y . . . 0 * [ 64084.250] 8 65 49 TrueColor 32 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 y y . . . 0 * 8 65 49 TrueColor 32 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 y y . . . 0 * [ 64084.250] 9 66 4a TrueColor 32 0 y . y copy . 8 8 8 0 32 8 0 16 16 16 0 0 0 y . . . . 0 * 9 66 4a TrueColor 32 0 y . y copy . 8 8 8 0 32 8 0 16 16 16 0 0 0 y . . . . 0 * [ 64084.250] 10 67 4b TrueColor 32 0 y . y copy . 8 8 8 0 16 8 0 16 16 16 0 0 0 y . . . . 0 * 10 67 4b TrueColor 32 0 y . y copy . 8 8 8 0 16 8 0 16 16 16 0 0 0 y . . . . 0 * [ 64084.250] 11 68 4c TrueColor 32 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 y y . . . 0 * 11 68 4c TrueColor 32 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 y y . . . 0 * [ 64084.250] 12 69 4d TrueColor 32 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 y y . . . 0 * 12 69 4d TrueColor 32 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 y y . . . 0 * [ 64084.250] 13 6a 4e TrueColor 32 0 y . y copy . 8 8 8 8 32 8 0 16 16 16 16 0 0 y . . . . 0 * 13 6a 4e TrueColor 32 0 y . y copy . 8 8 8 8 32 8 0 16 16 16 16 0 0 y . . . . 0 * [ 64084.250] 14 6b 4f TrueColor 32 0 y . y copy . 8 8 8 8 16 8 0 16 16 16 16 0 0 y . . . . 0 * 14 6b 4f TrueColor 32 0 y . y copy . 8 8 8 8 16 8 0 16 16 16 16 0 0 y . . . . 0 * [ 64084.250] 19 0 50 TrueColor 24 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 . y . . . 0 * 19 0 50 TrueColor 24 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 . y . . . 0 * [ 64084.250] 20 0 51 TrueColor 24 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 . y . . . 0 * 20 0 51 TrueColor 24 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 . y . . . 0 * [ 64084.250] 21 0 52 TrueColor 24 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 . y . . . 0 * 21 0 52 TrueColor 24 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 . y . . . 0 * [ 64084.250] 22 0 53 TrueColor 24 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 . y . . . 0 * 22 0 53 TrueColor 24 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 . y . . . 0 * [ 64084.250] 25 0 54 TrueColor 16 0 y . . . 5 5 5 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * 25 0 54 TrueColor 16 0 y . . . 5 5 5 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * [ 64084.250] 26 0 55 TrueColor 16 0 y . . . 5 5 5 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * 26 0 55 TrueColor 16 0 y . . . 5 5 5 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * [ 64084.250] 27 0 56 TrueColor 16 0 y . . . 5 5 5 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * 27 0 56 TrueColor 16 0 y . . . 5 5 5 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * [ 64084.250] 28 0 57 TrueColor 16 0 y . . . 5 5 5 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * 28 0 57 TrueColor 16 0 y . . . 5 5 5 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * [ 64084.250] 31 0 58 TrueColor 8 0 y . . . 3 3 2 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * 31 0 58 TrueColor 8 0 y . . . 3 3 2 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * [ 64084.250] 32 0 59 TrueColor 8 0 y . . . 3 3 2 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * 32 0 59 TrueColor 8 0 y . . . 3 3 2 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * [ 64084.250] 33 0 5a TrueColor 8 0 y . . . 3 3 2 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * 33 0 5a TrueColor 8 0 y . . . 3 3 2 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * [ 64084.250] 34 0 5b TrueColor 8 0 y . . . 3 3 2 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * 34 0 5b TrueColor 8 0 y . . . 3 3 2 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * [ 64084.250] 37 0 5c TrueColor 4 0 y . . . 1 1 1 0 32 8 0 5 6 5 0 0 0 . y . . . 0 * 37 0 5c TrueColor 4 0 y . . . 1 1 1 0 32 8 0 5 6 5 0 0 0 . y . . . 0 * [ 64084.250] 38 0 5d TrueColor 4 0 y . . . 1 1 1 0 16 8 0 5 6 5 0 0 0 . y . . . 0 * 38 0 5d TrueColor 4 0 y . . . 1 1 1 0 16 8 0 5 6 5 0 0 0 . y . . . 0 * [ 64084.250] 39 0 5e TrueColor 4 0 y . . . 1 1 1 8 32 8 0 4 4 4 4 0 0 . y . . . 0 * 39 0 5e TrueColor 4 0 y . . . 1 1 1 8 32 8 0 4 4 4 4 0 0 . y . . . 0 * [ 64084.250] 40 0 5f TrueColor 4 0 y . . . 1 1 1 8 16 8 0 4 4 4 4 0 0 . y . . . 0 * 40 0 5f TrueColor 4 0 y . . . 1 1 1 8 16 8 0 4 4 4 4 0 0 . y . . . 0 * [ 64084.250] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 64084.265] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [ 64084.265] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [ 64084.265] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [ 64084.437] winPointerWarpCursor - Discarding first warp: 840 525 winPointerWarpCursor - Discarding first warp: 840 525 [ 64084.437] (--) 3 mouse buttons found (--) 3 mouse buttons found [ 64084.437] (--) Setting autorepeat to delay=500, rate=31 (--) Setting autorepeat to delay=500, rate=31 [ 64084.437] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [ 64084.437] (--) Found matching XKB configuration "English (USA)" (--) Found matching XKB configuration "English (USA)" [ 64084.437] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 64084.437] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 64084.437] winBlockHandler - pthread_mutex_unlock() winBlockHandler - pthread_mutex_unlock() [ 64084.437] winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_lock () returned. [ 64084.437] winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. [ 64084.437] winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. [ 64084.437] winInitMultiWindowWM - DISPLAY=:0.0 winInitMultiWindowWM - DISPLAY=:0.0 [ 64084.437] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [ 64084.453] winProcEstablishConnection - winInitClipboard returned. winProcEstablishConnection - winInitClipboard returned. [ 64084.453] winMultiWindowXMsgProc - DISPLAY=:0.0 winMultiWindowXMsgProc - DISPLAY=:0.0 [ 64084.453] winClipboardProc - DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 [ 64084.453] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [ 64084.468] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 64084.468] winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 64144.546] Segmentation fault at address 0x44 Segmentation fault at address 0x44 [ 64144.546] Fatal server error: Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] [ 64144.546] Server terminated with error (1). Closing log file. Server terminated with error (1). Closing log file. -- 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 klindsay@ucar.edu Wed Apr 25 20:20:00 2012 From: klindsay@ucar.edu (Keith Lindsay) Date: Wed, 25 Apr 2012 20:20:00 -0000 Subject: X segmentation fault when particular application attempts to open a window Message-ID: <4F985C8A.6020209@ucar.edu> Hi, I'm running a data analysis program called ferret on a remote machine that I've logged on to with "ssh -X". When the program attempts to create a window, the Cygwin/X server crashes with a segmentation fault. The seg fault is reproducible. xclock works fine from the same remote machine. This is with version 1.12.0-4 of xorg-server. ferret has worked with some previous versions of the Cygwin/X server, but I'm not certain about the precise version where the breakage occurred. I backed up one version and encountered the same problem. I've attached the output of "cygcheck -c", the file /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to the XWin process when it crashes. I'm at a loss about how to proceed further. I welcome any advice that you can provide. Thank you, Keith Lindsay -------------- next part -------------- Cygwin Package Information Package Version Status _autorebase 000040-1 OK _update-info-dir 01043-1 OK alternatives 1.3.30c-10 OK aspell 0.60.6.1-1 OK aspell-en 7.1.0-1 OK autoconf 10-1 OK autoconf2.1 2.13-10 OK autoconf2.5 2.68-1 OK automake 4-10 OK automake1.10 1.10.3-1 OK automake1.11 1.11.3-1 OK automake1.4 1.4p6-10 OK automake1.5 1.5-10 OK automake1.6 1.6.3-11 OK automake1.7 1.7.9-10 OK automake1.8 1.8.5-10 OK automake1.9 1.9.6-10 OK base-cygwin 3.1-1 OK base-files 4.1-1 OK base-passwd 3.1-2 OK bash 4.1.10-4 OK bc 1.06-2 OK bcrypt 1.1-1 OK binutils 2.22.51-2 OK bzip2 1.0.6-2 OK ca-certificates 1.81-1 OK ccrypt 1.9-1 OK clisp 2.48-3 OK coreutils 8.15-1 OK crypt 1.1-1 OK csih 0.9.6-1 OK cygrunsrv 1.40-1 OK cygutils 1.4.10-2 OK cygwin 1.7.14-1 OK cygwin-doc 1.7-1 OK cygwin-x-doc 1.1.1-1 OK dash 0.5.7-1 OK dbus 1.4.16-1 OK dialog 1.1-20111020-1 OK diffutils 3.2-1 OK dos2unix 5.3.3-1 OK dri-drivers 7.11.2-1 OK e2fsprogs 1.41.14-1 OK ed 1.6-1 OK editrights 1.01-2 OK emacs 23.4-1 OK emacs-X11 23.4-1 OK enscript 1.6.4-3 OK file 5.11-1 OK findutils 4.5.9-2 OK font-adobe-dpi75 1.0.2-1 OK font-alias 1.0.3-1 OK font-bitstream-dpi100 1.0.2-1 OK font-bitstream-dpi75 1.0.2-1 OK font-bitstream-speedo 1.0.1-1 OK font-bitstream-type1 1.0.2-1 OK font-bitstream-vera-ttf 1.10-1 OK font-daewoo-misc 1.0.2-1 OK font-encodings 1.0.4-1 OK font-isas-misc 1.0.2-1 OK font-jis-misc 1.0.2-1 OK font-misc-misc 1.1.1-1 OK fontconfig 2.8.0-2 OK fontsproto 2.1.2-1 OK gamin 0.1.10-11 OK gawk 4.0.1-1 OK gcc4-core 4.5.3-3 OK gcc4-fortran 4.5.3-3 OK gcc4-g++ 4.5.3-3 OK gdb 7.3.50-3 OK gettext 0.18.1.1-2 OK ghostscript 9.04-1 OK ghostscript-fonts-other 6.0-1 OK ghostscript-fonts-std 8.11-1 OK gmp 4.3.2-1 OK gnome-icon-theme 3.2.1.2-1 OK gnuplot 4.4.4-1 OK grep 2.6.3-1 OK groff 1.21-2 OK gsettings-desktop-schemas 3.2.0-1 OK guile 1.8.7-2 OK gv 3.7.3-1 OK gzip 1.4-1 OK hdf5 1.8.8-1 OK hicolor-icon-theme 0.12-1 OK ImageMagick 6.7.6.3-1 OK imake 1.0.4-1 OK ipc-utils 1.0-1 OK joe 3.7-1 OK kbproto 1.0.6-1 OK less 444-1 OK libapr1 1.4.6-1 OK libaprutil1 1.4.1-1 OK libarpack0 3.1.0-1 OK libasn1_8 1.5.2-2 OK libaspell15 0.60.6.1-1 OK libatk1.0_0 2.2.0-1 OK libattr1 2.4.43-1 OK libaudio2 1.9.3-1 OK libautotrace3 0.31.1-11 OK libblkid1 2.21-1 OK libbz2-devel 1.0.6-2 OK libbz2_1 1.0.6-2 OK libcairo2 1.10.2-1 OK libcatgets1 1.1-1 OK libcharset1 1.14-2 OK libcloog0 0.15.7-1 OK libcom_err2 1.41.14-1 OK libcompface0 1.5.2-11 OK libcroco0.6_3 0.6.4-1 OK libcurl4 7.24.0-3 OK libdatrie1 0.2.4-1 OK libdb4.2 4.2.52.5-2 OK libdb4.5 4.5.20.2-3 OK libdb4.8 4.8.30-1 OK libdbus1_3 1.4.16-1 OK libdialog10 1.1-20111020-1 OK libe2p2 1.41.14-1 OK libedit0 20090923-1 OK libEMF1 1.0.4-1 OK libexpat1 2.0.1-1 OK libexpat1-devel 2.0.1-1 OK libext2fs2 1.41.14-1 OK libfam0 0.1.10-11 OK libfcgi0 2.4.0-2 OK libffi4 4.5.3-3 OK libfftw3_3 3.3-1 OK libfltk1.1 1.1.10-1 OK libfontconfig-devel 2.8.0-2 OK libfontconfig1 2.8.0-2 OK libfontenc1 1.1.0-1 OK libfpx 1.3.1-1 OK libfpx1 1.3.1-1 OK libfreetype-devel 2.4.9-2 OK libfreetype6 2.4.9-2 OK libgcc1 4.5.3-3 OK libgcj-common 4.5.3-3 OK libgcj11 4.5.3-3 OK libgcrypt11 1.4.6-1 OK libgd2 2.0.36RC1-12 OK libgdbm4 1.8.3-20 OK libgdk_pixbuf2.0_0 2.24.1-1 OK libgfortran3 4.5.3-3 OK libggi2 2.2.2-2 OK libggiwmh0 0.3.2-2 OK libgif4 4.1.6-10 OK libgii1 1.0.2-2 OK libGL1 7.11.2-1 OK libglapi0 7.11.2-1 OK libglib2.0_0 2.30.2-1 OK libglitz1 0.5.6-10 OK libglpk0 4.47-1 OK libGLU1 7.11.2-1 OK libgmp3 4.3.2-1 OK libgmpxx4 4.3.2-1 OK libgnutls26 2.12.14-1 OK libgomp1 4.5.3-3 OK libgpg-error0 1.10-1 OK libGraphicsMagick3 1.3.14-1 OK libgs8 8.63-2 OK libgs9 9.04-1 OK libgsf1_114 1.14.22-1 OK libgssapi3 1.5.2-2 OK libgtk2.0_0 2.24.10-1 OK libguile12 1.6.7-4 OK libguile17 1.8.7-2 OK libhdf5_0 1.6.9-2 OK libhdf5_6 1.8.6-1 OK libhdf5_7 1.8.8-1 OK libheimbase1 1.5.2-2 OK libheimntlm0 1.5.2-2 OK libhx509_5 1.5.2-2 OK libICE-devel 1.0.7-1 OK libICE6 1.0.7-1 OK libiconv 1.14-2 OK libiconv2 1.14-2 OK libicu48 4.8.1-1 OK libidn11 1.22-1 OK libImageMagick1 6.4.0.6-2 OK libintl3 0.14.5-1 OK libintl8 0.18.1.1-2 OK libjasper1 1.900.1-12 OK libjbig2 2.0-11 OK libjpeg62 6b-21 OK libjpeg7 7-10 OK libjpeg8 8b-1 OK libkafs0 1.5.2-2 OK libkpathsea3 2.0.2-15 OK libkpathsea4 3.0.0-3 OK libkpathsea6 20110705-1 OK libkrb5_26 1.5.2-2 OK liblapack0 3.4.0-3 OK liblcms1 1.19-2 OK liblcms2_2 2.2-1 OK libllvm3.0 3.0-1 OK libltdl3 1.5.27a-1 OK libltdl7 2.4-1 OK liblzma1 4.999.9beta-11 OK liblzma5 5.0.2_20110517-1 OK liblzo2_2 2.06-1 OK libMagickCore5 6.7.6.3-1 OK libmcrypt4 2.5.8-10 OK libming1 0.4.4-1 OK libmpc1 0.8-1 OK libmpfr1 2.4.1-4 OK libmpfr4 3.0.1-1 OK libncurses10 5.7-18 OK libncurses7 5.3-4 OK libncurses8 5.5-10 OK libncurses9 5.7-16 OK libncursesw10 5.7-18 OK libneon27 0.29.6-2 OK libnetpbm-devel 10.57.03-1 OK libnetpbm10 10.57.03-1 OK libopenjpeg1 1.5.0-1 OK libopenldap2_3_0 2.3.43-3 OK libopenssl098 0.9.8w-1 OK libopenssl100 1.0.1a-1 OK libpango1.0_0 1.29.4-2 OK libpaper-bin 1.1.24-1 OK libpaper1 1.1.24-1 OK libpcre0 8.21-2 OK libpixman1_0 0.24.4-1 OK libplot2 2.6-2 OK libplotter2 2.6-2 OK libpng12 1.2.46-1 OK libpng14 1.4.8-1 OK libpoppler19 0.18.4-2 OK libpopt0 1.6.4-4 OK libppl 0.10.2-1 OK libpq5 8.2.11-1 OK libproxy0 0.2.3-2 OK libproxy1 0.4.7-1 OK libpstoedit0 3.60-2 OK libptexenc1 20110705-1 OK libpthread-stubs 0.2-1 OK libqhull_5 2009.1.1-1 OK libqhull_6 2012.1-2 OK libqrupdate0 1.1.2-1 OK libreadline6 5.2.14-12 OK libreadline7 6.1.2-2 OK libRmath 2.14.2-1 OK libRmath-devel 2.14.2-1 OK libroken18 1.5.2-2 OK librsvg2_2 2.34.2-1 OK libsasl2 2.1.23-1 OK libserf0_0 0.3.1-1 OK libserf0_1 0.7.1-2 OK libserf1_0 1.0.3-1 OK libsigsegv2 2.10-1 OK libSM-devel 1.2.0-1 OK libSM6 1.2.0-1 OK libsqlite3_0 3.7.3-1 OK libss2 1.41.14-1 OK libssh2_1 1.4.0-1 OK libssp0 4.5.3-3 OK libstdc++6 4.5.3-3 OK libstdc++6-devel 4.5.3-3 OK libtasn1_3 2.12-1 OK libthai0 0.1.15-1 OK libtiff4 3.6.0-5 OK libtiff5 3.9.4-1 OK libtiff6 4.0.0beta5-1 OK libtool 2.4-1 OK libuuid-devel 2.21-1 OK libuuid1 2.21-1 OK libwind0 1.5.2-2 OK libwmf027 0.2.8.4-10 OK libwrap0 7.6-21 OK libX11-devel 1.4.4-1 OK libX11-xcb1 1.4.4-1 OK libX11_6 1.4.4-1 OK libXau-devel 1.0.6-1 OK libXau6 1.0.6-1 OK libXaw-devel 1.0.9-1 OK libXaw3d7 1.5D-10 OK libXaw7 1.0.9-1 OK libXaw8 6.8.99.901-1 OK libxcb-devel 1.7-2 OK libxcb-glx0 1.7-2 OK libxcb-render-util0 0.3.8-1 OK libxcb-render0 1.7-2 OK libxcb-shm0 1.7-2 OK libxcb1 1.7-2 OK libXcomposite1 0.4.3-1 OK libXcursor1 1.1.12-1 OK libXdamage1 1.1.3-1 OK libXdmcp-devel 1.1.0-1 OK libXdmcp6 1.1.0-1 OK libXext-devel 1.3.0-1 OK libXext6 1.3.0-1 OK libXfixes3 5.0-1 OK libXft2 2.2.0-1 OK libXi6 1.4.5-1 OK libXinerama1 1.1.1-1 OK libxkbfile1 1.0.7-1 OK libXm-devel 0.95.2-2 OK libXm2 0.95.2-2 OK libxml2 2.7.8-3 OK libXmu-devel 1.1.0-1 OK libXmu6 1.1.0-1 OK libXmuu1 1.1.0-1 OK libXp6 6.8.99.901-1 OK libXpm-devel 3.5.9-1 OK libXpm4 3.5.9-1 OK libXrandr2 1.3.2-1 OK libXrender1 0.9.6-1 OK libXss1 1.2.0-1 OK libXt-devel 1.1.1-1 OK libXt6 1.1.1-1 OK libzzip0.13 0.13.60-1 OK lilypond 2.14.1-1 OK lilypond-doc 2.14.1-1 OK login 1.10-10 OK lua 5.1.4-11 OK luit 1.1.0-1 OK m4 1.4.16-1 OK make 3.82.90-1 OK makedepend 1.0.3-1 OK man 1.6g-1 OK mcrypt 2.6.8-1 OK mhash 0.9.2-1 OK minires 1.02-1 OK mintty 1.0.3-1 OK mkfontdir 1.0.6-1 OK mkfontscale 1.0.9-1 OK multitail 5.2.8-1 OK nano 2.2.5-1 OK ncurses 5.7-18 OK nedit 5.5-4 OK netpbm 10.57.03-1 OK nfrotz 0.3.3-3 OK octave 3.6.1-1 OK octave-doc 3.6.1-1 OK openssh 6.0p1-1 OK openssl 1.0.1a-1 OK pdftk 1.44-1 OK perl 5.10.1-5 OK ping 1.0-1 OK poppler-data 0.4.5-1 OK printproto 1.0.4-1 OK procps 3.2.7-1 OK python 2.6.7-1 OK python-doc 2.6.7-1 OK python-numpy 1.5.1-1 OK R 2.14.2-1 OK rebase 4.1.0-1 OK rsync 3.0.9-1 OK ruby 1.8.7-p358-2 OK run 1.1.13-1 OK rxvt 20050409-21 OK screen 4.0.3-7 OK sed 4.2.1-1 OK shared-mime-info 1.0-1 OK sharutils 4.10-2 OK subversion 1.7.4-1 OK sudoku 1.0.1-1 OK sysvinit 2.86-10 OK t1lib5 5.1.2-11 OK tar 1.25-1 OK tcl 8.5.11-1 OK tcl-tk 8.5.11-1 OK tcltk 20120206-1 OK tcsh 6.18.00-3 OK ted 2.21-1 OK termcap 5.7_20091114-14 OK terminfo 5.7_20091114-14 OK terminfo0 5.5_20061104-12 OK tetex-base 20120119-1 OK tetex-bin 20120119-1 OK tetex-doc 20120119-1 OK tetex-extra 20120119-1 OK tetex-tiny 20120119-1 OK tetex-x11 20120119-1 OK texinfo 4.13-4 OK texlive 20110705-1 OK texlive-collection-basic 20120312-1 OK texlive-collection-bibtexextra 20120312-1 OK texlive-collection-binextra 20120312-1 OK texlive-collection-documentation-base 20120312-1 OK texlive-collection-documentation-english 20120312-1 OK texlive-collection-fontsextra 20120312-1 OK texlive-collection-fontsrecommended 20120312-1 OK texlive-collection-fontutils 20120202-1 OK texlive-collection-formatsextra 20120202-1 OK texlive-collection-games 20120202-1 OK texlive-collection-genericextra 20120202-1 OK texlive-collection-genericrecommended 20120312-1 OK texlive-collection-humanities 20120312-1 OK texlive-collection-latex 20120312-1 OK texlive-collection-latexextra 20120312-1 OK texlive-collection-latexrecommended 20120312-1 OK texlive-collection-mathextra 20120312-1 OK texlive-collection-metapost 20120312-1 OK texlive-collection-pictures 20120312-1 OK texlive-collection-texinfo 20120312-1 OK time 1.7-2 OK transfig 3.2.5d-1 OK tzcode 2012b-1 OK unzip 6.0-10 OK util-linux 2.21-1 OK vim 7.3.447-1 OK vim-common 7.3.447-1 OK w32api 3.17-2 OK wget 1.13.4-1 OK which 2.20-2 OK X-start-menu-icons 1.0.4-1 OK xauth 1.0.6-1 OK xcalc 1.0.4.1-1 OK xclock 1.0.5-2 OK xcursor-themes 1.0.3-1 OK xemacs-emacs-common 21.4.22-1 OK xextproto 7.2.1-1 OK xeyes 1.1.1-1 OK xf86-video-dummy 0.3.5-1 OK xf86-video-nested 0.1.0-1 OK xfig 3.2.5b-2 OK xfig-lib 3.2.5b-2 OK xinit 1.3.2-1 OK xkbcomp 1.2.3-1 OK xkeyboard-config 2.5.1-1 OK xmodmap 1.0.5-1 OK xorg-cf-files 1.0.4-1 OK xorg-docs 1.6-1 OK xorg-server 1.12.0-4 OK xorg-server-common 1.12.0-4 OK xpdf 3.03-1 OK xproto 7.0.23-1 OK xrdb 1.0.9-1 OK xterm 278-1 OK xxd 7.3.447-1 OK xz 5.0.2_20110517-1 OK zip 3.0-11 OK zlib 1.2.5-1 OK zlib-devel 1.2.5-1 OK zlib0 1.2.5-1 OK -------------- next part -------------- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.12.0.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win32) Package: version 1.12.0-4 built 2012-04-17 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1440 h 900 winInitializeScreenDefaults - native DPI x 96 y 96 [ 18194.599] (--) Windows reports only 2 mouse buttons, defaulting to -emulate3buttons [ 18194.599] (II) xorg.conf is not supported [ 18194.599] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 18194.599] LoadPreferences: /home/klindsay/.XWinrc not found [ 18194.630] LoadPreferences: Loading /etc/X11/system.XWinrc [ 18194.646] LoadPreferences: Done parsing the configuration file... [ 18194.880] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [ 18194.880] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 18194.880] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 18194.927] winDetectSupportedEngines - Returning, supported engines 0000001f [ 18194.927] winSetEngine - Multi Window or Rootless => ShadowGDI [ 18194.927] winScreenInit - Using Windows display depth of 32 bits per pixel [ 18194.942] winAllocateFBShadowGDI - Creating DIB with width: 1440 height: 900 depth: 32 [ 18194.942] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 18194.942] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 18194.942] winInitMultiWindowWM - Calling pthread_mutex_lock () [ 18194.942] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 18194.958] MIT-SHM extension disabled due to lack of kernel support [ 18194.973] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 18195.098] GL_VERSION: 2.1.2 [ 18195.098] GL_VENDOR: NVIDIA Corporation [ 18195.098] GL_RENDERER: Quadro NVS 160M/PCI/SSE2 [ 18195.098] GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_fragment_program [ 18195.098] GL_EXTENSIONS: GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_half_float_pixel GL_ARB_imaging [ 18195.098] GL_EXTENSIONS: GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object [ 18195.098] GL_EXTENSIONS: GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow GL_ARB_shader_objects [ 18195.098] GL_EXTENSIONS: GL_ARB_shading_language_100 GL_ARB_texture_border_clamp GL_ARB_texture_compression [ 18195.098] GL_EXTENSIONS: GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 [ 18195.098] GL_EXTENSIONS: GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two [ 18195.098] GL_EXTENSIONS: GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program [ 18195.098] GL_EXTENSIONS: GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float [ 18195.098] GL_EXTENSIONS: GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color [ 18195.098] GL_EXTENSIONS: GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract [ 18195.098] GL_EXTENSIONS: GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_bindable_uniform GL_EXT_depth_bounds_test [ 18195.098] GL_EXTENSIONS: GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord [ 18195.098] GL_EXTENSIONS: GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object [ 18195.098] GL_EXTENSIONS: GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 [ 18195.098] GL_EXTENSIONS: GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil [ 18195.098] GL_EXTENSIONS: GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters [ 18195.098] GL_EXTENSIONS: GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs [ 18195.098] GL_EXTENSIONS: GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array [ 18195.098] GL_EXTENSIONS: GL_EXT_texture_buffer_object GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc [ 18195.098] GL_EXTENSIONS: GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp [ 18195.098] GL_EXTENSIONS: GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic [ 18195.098] GL_EXTENSIONS: GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp [ 18195.098] GL_EXTENSIONS: GL_EXT_texture_object GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_EXT_timer_query [ 18195.098] GL_EXTENSIONS: GL_EXT_vertex_array GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region [ 18195.098] GL_EXTENSIONS: GL_NV_blend_square GL_NV_copy_depth_to_color GL_NV_depth_buffer_float GL_NV_conditional_render [ 18195.098] GL_EXTENSIONS: GL_NV_depth_clamp GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program [ 18195.098] GL_EXTENSIONS: GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage [ 18195.098] GL_EXTENSIONS: GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent [ 18195.098] GL_EXTENSIONS: GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query [ 18195.098] GL_EXTENSIONS: GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_pixel_data_range GL_NV_point_sprite [ 18195.098] GL_EXTENSIONS: GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_texgen_reflection [ 18195.098] GL_EXTENSIONS: GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal [ 18195.098] GL_EXTENSIONS: GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 [ 18195.098] GL_EXTENSIONS: GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_program [ 18195.098] GL_EXTENSIONS: GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 [ 18195.098] GL_EXTENSIONS: GL_NVX_conditional_render GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture [ 18195.098] GL_EXTENSIONS: GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control [ 18195.098] WGL_EXTENSIONS: WGL_ARB_buffer_region WGL_ARB_extensions_string WGL_ARB_make_current_read WGL_ARB_multisample [ 18195.098] WGL_EXTENSIONS: WGL_ARB_pbuffer WGL_ARB_pixel_format WGL_ARB_pixel_format_float WGL_ARB_render_texture [ 18195.098] WGL_EXTENSIONS: WGL_ATI_pixel_format_float WGL_EXT_extensions_string WGL_EXT_framebuffer_sRGB [ 18195.098] WGL_EXTENSIONS: WGL_EXT_pixel_format_packed_float WGL_EXT_swap_control WGL_NV_float_buffer WGL_NV_multisample_coverage [ 18195.098] WGL_EXTENSIONS: WGL_NV_render_depth_texture WGL_NV_render_texture_rectangle [ 18195.098] (II) AIGLX: enabled GLX_SGI_make_current_read [ 18195.098] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 18195.098] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 18195.098] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 18195.098] (II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample [ 18195.098] (II) AIGLX: Set GLX version to 1.4 [ 18195.098] 305 fbConfigs [ 18195.098] pxf vis fb render Ste aux accum MS drawable Group/ [ 18195.098] idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat [ 18195.098] ----------------------------------------------------------------------------------------------------------------------------- [ 18195.098] 1 173 42 TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 2 174 43 TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 3 175 44 TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 4 176 45 TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 5 177 46 TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 6 178 47 TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 7 179 48 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 8 17a 49 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.098] 9 17b 4a TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 10 21 4b TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 11 17c 4c TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 12 17d 4d TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 13 17e 4e TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 14 17f 4f TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 15 180 50 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 16 41 51 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 17 181 52 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 18 182 53 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 0 0 y . y . . 2 [ 18195.114] 19 183 54 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 20 184 55 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 21 185 56 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 22 186 57 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 23 187 58 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 24 188 59 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 25 189 5a TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 26 18a 5b TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 27 18b 5c TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 28 18c 5d TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 29 18d 5e TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 30 18e 5f TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 2 y . y . . 2 [ 18195.114] 31 18f 60 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 32 190 61 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 33 191 62 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 34 192 63 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 35 193 64 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 36 194 65 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 37 195 66 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 38 196 67 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 39 197 68 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 40 198 69 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 41 199 6a TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 42 19a 6b TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 4 y . y . . 2 [ 18195.114] 43 19b 6c TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 44 19c 6d TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 45 19d 6e TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 46 19e 6f TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 47 19f 70 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 48 1a0 71 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 49 1a1 72 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 50 1a2 73 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 51 1a3 74 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 52 1a4 75 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 53 1a5 76 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 54 1a6 77 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 55 1a7 78 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 56 1a8 79 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 57 1a9 7a TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 58 1aa 7b TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 59 1ab 7c TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 60 1ac 7d TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 61 1ad 7e TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 62 1ae 7f TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 63 1af 80 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 64 1b0 81 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 65 1b1 82 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 66 1b2 83 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 67 1b3 84 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 68 1b4 85 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 69 1b5 86 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 70 1b6 87 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 71 1b7 88 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 72 1b8 89 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 73 1b9 8a TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 74 1ba 8b TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 8 y . y . . 2 [ 18195.114] 75 1bb 8c TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 76 1bc 8d TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 77 1bd 8e TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 78 1be 8f TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 79 1bf 90 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 80 1c0 91 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 81 1c1 92 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 82 1c2 93 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 83 1c3 94 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 84 1c4 95 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 85 1c5 96 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 86 1c6 97 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 87 1c7 98 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 88 1c8 99 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 89 1c9 9a TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 90 1ca 9b TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 y . y . . 2 [ 18195.114] 91 1cb 9c TrueColor 32 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 y y . . . 0 * [ 18195.114] 92 1cc 9d TrueColor 32 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 y y . . . 0 * [ 18195.114] 93 1cd 9e TrueColor 32 0 y . y copy . 8 8 8 0 32 8 0 16 16 16 0 0 0 y . . . . 0 * [ 18195.114] 94 1ce 9f TrueColor 32 0 y . y copy . 8 8 8 0 16 8 0 16 16 16 0 0 0 y . . . . 0 * [ 18195.114] 95 1cf a0 TrueColor 32 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 y y . . . 0 * [ 18195.114] 96 1d0 a1 TrueColor 32 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 y y . . . 0 * [ 18195.114] 97 1d1 a2 TrueColor 32 0 y . y copy . 8 8 8 8 32 8 0 16 16 16 16 0 0 y . . . . 0 * [ 18195.114] 98 1d2 a3 TrueColor 32 0 y . y copy . 8 8 8 8 16 8 0 16 16 16 16 0 0 y . . . . 0 * [ 18195.114] 103 0 a4 TrueColor 24 0 y . . . 8 8 8 0 32 8 0 16 16 16 0 0 0 . y . . . 0 * [ 18195.114] 104 0 a5 TrueColor 24 0 y . . . 8 8 8 0 16 8 0 16 16 16 0 0 0 . y . . . 0 * [ 18195.114] 105 0 a6 TrueColor 24 0 y . . . 8 8 8 8 32 8 0 16 16 16 16 0 0 . y . . . 0 * [ 18195.114] 106 0 a7 TrueColor 24 0 y . . . 8 8 8 8 16 8 0 16 16 16 16 0 0 . y . . . 0 * [ 18195.114] 109 0 a8 TrueColor 16 0 y . . . 5 5 5 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * [ 18195.114] 110 0 a9 TrueColor 16 0 y . . . 5 5 5 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * [ 18195.114] 111 0 aa TrueColor 16 0 y . . . 5 5 5 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * [ 18195.114] 112 0 ab TrueColor 16 0 y . . . 5 5 5 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * [ 18195.114] 115 0 ac TrueColor 8 0 y . . . 3 3 2 0 32 8 0 11 11 10 0 0 0 . y . . . 0 * [ 18195.114] 116 0 ad TrueColor 8 0 y . . . 3 3 2 0 16 8 0 11 11 10 0 0 0 . y . . . 0 * [ 18195.114] 117 0 ae TrueColor 8 0 y . . . 3 3 2 8 32 8 0 8 8 8 8 0 0 . y . . . 0 * [ 18195.114] 118 0 af TrueColor 8 0 y . . . 3 3 2 8 16 8 0 8 8 8 8 0 0 . y . . . 0 * [ 18195.114] 121 0 b0 TrueColor 4 0 y . . . 1 1 1 0 32 8 0 5 6 5 0 0 0 . y . . . 0 * [ 18195.114] 122 0 b1 TrueColor 4 0 y . . . 1 1 1 0 16 8 0 5 6 5 0 0 0 . y . . . 0 * [ 18195.114] 123 0 b2 TrueColor 4 0 y . . . 1 1 1 8 32 8 0 4 4 4 4 0 0 . y . . . 0 * [ 18195.114] 124 0 b3 TrueColor 4 0 y . . . 1 1 1 8 16 8 0 4 4 4 4 0 0 . y . . . 0 * [ 18195.114] 127 0 b4 TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 128 0 b5 TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 129 0 b6 TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 130 0 b7 TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 131 0 b8 TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 132 0 b9 TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 133 0 ba TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 134 0 bb TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 135 0 bc TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 136 0 bd TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 137 0 be TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 138 0 bf TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 139 0 c0 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 140 0 c1 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 141 0 c2 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 142 0 c3 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 143 0 c4 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 144 0 c5 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 145 0 c6 TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 146 0 c7 TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 147 0 c8 TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 148 0 c9 TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 149 0 ca TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 150 0 cb TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 151 0 cc TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 152 0 cd TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 153 0 ce TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 154 0 cf TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 155 0 d0 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 156 0 d1 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 157 0 d2 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 158 0 d3 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 159 0 d4 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 160 0 d5 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 161 0 d6 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 162 0 d7 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 163 0 d8 TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 164 0 d9 TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 165 0 da TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 166 0 db TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 167 0 dc TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 168 0 dd TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 169 0 de TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 170 0 df TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 171 0 e0 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 172 0 e1 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 173 0 e2 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 174 0 e3 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 175 0 e4 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 176 0 e5 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 177 0 e6 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 178 0 e7 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 179 0 e8 TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 180 0 e9 TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 181 0 ea TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 182 0 eb TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 183 0 ec TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 184 0 ed TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 185 0 ee TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 186 0 ef TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 187 0 f0 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 188 0 f1 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 189 0 f2 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 190 0 f3 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 191 0 f4 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 192 0 f5 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 193 0 f6 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 194 0 f7 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 195 0 f8 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 196 0 f9 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 197 0 fa TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 198 0 fb TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 199 0 fc TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 200 0 fd TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 201 0 fe TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 202 0 ff TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 203 0 100 TrueColor 32 0 y . . . 8 8 8 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 204 0 101 TrueColor 32 0 y . . . 8 8 8 8 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 205 0 102 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 206 0 103 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 207 0 104 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 208 0 105 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 209 0 106 TrueColor 32 0 y . y xchg . 8 8 8 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 210 0 107 TrueColor 32 0 y . y xchg . 8 8 8 8 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 211 0 108 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 212 0 109 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 213 0 10a TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 214 0 10b TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 215 0 10c TrueColor 32 0 y . y copy . 8 8 8 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 216 0 10d TrueColor 32 0 y . y copy . 8 8 8 8 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 217 0 10e TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 218 0 10f TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 219 0 110 TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 220 0 111 TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 221 0 112 TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 222 0 113 TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 223 0 114 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 224 0 115 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 225 0 116 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 226 0 117 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 227 0 118 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 228 0 119 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 229 0 11a TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 230 0 11b TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 231 0 11c TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 232 0 11d TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 233 0 11e TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 234 0 11f TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 235 0 120 TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 236 0 121 TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 237 0 122 TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 238 0 123 TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 239 0 124 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 240 0 125 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 241 0 126 TrueColor 32 0 y . . . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 242 0 127 TrueColor 32 0 y . . . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 243 0 128 TrueColor 32 0 y . . . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 244 0 129 TrueColor 32 0 y . . . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 245 0 12a TrueColor 32 0 y . y xchg . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 246 0 12b TrueColor 32 0 y . y xchg . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 247 0 12c TrueColor 32 0 y . y xchg . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 248 0 12d TrueColor 32 0 y . y xchg . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 249 0 12e TrueColor 32 0 y . y copy . 8 8 8 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 250 0 12f TrueColor 32 0 y . y copy . 8 8 8 8 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 251 0 130 TrueColor 32 0 y . y copy . 8 8 8 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 252 0 131 TrueColor 32 0 y . y copy . 8 8 8 8 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 253 0 132 TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 254 0 133 TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 255 0 134 TrueColor 16 0 y . . . 5 6 5 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 256 0 135 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 257 0 136 TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 258 0 137 TrueColor 16 0 y . y xchg . 5 6 5 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 259 0 138 TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 260 0 139 TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 261 0 13a TrueColor 16 0 y . y copy . 5 6 5 0 0 0 4 16 16 16 16 0 0 . . y . . 2 [ 18195.114] 262 0 13b TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 263 0 13c TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 264 0 13d TrueColor 16 0 y . . . 5 6 5 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 265 0 13e TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 266 0 13f TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 267 0 140 TrueColor 16 0 y . y xchg . 5 6 5 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 268 0 141 TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 269 0 142 TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 270 0 143 TrueColor 16 0 y . y copy . 5 6 5 0 0 0 4 16 16 16 16 1 2 . . y . . 2 [ 18195.114] 271 0 144 TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 272 0 145 TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 273 0 146 TrueColor 16 0 y . . . 5 6 5 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 274 0 147 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 275 0 148 TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 276 0 149 TrueColor 16 0 y . y xchg . 5 6 5 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 277 0 14a TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 278 0 14b TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 279 0 14c TrueColor 16 0 y . y copy . 5 6 5 0 0 0 4 16 16 16 16 1 4 . . y . . 2 [ 18195.114] 280 0 14d TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 281 0 14e TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 282 0 14f TrueColor 16 0 y . . . 5 6 5 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 283 0 150 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 284 0 151 TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 285 0 152 TrueColor 16 0 y . y xchg . 5 6 5 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 286 0 153 TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 287 0 154 TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 288 0 155 TrueColor 16 0 y . y copy . 5 6 5 0 0 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 289 0 156 TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 290 0 157 TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 291 0 158 TrueColor 16 0 y . . . 5 6 5 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 292 0 159 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 293 0 15a TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 294 0 15b TrueColor 16 0 y . y xchg . 5 6 5 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 295 0 15c TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 296 0 15d TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 297 0 15e TrueColor 16 0 y . y copy . 5 6 5 0 0 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 298 0 15f TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 299 0 160 TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 300 0 161 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 301 0 162 TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 302 0 163 TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 303 0 164 TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 8 . . y . . 2 [ 18195.114] 304 0 165 TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 305 0 166 TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 306 0 167 TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 307 0 168 TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 308 0 169 TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 309 0 16a TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 310 0 16b TrueColor 16 0 y . . . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 311 0 16c TrueColor 16 0 y . . . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 312 0 16d TrueColor 16 0 y . y xchg . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 313 0 16e TrueColor 16 0 y . y xchg . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 314 0 16f TrueColor 16 0 y . y copy . 5 6 5 0 24 0 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 315 0 170 TrueColor 16 0 y . y copy . 5 6 5 0 24 8 4 16 16 16 16 1 16 . . y . . 2 [ 18195.114] 316 0 171 TrueColor 0 0 y . . . 0 0 0 0 24 0 0 0 0 0 0 0 0 . . y . . 2 [ 18195.114] 317 0 172 TrueColor 0 0 y . . . 0 0 0 0 24 8 0 0 0 0 0 0 0 . . y . . 2 [ 18195.114] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 18195.129] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [ 18195.894] winPointerWarpCursor - Discarding first warp: 720 450 [ 18195.894] (--) 2 mouse buttons found [ 18195.894] (--) Setting autorepeat to delay=500, rate=31 [ 18195.894] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [ 18195.894] (--) Found matching XKB configuration "English (USA)" [ 18195.894] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 18195.894] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 18195.894] winBlockHandler - pthread_mutex_unlock() [ 18195.894] winInitMultiWindowWM - pthread_mutex_lock () returned. [ 18195.909] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [ 18195.909] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [ 18195.909] winMultiWindowXMsgProc - DISPLAY=:0.0 [ 18195.909] winInitMultiWindowWM - pthread_mutex_unlock () returned. [ 18195.909] winProcEstablishConnection - winInitClipboard returned. [ 18195.909] winInitMultiWindowWM - DISPLAY=:0.0 [ 18195.909] winClipboardProc - DISPLAY=:0.0 [ 18195.909] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 18195.909] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [ 18195.909] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 18298.886] Segmentation fault at address 0x44 [ 18298.886] Fatal server error: [ 18298.886] Caught signal 11 (Segmentation fault). Server aborting [ 18298.886] [ 18298.886] Server terminated with error (1). Closing log file. -------------- next part -------------- GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-cygwin". For bug reporting instructions, please see: . Attaching to process 2640 [New Thread 2640.0x8f4] [New Thread 2640.0x17f0] [New Thread 2640.0x1330] [New Thread 2640.0x510] [New Thread 2640.0x1620] [New Thread 2640.0x1590] [New Thread 2640.0xeec] [New Thread 2640.0x26c] [New Thread 2640.0x17e8] [New Thread 2640.0xcf4] [New Thread 2640.0x798] [New Thread 2640.0xe90] [New Thread 2640.0x11fc] [New Thread 2640.0xf5c] Reading symbols from /usr/bin/XWin.exe...Reading symbols from /usr/lib/debug/usr/bin/XWin.dbg... warning: section .gnu_debuglink not found in /usr/lib/debug/usr/bin/XWin.dbg done. done. [?1034h(gdb) c Continuing. [New Thread 2640.0x168] [New Thread 2640.0xac] [New Thread 2640.0x12c8] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 2640.0x1620] 0x0040a41e in winXIconToHICON (pDisplay=0x202f3ed8, id=2097153, iconSize=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 535 /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c: No such file or directory. in /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c (gdb) bt full #0 0x0040a41e in winXIconToHICON (pDisplay=0x202f3ed8, id=2097153, iconSize=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 root = 1987733555 y = 2145373224 depth = 2145373168 xImageIcon = 0x0 x = 1987733604 width = 1024 height = 0 border_width = 1987759504 xImageMask = 0x0 mask = image = imageMask = dst = src = planes = 1 bpp = 32 i = biggest_size = hDC = ii = {fIcon = 2145373152, xHotspot = 1987733433, yHotspot = 11, hbmMask = 0xb, hbmColor = 0x200001} hints = 0x203aff40 hIcon = 0x0 biggest_icon = _XA_NET_WM_ICON = 238 generation = 1 icon = icon_data = 0x0 size = 0 type = 0 format = 0 left = 0 #1 0x0040a6ab in winUpdateIcon (hWnd=0x1004e0, pDisplay=0x202f3ed8, id=2097153, hIconNew=0x0) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:560 hIcon = hIconSmall = 0x0 hIconOld = #2 0x0041f5e7 in UpdateIcon (iWindow=2097153, pWMInfo=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowwm.c:667 hWnd = 0x1004e0 hIconNew = attr = {x = 310, y = 96, width = 819, height = 707, border_width = 0, depth = 24, visual = 0x2033fb40, root = 468, class = 1, bit_gravity = 0, win_gravity = 1, backing_store = 0, backing_planes = 4294967295, backing_pixel = 0, save_under = 0, colormap = 32, map_installed = 1, map_state = 2, all_event_masks = 4358144, your_event_mask = 0, do_not_propagate_mask = 8205, override_redirect = 0, screen = 0x2033fa90} #3 0x004210d0 in winMultiWindowWMProc (pArg=0x20046fa0) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowwm.c:836 pNode = 0x202e54f8 __cleanup_handler = {function = 0x41eeb0 , arg = 0x0, next = 0x0} pProcArg = 0x20046fa0 pWMInfo = 0x20046fb0 #4 0x610fc052 in pthread::thread_init_wrapper(void*) () from /usr/bin/cygwin1.dll No symbol table info available. #5 0x61086bf2 in thread_wrapper(void*) () from /usr/bin/cygwin1.dll No symbol table info available. Backtrace stopped: Not enough registers or memory available to unwind further (gdb) quit A debugging session is active. Inferior 1 [process 2640] will be detached. Quit anyway? (y or n) Detaching from program: /usr/bin/XWin.exe, Pid 2640 -------------- next part -------------- -- 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 yselkowitz@users.sourceforge.net Wed Apr 25 21:06:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 25 Apr 2012 21:06:00 -0000 Subject: startx with different displays In-Reply-To: <33745960.post@talk.nabble.com> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> <4F96E3BC.4050800@cygwin.com> <33741843.post@talk.nabble.com> <4F971F46.5090308@cygwin.com> <33745960.post@talk.nabble.com> Message-ID: <4F98673E.40207@users.sourceforge.net> On 2012-04-25 06:50, Marc Girod wrote: > Back to my original problem... > I tried startxwin (as suggested by a colleague) and this one accepts to > start XWin on DISPLAY :0 > Are all my problems related to startx? > I can see that defaulting to the highest display found in /tmp/.X* seems to > comes from it... > Does anybody use startx with success? Of course. Yaakov Cygwin/X -- 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 marc.girod@gmail.com Wed Apr 25 21:27:00 2012 From: marc.girod@gmail.com (Marc Girod) Date: Wed, 25 Apr 2012 21:27:00 -0000 Subject: startx with different displays In-Reply-To: <4F98673E.40207@users.sourceforge.net> References: <33702991.post@talk.nabble.com> <33732045.post@talk.nabble.com> <33732071.post@talk.nabble.com> <4F956D3E.5000408@cygwin.com> <33737835.post@talk.nabble.com> <4F96E3BC.4050800@cygwin.com> <33741843.post@talk.nabble.com> <4F971F46.5090308@cygwin.com> <33745960.post@talk.nabble.com> <4F98673E.40207@users.sourceforge.net> Message-ID: <33749731.post@talk.nabble.com> Yaakov (Cygwin/X) wrote: > > Of course. > Thanks. Sorry, this was a stupid question: even I use it on my other laptop, without problem. OK: with the two glitches I described. Marc -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33749731.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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 klindsay@ucar.edu Wed Apr 25 21:45:00 2012 From: klindsay@ucar.edu (Keith Lindsay) Date: Wed, 25 Apr 2012 21:45:00 -0000 Subject: X segmentation fault when particular application attempts to open a window In-Reply-To: <4F985C8A.6020209@ucar.edu> References: <4F985C8A.6020209@ucar.edu> Message-ID: <4F98705E.6010204@ucar.edu> On 4/25/2012 2:20 PM, Keith Lindsay wrote: > Hi, > > I'm running a data analysis program called ferret on a remote machine > that I've logged on to with "ssh -X". When the program attempts to > create a window, the Cygwin/X server crashes with a segmentation fault. > The seg fault is reproducible. > > xclock works fine from the same remote machine. > > This is with version 1.12.0-4 of xorg-server. > > ferret has worked with some previous versions of the Cygwin/X server, > but I'm not certain about the precise version where the breakage > occurred. I backed up one version and encountered the same problem. > > I've attached the output of "cygcheck -c", the file > /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to > the XWin process when it crashes. > > I'm at a loss about how to proceed further. > I welcome any advice that you can provide. > > Thank you, > Keith Lindsay Hi again, I realized that I can back up to other versions of xorg-server by installing from the local directory that contains previous version downloads. I have discovered that ferret works fine with version 1.12.0-1 of xorg-server (built 2012-03-12) and generates the segmentation violation with version 1.12.0-2 (built 2012-04-04). Keith -- 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 26 13:18:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 13:18:00 -0000 Subject: Fatal Error (Segmentation Fault) only while viewing the LVM GUI In-Reply-To: References: Message-ID: <4F994B13.7020101@dronecode.org.uk> On 25/04/2012 19:25, Carlo.DiCocco wrote: > I think I may have found a bug. I am connecting to a remote Linux server > from my Windows desktop and attempting to use some of the GUI tools on the > remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI > displays fine. The LVM "system-config-lvm" GUI displays and works fine, > but cygwin generates a fatal error window due to a segmentation fault. > The following command displays the GUI, but reports a fatal error: > > [root@aorahdev ~]# system-config-lvm > [ 64144.546] Segmentation fault at address 0x44 > [ 64144.546] Fatal server error: > [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting > [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. -- 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 Thu Apr 26 13:22:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 13:22:00 -0000 Subject: XWin 1.12.0-4 crash In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> Message-ID: <4F994C0A.2050806@dronecode.org.uk> On 23/04/2012 14:03, Michel Bardiaux wrote: > Yes, it is a crash at startup. > > I could not find XWin.exe.stackdump anywhere on my hard drive. I have > attached the bat script (renamed into .txt) used to start cygwin/X, > maybe I need to modify it. > > Would it work to add > > CYGWIN='error_start=c:\cygwin\bin\dumper.exe' > > in the system environment (meaning, via the control panel), to have a > core file that I could then open with gdb? No, I don't think that would work (for various uninteresting reasons) Start the X server from a terminal using 'gdb --args XWin -multiwindow', type 'r' to start the X server running, and 'bt full' after it crashes. -- 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 Thu Apr 26 13:23:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 13:23:00 -0000 Subject: Fatal Error (Segmentation Fault) only while viewing the LVM GUI In-Reply-To: <4F994B13.7020101@dronecode.org.uk> References: <4F994B13.7020101@dronecode.org.uk> Message-ID: <4F994C66.4090808@dronecode.org.uk> On 26/04/2012 14:18, Jon TURNEY wrote: > On 25/04/2012 19:25, Carlo.DiCocco wrote: >> I think I may have found a bug. I am connecting to a remote Linux server >> from my Windows desktop and attempting to use some of the GUI tools on the >> remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI >> displays fine. The LVM "system-config-lvm" GUI displays and works fine, >> but cygwin generates a fatal error window due to a segmentation fault. > >> The following command displays the GUI, but reports a fatal error: >> >> [root@aorahdev ~]# system-config-lvm > >> [ 64144.546] Segmentation fault at address 0x44 >> [ 64144.546] Fatal server error: >> [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting >> [ 64144.546] Server terminated with error (1). Closing log file. > > Thanks for reporting this problem. > > I was not able to reproduce this crash using system-config-lvm 1.1.16, on > Fedora 15. Perhaps you can provide details on the remote server and > system-config-lvm version you are using? > > It would be very helpful if you could follow the instructions at [1] to use > gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.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 MBardiaux@mediaxim.be Thu Apr 26 14:54:00 2012 From: MBardiaux@mediaxim.be (Michel Bardiaux) Date: Thu, 26 Apr 2012 14:54:00 -0000 Subject: XWin 1.12.0-4 crash In-Reply-To: <4F994C0A.2050806@dronecode.org.uk> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> <4F994C0A.2050806@dronecode.org.uk> Message-ID: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D274@bespdc01.mediaxim.local> > From: Jon TURNEY > Start the X server from a terminal using 'gdb --args XWin -multiwindow', type 'r' to start the X > server running, Did exactly that in a minty. Then in another one: export DISPLAY=localhost:0.0 ssh -X -Y michel@besdev01 multi-gnome-terminal > and 'bt full' after it crashes. Which gives: winProcEstablishConnection - winInitClipboard returned. winClipboardProc - DISPLAY=:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. [New Thread 1452.0x350] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [New Thread 1452.0xcf0] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1452.0xf04] 0x0040a41e in winXIconToHICON () (gdb) bt full #0 0x0040a41e in winXIconToHICON () No symbol table info available. #1 0x0040a6ab in winUpdateIcon () No symbol table info available. #2 0x0041f5e7 in UpdateIcon.clone.3 () No symbol table info available. #3 0x004210d0 in winMultiWindowWMProc () No symbol table info available. #4 0x610fbd52 in pthread::thread_init_wrapper(void*) () from /cygdrive/c/cygwin/bin/cygwin1.dll No symbol table info available. #5 0x610868f2 in thread_wrapper(void*) () from /cygdrive/c/cygwin/bin/cygwin1.dll No symbol table info available. Backtrace stopped: Not enough registers or memory available to unwind further Note that if I invoke xclock instead of multi-gnome-terminal, it works. Ditto xterm, emacs, and fortunately all my personal apps! Greetings, (s) M. Bardiaux -- 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 tamura@hpc-sol.co.jp Thu Apr 26 15:40:00 2012 From: tamura@hpc-sol.co.jp (Yusuke Tamura) Date: Thu, 26 Apr 2012 15:40:00 -0000 Subject: xlogo crahes XWin with Fatal Error (Segmentation Fault) Message-ID: <2FCD23C2DF2F22tamura@hpc-sol.co.jp> Dear sirs, Some days ago I updated the cygwin system by 'setup.exe', expecting some "GL" problems are fixed. Since then XWin crashes with some application programs. One of the most simplest is 'xlogo'. What I have done is as follows; Start [XWin Server] (wait some time for bringing up xterm), then enter 'xlogo' in xterm, [Cygwin/X] window appears immediately. It says, > A fatal error ... > > Caught signal 11 (Segmentation fault). ... > > Please open /var/log/xwin/XWin.0.log ... > > Vendor: .. > Release: 1.12.0.0 > Contact: .. > Package: version 1.12.0-4 built 2012-04-17 > > XWin was started ... > > X :0 -multiwindow /var/log/xwin/XWin.0.log does not report anything important at all. OK, I tried 'X :0 -multiwindow' on one terminal, and on the other terminal $ export DISPLAY=:0.0 $ xlogo then, the message appears on one therminal; >Segmentation fault at address 0x44 > >Fatal server error: >Caught signal 11 (Segmentation fault). Server aborting > >Server terminated with error (1). Closing log file. >winDeinitMultiWindowWM - Noting shutdown in progress >winMsgWindowProc - pthread_mutex_unlock () failed: 1 while entering 'X :0' on one terminal, entring 'xlogo' on the other, there was no fatal problem. Obviously '-multiwindow' does something wrong. Keith Lindsay's post might be helpfull as workaround, but I cannot rollback to the 'version 1.12.0-1 of xorg-server (built 2012-03-12)' using 'setup.exe', April 25, 2012 21:45 Re: X segmentation fault when particular application attempts to open a window http://cygwin.com/ml/cygwin-xfree/2012-04/msg00100.html best regards, Yusuke Tamura --- -- 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 26 18:15:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 18:15:00 -0000 Subject: X segmentation fault when particular application attempts to open a window In-Reply-To: <4F98705E.6010204@ucar.edu> References: <4F985C8A.6020209@ucar.edu> <4F98705E.6010204@ucar.edu> Message-ID: <4F9990D0.9040103@dronecode.org.uk> On 25/04/2012 22:45, Keith Lindsay wrote: > On 4/25/2012 2:20 PM, Keith Lindsay wrote: >> I'm running a data analysis program called ferret on a remote machine >> that I've logged on to with "ssh -X". When the program attempts to >> create a window, the Cygwin/X server crashes with a segmentation fault. >> The seg fault is reproducible. >> >> xclock works fine from the same remote machine. >> >> This is with version 1.12.0-4 of xorg-server. >> >> ferret has worked with some previous versions of the Cygwin/X server, >> but I'm not certain about the precise version where the breakage >> occurred. I backed up one version and encountered the same problem. >> >> I've attached the output of "cygcheck -c", the file >> /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to >> the XWin process when it crashes. > > I realized that I can back up to other versions of xorg-server by installing > from the local directory that contains previous version downloads. I have > discovered that ferret works fine with version 1.12.0-1 of xorg-server (built > 2012-03-12) and generates the segmentation violation with version 1.12.0-2 > (built 2012-04-04). Thanks for the excellent bug report. I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. This crash was caused by the server being unable to find the bitmap which the application wants to use for it's icon, it's not clear why this is happening, so I would be interested to know if the application icon is correct or not. -- 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 Thu Apr 26 18:20:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 18:20:00 -0000 Subject: XWin 1.12.0-4 crash In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D274@bespdc01.mediaxim.local> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> <4F994C0A.2050806@dronecode.org.uk> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D274@bespdc01.mediaxim.local> Message-ID: <4F9991C8.3080907@dronecode.org.uk> On 23/04/2012 12:55, Michel Bardiaux wrote: > Nothing much to add to the 2 attached files - except that my X worked > fine until the last update. Will try reverting to previous version. Mentioning the name of the application which caused the crash (multi-gnome-terminal) would have helped. On 23/04/2012 14:03, Michel Bardiaux wrote: > Yes, it is a crash at startup. So, in fact, it's not a crash when the X server is started, but when you try to run the application multi-gnome-terminal? On 26/04/2012 15:54, Michel Bardiaux wrote: >> Start the X server from a terminal using 'gdb --args XWin > -multiwindow', type 'r' to start the X >> server running, > > Did exactly that in a minty. Then in another one: > > export DISPLAY=localhost:0.0 > ssh -X -Y michel@besdev01 multi-gnome-terminal It looks like this is the same crash as reported at [1], and should be fixed in X server 1.12.0-5. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.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 Thu Apr 26 18:21:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 18:21:00 -0000 Subject: Fatal Error (Segmentation Fault) only while viewing the LVM GUI In-Reply-To: <4F994C66.4090808@dronecode.org.uk> References: <4F994B13.7020101@dronecode.org.uk> <4F994C66.4090808@dronecode.org.uk> Message-ID: <4F99922B.1040301@dronecode.org.uk> On 26/04/2012 14:23, Jon TURNEY wrote: > On 26/04/2012 14:18, Jon TURNEY wrote: >> On 25/04/2012 19:25, Carlo.DiCocco wrote: >>> I think I may have found a bug. I am connecting to a remote Linux server >>> from my Windows desktop and attempting to use some of the GUI tools on the >>> remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI >>> displays fine. The LVM "system-config-lvm" GUI displays and works fine, >>> but cygwin generates a fatal error window due to a segmentation fault. >> >>> The following command displays the GUI, but reports a fatal error: >>> >>> [root@aorahdev ~]# system-config-lvm >> >>> [ 64144.546] Segmentation fault at address 0x44 >>> [ 64144.546] Fatal server error: >>> [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting >>> [ 64144.546] Server terminated with error (1). Closing log file. >> >> Thanks for reporting this problem. >> >> I was not able to reproduce this crash using system-config-lvm 1.1.16, on >> Fedora 15. Perhaps you can provide details on the remote server and >> system-config-lvm version you are using? >> >> It would be very helpful if you could follow the instructions at [1] to use >> gdb to get a backtrace for the X server when it crashes. > > Oops > > [1] http://x.cygwin.com/devel/backtrace.html It seems quite likely this is the same crash as reported at [1], so it's probably worth testing X server 1.12.0-5 to see if it's fixed there, first. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.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 Thu Apr 26 18:28:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 26 Apr 2012 18:28:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-5 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-5 *** xorg-server-common-1.12.0-5 *** xorg-server-dmx-1.12.0-5 *** xorg-server-extra-1.12.0-5 *** xorg-server-devel-1.12.0-5 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.12.0-4: * Fix a crash which could occur in WM_HINTS bitmap icon conversion (Reported by Keith Lindsay, Yusuke Tamura and others) * stdout and stderr for processes started from the notification area icon are now written to the X server log * Remove the llvmpipe/softpipe testing facility using the GALLIUM_DRIVER environment variable 696546cad78a343467ddf4dafbdb8ebb *xorg-server-1.12.0-5.tar.bz2 a4e2688aac776d4857b585af1c30e3bd *xorg-server-common-1.12.0-5.tar.bz2 96e6cd66404a1a3f0f12fe7a5663ae48 *xorg-server-devel-1.12.0-5.tar.bz2 aa008cd283e392eb50f5a33d706fb249 *xorg-server-dmx-1.12.0-5.tar.bz2 b54a699855c844dd536e848195c50a61 *xorg-server-extra-1.12.0-5.tar.bz2 2ffceecd814981724ce6ec6470ea9da9 *xorg-server-1.12.0-5-src.tar.bz2 -- 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 gbarrick@walsh.edu Thu Apr 26 18:45:00 2012 From: gbarrick@walsh.edu (George Barrick) Date: Thu, 26 Apr 2012 18:45:00 -0000 Subject: xlogo crashes XWin with Fatal Error (Segmentation Fault) Message-ID: <4B30AD0BED19E842AAE88DC3973649314FA7C57898@mail3.walsh.edu> Re: xlogo crashes XWin with Fatal Error (Segmentation Fault) 2012.04.26.18:13:33 UT Hey cygwin-x folks, I have not had notable difficulties with XWin-1.12.0-4. Just about everything that I have done with it over the past few days has been fine. However, when I read Yusuke's post, I thought that I should try one of those old-timey X-programs to see whether it would crash. I've been able to reproduce an XWin crash similar to the one experienced by Yusuke. My XWin did _not_ fail when I was running octave with either the fltk or its usual gnuplot backends. I was also able to run xfig with no problem. This was a crash caused when I opened the xcalc program. I'm not certain that I understand his experiment with two terminal windows as a method of narrowing the difficulty to the -multiwindow option. However like Yusuke, I am starting XWin with the -mulitwindow option. The crash I observed was with just a single xterm, and then the xcalc program. Other programs that opened x-windows seemed fine. In this instance, I had the debugging symbols available, and collected information from a backtrace using (gdb). I've attached gdb.xwin.20120426.txt and my XWin.0.20120426.log. I did not see anything interesting in the xwin0-log, and my (gdb) backtrace is just the output from my glance at Jon Turney's recipe. I'm tossing it in this list in case it helps better-informed folks to track down the difficulty with XWin-1.12.0-4. If there is more specific or nuanced stuff that I can log with (gdb) to provide more information, please e-mail me. George gbarrick_at_walsh_dot_edu -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdb.xwin.20120426.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.20120426.log Type: application/octet-stream Size: 10951 bytes Desc: XWin.0.20120426.log URL: -------------- next part -------------- -- 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 klindsay@ucar.edu Thu Apr 26 20:22:00 2012 From: klindsay@ucar.edu (Keith Lindsay) Date: Thu, 26 Apr 2012 20:22:00 -0000 Subject: X segmentation fault when particular application attempts to open a window In-Reply-To: <4F9990D0.9040103@dronecode.org.uk> References: <4F985C8A.6020209@ucar.edu> <4F98705E.6010204@ucar.edu> <4F9990D0.9040103@dronecode.org.uk> Message-ID: <4F99AE64.3080207@ucar.edu> On 04/26/2012 12:15 PM, Jon TURNEY wrote: > Thanks for the excellent bug report. You're welcome. Thank you for the prompt response. > I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. Good news, ferret works fine with 1.12.0-5. > This crash was caused by the server being unable to find the bitmap which the > application wants to use for it's icon, it's not clear why this is happening, > so I would be interested to know if the application icon is correct or not. The icon that appears on the taskbar when I open a ferret window is a generic Xorg icon. I'm not certain if there is an actual icon for ferret that should be appearing. I get a similar generic icon when the X server displaying the window is being run on Linux, so this behavoir is not unique to Cygwin. So it seems like a feature of the application, or the installation of the application. The application works otherwise. Thanks again for the prompt response and fix, Keith -- 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 tamura@hpc-sol.co.jp Fri Apr 27 00:39:00 2012 From: tamura@hpc-sol.co.jp (Yusuke Tamura) Date: Fri, 27 Apr 2012 00:39:00 -0000 Subject: X segmentation fault when particular application attempts to open a window In-Reply-To: <4F9990D0.9040103@dronecode.org.uk> References: <4F985C8A.6020209@ucar.edu> <4F98705E.6010204@ucar.edu> <4F9990D0.9040103@dronecode.org.uk> Message-ID: <30CD240E1F5702tamura@hpc-sol.co.jp> Jon, thank you for the update! XWin is working as before. I appreciate your prompt action very much. Yusuke >On 25/04/2012 22:45, Keith Lindsay wrote: >> On 4/25/2012 2:20 PM, Keith Lindsay wrote: >>> I'm running a data analysis program called ferret on a remote machine >>> that I've logged on to with "ssh -X". When the program attempts to >>> create a window, the Cygwin/X server crashes with a segmentation fault. >>> The seg fault is reproducible. >>> >>> xclock works fine from the same remote machine. >>> >>> This is with version 1.12.0-4 of xorg-server. >>> >>> ferret has worked with some previous versions of the Cygwin/X server, >>> but I'm not certain about the precise version where the breakage >>> occurred. I backed up one version and encountered the same problem. >>> >>> I've attached the output of "cygcheck -c", the file >>> /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to >>> the XWin process when it crashes. >> >> I realized that I can back up to other versions of xorg-server by >> installing >> from the local directory that contains previous version downloads. I have >> discovered that ferret works fine with version 1.12.0-1 of xorg-server >> (built >> 2012-03-12) and generates the segmentation violation with version 1.12.0-2 >> (built 2012-04-04). > >Thanks for the excellent bug report. > >I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. > >This crash was caused by the server being unable to find the bitmap which the >application wants to use for it's icon, it's not clear why this is happening, >so I would be interested to know if the application icon is correct or not. > >-- >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 MBardiaux@mediaxim.be Fri Apr 27 09:00:00 2012 From: MBardiaux@mediaxim.be (Michel Bardiaux) Date: Fri, 27 Apr 2012 09:00:00 -0000 Subject: XWin 1.12.0-4 crash In-Reply-To: <4F9991C8.3080907@dronecode.org.uk> References: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local> <4F994C0A.2050806@dronecode.org.uk> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D274@bespdc01.mediaxim.local> <4F9991C8.3080907@dronecode.org.uk> Message-ID: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D2B8@bespdc01.mediaxim.local> > From: Jon TURNEY > Mentioning the name of the application which caused the crash > (multi-gnome-terminal) would have helped. Sorry, I thought it was clear from the startup script that I had attached. > So, in fact, it's not a crash when the X server is started, but when you try to run the application > multi-gnome-terminal? Yes. But because the MGT was started just after X in my startup script, it looked like a startup issue. When I removed the MGT from the script, I was able to run the apps I needed, using a local mintty+ssh. > It looks like this is the same crash as reported at [1], and should be fixed in X server 1.12.0-5. It is indeed. Thanks for the quick support. Greetings, (s) M. Bardiaux. -- 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 Carlo.DiCocco@dfs.ny.gov Fri Apr 27 12:38:00 2012 From: Carlo.DiCocco@dfs.ny.gov (Carlo.DiCocco@dfs.ny.gov) Date: Fri, 27 Apr 2012 12:38:00 -0000 Subject: Fatal Error (Segmentation Fault) only while viewing the LVM GUI Message-ID: Thank you for your prompt response. I was out yesterday, so I didn't get your email until now. I did an update and the issue no longer exists. Thanks, Carlo L. DiCocco -- 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 patrick.hogan@gmail.com Mon Apr 30 08:53:00 2012 From: patrick.hogan@gmail.com (Patrick Hogan) Date: Mon, 30 Apr 2012 08:53:00 -0000 Subject: startx - no keyboard or mouse focus with single xterm, repeatable error Message-ID: I've observed a problem whereby a single-screen X11 session started with startx or Xwin prevents a single xterm from being started in a usable state (no keyboard or mouse focus), but the problem goes away if the xterm is placed in a *particular area on the screen*. It's a new fresh Cygwin install. Here's the command I'm using: startx /usr/bin/xterm This opens a single-window X11 server populated with one xterm. Within the X11 server window, the cursor is not visible and neither mouse focus or keyboard focus is available. Even with twm running, the situation is the same: startx /usr/bin/xterm -e twm Tested on: Windows XP SP3 32-bit (running under VirtualBox on a Linux host, 1024x768 resolution, 32bpp and 16bpp) Windows Server 2008 R2 64-bit (running under VMware ESX 3.x via an RDP remote desktop session, 1132x778 resolution, 16bpp). Here is the strange thing. On both installations I can get everything working fine by running the xterm like this: startx /usr/bin/xterm -g 40x40-xxx+51 with "xxx" set to 257 or more, up to an upper bound of 508, after which it stops working again. This range seems to depend on the horizontal resolution of the X11 server window, the example above using 1024x768 32bpp, and basic testing seems to suggest that "xxx" needs to be just over 25% of the horizontal resolution. The vertical resolution of the X11 server window doesn't seem to have a bearing on the issue. So - it seems that the problem can be side-stepped by popping up an xterm in the area of the screen just beyond the 25% mark on the horizontal access, and then immediately closing it again, after which everything is fine. The fact that it's such a repeatable error is interesting! Any insights appreciated. Regards, Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 3450 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 21308 bytes Desc: not available URL: -------------- next part -------------- -- 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 patrick.hogan@gmail.com Mon Apr 30 10:27:00 2012 From: patrick.hogan@gmail.com (Patrick Hogan) Date: Mon, 30 Apr 2012 10:27:00 -0000 Subject: Updated: startx - no keyboard or mouse focus with single xterm, repeatable error Message-ID: In my previous email, I mis-typed the xterm geometry which might have caused confusion. There was a minus where there should have been a plus. Corrected version below. -------- I've observed a problem whereby a single-screen X11 session started with startx or Xwin prevents a single xterm from being started in a usable state (no keyboard or mouse focus), but the problem goes away if the xterm is placed in a *particular area on the screen*. It's a new fresh Cygwin install. Here's the command I'm using: startx /usr/bin/xterm This opens a single-window X11 server populated with one xterm. Within the X11 server window, the cursor is not visible and neither mouse focus or keyboard focus is available. Even with twm running, the situation is the same: startx /usr/bin/xterm -e twm Tested on: Windows XP SP3 32-bit (running under VirtualBox on a Linux host, 1024x768 resolution, 32bpp and 16bpp) Windows Server 2008 R2 64-bit (running under VMware ESX 3.x via an RDP remote desktop session, 1132x778 resolution, 16bpp). Here is the strange thing. On both installations I can get everything working fine by running the xterm like this: startx /usr/bin/xterm -g 40x40+xxx+51 with "xxx" set to 257 or more, up to an upper bound of 508, after which it stops working again. This range seems to depend on the horizontal resolution of the X11 server window, the example above using 1024x768 32bpp, and basic testing seems to suggest that "xxx" needs to be just over 25% of the horizontal resolution. The vertical resolution of the X11 server window doesn't seem to have a bearing on the issue. So - it seems that the problem can be side-stepped by popping up an xterm in the area of the screen just beyond the 25% mark on the horizontal access, and then immediately closing it again, after which everything is fine. The fact that it's such a repeatable error is interesting! Any insights appreciated. Regards, Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 3450 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 21308 bytes Desc: not available URL: -------------- next part -------------- -- 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 kantacki@o2.pl Mon Apr 30 14:44:00 2012 From: kantacki@o2.pl (Kantacki) Date: Mon, 30 Apr 2012 14:44:00 -0000 Subject: libqt3-devel uic.exe segmentation fault Message-ID: <4F9EA548.5070000@o2.pl> Hello, I have problems with uic.exe compiler which is included to libqt3-devel package. When I run it with or without parameters I always get segmentation fault message. Could anyone of you confirm that the problem exist and has to be repaired or with my Cygwin installation is something wrong, by the way I already tried to reinstall libqt3 and libqt3-devel from many different sources and I always get the same error message. Best regards. Kantacki -- 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/