From yselkowitz@users.sourceforge.net Sun Feb 2 02:42:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Sun, 02 Feb 2014 02:42:00 -0000 Subject: Advice on getting window manager, file manager and simple text editor to work In-Reply-To: References: Message-ID: <52EDB07A.3070008@users.sourceforge.net> http://cygwin.com/acronyms/#PCYMTWLL ! On 2014-01-31 16:41, Sinkler, Wharton wrote: > I'm trying to recreate the look and feel of a standard Unix X Windows system > on my PC using Cygwin (something resembling the old CDE, or Redhat in functionality). > > I've got Cygwin with X11 and openbox running, but a few problems stubbornly > unresolved: > > Openbox doesn't have a dock so if you minimize a window it's just gone. Openbox is only a window manager, so that is to be expected. > There are suggestions to solve this problem with a toolbar application called > tint2, however the latter doesn't build successfully on my Cygwin installation > (Errors in cmake about compilers not working when in fact they are working just > fine). As far as standalone panels go, tint2 is available in Ports (built OOTB), as is fbpanel (my personal favourite). > Another major item is some kind of file manager to run inside the Openbox root > window. Although I've installed the KDE and Gnome items available through cygwin > setup-x86_64.exe, none of the file managers such as Nautilus, Thunar, KDE file > manager etc. appear to be part of those installations. dolphin, gentoo (the file manager, not the Linux distro), gnome-commander, mate-file-manager (aka Caja), nautilus, pcmanfm, Thunar, and xfe are all available in Ports. > I tried downloading a version of rox (rox-2.1.2-cygwin.tar.bz2) but installation > failed (gcc apparently detects multiple incompatible declarations in part of the > code). Like most X11 desktops, a fairly complete ROX environment is also available in Ports. > Finally, I'd like a simple editor. Have installed nedit, but get 'UTF8 locale not > supported' followed by Segmentation fault when I execute it. The message is harmless but otherwise it WFM. 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 doran.kangwai@gmail.com Tue Feb 18 07:56:00 2014 From: doran.kangwai@gmail.com (Doran Kangwai) Date: Tue, 18 Feb 2014 07:56:00 -0000 Subject: Problem with xman-1.1.3-1 Message-ID: Hi, When I use xman 1.1.3-1 to view man pages it renders the pages as postscript. It seems to omit the step to process the PS. So I see stuff like this %!PS-Adobe-3.0 %%Creator: groff version 1.22.2 ... ... Using man to display the page works fine. When I use xman 1.1.2-1 the man page is also rendered correctly. Steps to repro 1)Install cygwin using setup-x86.exe (version 2.831). I choose all of Base (Default) and from X11 xinit xman xorg-server xorg-server-common xterm X-start-menu-icons 2) Start->Cygwin-X->XWin Server 3) From xterm type xman -notopbox 4) Confirm xman version using Options->Show Version 5) Display man page for cat by Options->Display Directory and selecting cat 6) You should see postscript displayed for xman 1.1.3-1 I downloaded xman-1.2.2-1.tar.bz2 and using xman.exe from there I confirmed that I can successfully see man pages. cygcheck.out and XWin.0.log attached. Note that files contain XXREDACTEDXX where information was redacted. -- Doran Kangwai -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 23866 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 5357 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 jon.turney@dronecode.org.uk Wed Feb 19 15:02:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 19 Feb 2014 15:02:00 -0000 Subject: Problem with xman-1.1.3-1 In-Reply-To: References: Message-ID: <5304C798.4090300@dronecode.org.uk> On 18/02/2014 07:56, Doran Kangwai wrote: > When I use xman 1.1.3-1 to view man pages it renders the pages as > postscript. It seems to omit the step to process the PS. Close, but not quite right. groff is not being given the -T option to set the output format, so it's producing the default, ps > So I see stuff like this > %!PS-Adobe-3.0 > %%Creator: groff version 1.22.2 > ... > ... > > Using man to display the page works fine. > > When I use xman 1.1.2-1 the man page is also rendered correctly. Thanks for reporting this problem, and the clear reproduction steps. I can reproduce the problem, and bisecting points to this commit [1], which changes the formatting command used by xman. Yaakov, Attached is trivial patch to fix. If it looks good to you can you apply and rebuild xman? [1] http://cgit.freedesktop.org/xorg/app/xman/commit/?id=d25a3b87ce9fdf950b42f45b644242d72e7167b3 -------------- next part -------------- >From ea0ecbfa007e03e29f80f976472a28e37cf59931 Mon Sep 17 00:00:00 2001 From: Jon TURNEY Date: Wed, 19 Feb 2014 14:51:34 +0000 Subject: [PATCH app/xman] Use same FORMAT command on cygwin as on linux in HANDLE_ROFFSEQ case as well Signed-off-by: Jon TURNEY --- vendor.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vendor.h b/vendor.h index 548ded6..06df38f 100644 --- a/vendor.h +++ b/vendor.h @@ -159,7 +159,7 @@ from the X Consortium. # define REFER "refer" # if defined(CSRG_BASED) # define FORMAT "nroff -mandoc" -# elif defined(linux) +# elif defined(linux) || defined(__CYGWIN__) # define FORMAT "GROFF_NO_SGR= groff -Tlatin1 -mandoc" # elif defined(__DARWIN__) # define FORMAT "nroff -man" -- 1.8.3.4 -------------- 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 Feb 19 18:02:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 19 Feb 2014 18:02:00 -0000 Subject: [ANNOUNCEMENT] Updated: xman-1.1.3-2 In-Reply-To: <5304C798.4090300@dronecode.org.uk> References: <5304C798.4090300@dronecode.org.uk> Message-ID: The following packages have been updated in the Cygwin distribution: *** xman-1.1.3-2 Xman is a graphical man page browser. This release includes a patch from Jon TURNEY to fix groff formatting (again). A desktop menu entry has been added. 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 yselkowitz@users.sourceforge.net Wed Feb 19 18:02:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 19 Feb 2014 18:02:00 -0000 Subject: [ANNOUNCEMENT] Updated: xterm-301-1 Message-ID: The following package has been updated in the Cygwin distribution: *** xterm-301-1 The xterm program is a terminal emulator for the X Window System. It provides DEC VT102 and Tektronix 4014 compatible terminals for programs that can't use the window system directly. This is an update to the latest upstream release. -- 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 ola.stromfors@gmail.com Thu Feb 20 17:47:00 2014 From: ola.stromfors@gmail.com (=?ISO-8859-1?Q?Ola_Str=F6mfors?=) Date: Thu, 20 Feb 2014 17:47:00 -0000 Subject: Problem with xterm-301-1 Message-ID: <53063FA4.5020806@gmail.com> Hi, After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. /bin/ash /bin/bash /bin/dash /bin/sh /bin/tcsh /bin/zsh Regards, Ola Str??mfors -- 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 Thu Feb 20 18:33:00 2014 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 20 Feb 2014 18:33:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: <53063FA4.5020806@gmail.com> References: <53063FA4.5020806@gmail.com> Message-ID: On Thu, Feb 20, 2014 at 10:47 AM, Ola Str?mfors wrote: > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > my shell specified in /etc/passwd or in the SHELL environment variable. I saw the same thing, but only on my home computer running Windows 7 Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit. I start Xwin this way (i.e. same as Cygwin-X group in Start menu): C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I don't know why SHELL defined as /bin/sh by default (my entry in the /etc/passwd file invokes bash). I could not find a way to change SHELL before XWin starts. One way I fixed it was to launch xterm from .XWinrc like this: "xterm" EXEC "xterm -e /bin/bash" instead of this: "xterm" EXEC "xterm -ls" -- 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 matseitz@cisco.com Thu Feb 20 18:45:00 2014 From: matseitz@cisco.com (Matt Seitz (matseitz)) Date: Thu, 20 Feb 2014 18:45:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: <53063FA4.5020806@gmail.com> References: <53063FA4.5020806@gmail.com> Message-ID: > From: Ola Str?mfors [mailto:ola.stromfors@gmail.com] > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > my shell specified in /etc/passwd or in the SHELL environment variable. > > The workaround I have found is to create /etc/shells with a list of > permitted shells, e.g. >From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301: Patch #301 - 2014/01/19 only set SHELL environment variable to programs found in /etc/shells (prompted by patch/report by Al Poole). -- 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 dickey@his.com Thu Feb 20 21:58:00 2014 From: dickey@his.com (Thomas Dickey) Date: Thu, 20 Feb 2014 21:58:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: References: <53063FA4.5020806@gmail.com> Message-ID: <20140220215747.GB3983@aerie.jexium-island.net> On Thu, Feb 20, 2014 at 11:33:22AM -0700, Jim Reisert AD1C wrote: > On Thu, Feb 20, 2014 at 10:47 AM, Ola Str?mfors wrote: > > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > > my shell specified in /etc/passwd or in the SHELL environment variable. > > I saw the same thing, but only on my home computer running Windows 7 > Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit. > > I start Xwin this way (i.e. same as Cygwin-X group in Start menu): > > C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe > > I don't know why SHELL defined as /bin/sh by default (my entry in the > /etc/passwd file invokes bash). I could not find a way to change That sounds like a case reported Saturday - see ftp://invisible-island.net/temp/xterm-301a.patch.gz I have a few other reports on different issues to iron out, and expect to be ok with #302 sometime next week. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From dickey@his.com Thu Feb 20 22:40:00 2014 From: dickey@his.com (Thomas Dickey) Date: Thu, 20 Feb 2014 22:40:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: References: <53063FA4.5020806@gmail.com> Message-ID: <20140220224047.GC3983@aerie.jexium-island.net> On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote: > > From: Ola Str?mfors [mailto:ola.stromfors@gmail.com] > > > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > > my shell specified in /etc/passwd or in the SHELL environment variable. > > > > The workaround I have found is to create /etc/shells with a list of > > permitted shells, e.g. > > >From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301: > > Patch #301 - 2014/01/19 > only set SHELL environment variable to programs found in /etc/shells (prompted by patch/report by Al Poole). yes. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From danilo.turina@alcatel-lucent.com Fri Feb 21 16:51:00 2014 From: danilo.turina@alcatel-lucent.com (Danilo Turina) Date: Fri, 21 Feb 2014 16:51:00 -0000 Subject: Clipboard integration does not work with XDMCP Message-ID: <530783F6.90209@alcatel-lucent.com> Hello, I need to connect from my PC to a Linux machine that runs KDE and I use the following command: XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR It works well but the clipboard integration that fails. Notice that: 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows clipboard 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux machine) I gave a look at the XWin log in two cases: A) XWin alone B) XWin + XDMCP And the only differences I've found (apart from the different command line arguments) is the following lines that were at the end of the log of the XDMCP invokation: winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winClipboardProc - trying to restart clipboard thread winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. I've searched around (google) for this problem but I found almost nothing (and most of that was old stuff). The only relevant suggestion was a post on this same mailing list that suggested to create the file /etc/X0.hosts and put "localhost" inside it. This doesn't work for me. Any help is appreciated. Thank you, Danilo Turina -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 20 giorni 8 ore 29 minuti 52 secondi -- 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 Feb 22 13:36:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 22 Feb 2014 13:36:00 -0000 Subject: Clipboard integration does not work with XDMCP In-Reply-To: <530783F6.90209@alcatel-lucent.com> References: <530783F6.90209@alcatel-lucent.com> Message-ID: <5308A7F3.5050900@dronecode.org.uk> On 21/02/2014 16:51, Danilo Turina wrote: > Hello, > I need to connect from my PC to a Linux machine that runs KDE and I use > the following command: > > XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR > > It works well but the clipboard integration that fails. > > Notice that: > 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows > clipboard > 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux > machine) > > I gave a look at the XWin log in two cases: > A) XWin alone > B) XWin + XDMCP > > And the only differences I've found (apart from the different command line > arguments) is the following lines that were at the end of the log of the XDMCP > invokation: > > winProcEstablishConnection - winInitClipboard returned. > winClipboardThreadProc - DISPLAY=:0.0 > winClipboardProc - XOpenDisplay () returned and successfully opened the display. > winClipboardIOErrorHandler! > winClipboardProc - setjmp returned for IO Error Handler. > winClipboardProc - trying to restart clipboard thread > winClipboardThreadProc - DISPLAY=:0.0 > winClipboardProc - XOpenDisplay () returned and successfully opened the display. > winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT > message, exiting main loop. > winClipboardProc - XDestroyWindow succeeded. Thanks for reporting this problem, and the clear reproduction steps. The issue here is that the XDMCP login dialog kills all other X clients (including the clipboard integration client) for security. The clipboard integration client is supposed to restart and reconnect as necessary, but it seems this has been broken for a while. I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you could try that and see if it improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.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 csylvain@electro-technica.com Sun Feb 23 02:54:00 2014 From: csylvain@electro-technica.com (Claude Sylvain) Date: Sun, 23 Feb 2014 02:54:00 -0000 Subject: Clipboard integration does not work with XDMCP In-Reply-To: <5308A7F3.5050900@dronecode.org.uk> References: <530783F6.90209@alcatel-lucent.com> <5308A7F3.5050900@dronecode.org.uk> Message-ID: <530962DA.4070100@electro-technica.com> On 02/22/2014 08:36 AM, Jon TURNEY wrote: > > Thanks for reporting this problem, and the clear reproduction steps. > > The issue here is that the XDMCP login dialog kills all other X clients > (including the clipboard integration client) for security. The clipboard > integration client is supposed to restart and reconnect as necessary, but it > seems this has been broken for a while. > > I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you > could try that and see if it improves things for you? > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 > I also noticed this problem, and tested your fix, above [1]. After applying your fix, Xwin clipboard transaction between local machine and remote machine (through XDMCP) seems to be functional. Claude -- 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 danilo.turina@alcatel-lucent.com Mon Feb 24 08:31:00 2014 From: danilo.turina@alcatel-lucent.com (Danilo Turina) Date: Mon, 24 Feb 2014 08:31:00 -0000 Subject: Clipboard integration does not work with XDMCP In-Reply-To: <5308A7F3.5050900@dronecode.org.uk> References: <530783F6.90209@alcatel-lucent.com> <5308A7F3.5050900@dronecode.org.uk> Message-ID: <530B0375.2070508@alcatel-lucent.com> Thank you very much for your prompt intervention. I can confirm that your fix works for me too. I see that now, in the log, lines like the followings are appearing: client(600000): Released pid(-1). client(600000): Released cmdline(NULL) and cmdargs(NULL). client(600000): Reserved pid(-1). client(600000): Reserved cmdname(NULL) and cmdargs(NULL). AllocNewConnection: client index = 3, socket fd = 13 I guess you raised the trace/log levels for debug/reporting purposes, so probably this is not relevant. Thank you, Danilo Turina Il 22/02/2014 14:36, Jon TURNEY ha scritto: > On 21/02/2014 16:51, Danilo Turina wrote: >> Hello, >> I need to connect from my PC to a Linux machine that runs KDE and I use >> the following command: >> >> XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR >> >> It works well but the clipboard integration that fails. >> >> Notice that: >> 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows >> clipboard >> 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux >> machine) >> >> I gave a look at the XWin log in two cases: >> A) XWin alone >> B) XWin + XDMCP >> >> And the only differences I've found (apart from the different command line >> arguments) is the following lines that were at the end of the log of the XDMCP >> invokation: >> >> winProcEstablishConnection - winInitClipboard returned. >> winClipboardThreadProc - DISPLAY=:0.0 >> winClipboardProc - XOpenDisplay () returned and successfully opened the display. >> winClipboardIOErrorHandler! >> winClipboardProc - setjmp returned for IO Error Handler. >> winClipboardProc - trying to restart clipboard thread >> winClipboardThreadProc - DISPLAY=:0.0 >> winClipboardProc - XOpenDisplay () returned and successfully opened the display. >> winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT >> message, exiting main loop. >> winClipboardProc - XDestroyWindow succeeded. > > Thanks for reporting this problem, and the clear reproduction steps. > > The issue here is that the XDMCP login dialog kills all other X clients > (including the clipboard integration client) for security. The clipboard > integration client is supposed to restart and reconnect as necessary, but it > seems this has been broken for a while. > > I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you > could try that and see if it improves things for you? > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 > -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 23 giorni 24 minuti 22 secondi -- 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 danilo.turina@alcatel-lucent.com Mon Feb 24 08:39:00 2014 From: danilo.turina@alcatel-lucent.com (Danilo Turina) Date: Mon, 24 Feb 2014 08:39:00 -0000 Subject: Clipboard integration does not work with XDMCP In-Reply-To: <5308A7F3.5050900@dronecode.org.uk> References: <530783F6.90209@alcatel-lucent.com> <5308A7F3.5050900@dronecode.org.uk> Message-ID: <530B052D.9090808@alcatel-lucent.com> Il 22/02/2014 14:36, Jon TURNEY ha scritto: > On 21/02/2014 16:51, Danilo Turina wrote: >> Hello, >> I need to connect from my PC to a Linux machine that runs KDE and I use >> the following command: >> >> XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR >> >> It works well but the clipboard integration that fails. >> >> Notice that: >> 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows >> clipboard >> 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux >> machine) >> >> I gave a look at the XWin log in two cases: >> A) XWin alone >> B) XWin + XDMCP >> >> And the only differences I've found (apart from the different command line >> arguments) is the following lines that were at the end of the log of the XDMCP >> invokation: >> >> winProcEstablishConnection - winInitClipboard returned. >> winClipboardThreadProc - DISPLAY=:0.0 >> winClipboardProc - XOpenDisplay () returned and successfully opened the display. >> winClipboardIOErrorHandler! >> winClipboardProc - setjmp returned for IO Error Handler. >> winClipboardProc - trying to restart clipboard thread >> winClipboardThreadProc - DISPLAY=:0.0 >> winClipboardProc - XOpenDisplay () returned and successfully opened the display. >> winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT >> message, exiting main loop. >> winClipboardProc - XDestroyWindow succeeded. > > Thanks for reporting this problem, and the clear reproduction steps. > > The issue here is that the XDMCP login dialog kills all other X clients > (including the clipboard integration client) for security. The clipboard > integration client is supposed to restart and reconnect as necessary, but it > seems this has been broken for a while. > > I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you > could try that and see if it improves things for you? > > [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 > Sorry for top posting... I resend here my previous e-mail, without top posting. --- Thank you very much for your prompt intervention. I can confirm that your fix works for me too. I see that now, in the log, lines like the followings are appearing: client(600000): Released pid(-1). client(600000): Released cmdline(NULL) and cmdargs(NULL). client(600000): Reserved pid(-1). client(600000): Reserved cmdname(NULL) and cmdargs(NULL). AllocNewConnection: client index = 3, socket fd = 13 I guess you raised the trace/log levels for debug/reporting purposes, so probably this is not relevant. Thank you, Danilo Turina -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 23 giorni 34 minuti 43 secondi -- 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 Feb 25 19:08:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 25 Feb 2014 19:08:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.15.0-3 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.15.0-3 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.15.0-2: * Repair clipboard thread restart to fix clipboard integration when using XDMCP x86: d7781c8687ccc1899247d926ee9e3ac4 *xorg-server-1.15.0-3-src.tar.xz bbc29bb3fa18db2718d76194d85af29d *xorg-server-1.15.0-3.tar.xz e0532f3c58c23fbc26bc106ec0787fd4 *xorg-server-common-1.15.0-3.tar.xz 3f454a19e21ae0946f3feac5f3126d63 *xorg-server-debuginfo-1.15.0-3.tar.xz f56c1be28a08641e1f87688880802a01 *xorg-server-devel-1.15.0-3.tar.xz dae8627af10f67cbc7e05481e40f79a9 *xorg-server-dmx-1.15.0-3.tar.xz 23fda3a7ad5e3715cce264e276bd9d26 *xorg-server-extra-1.15.0-3.tar.xz 1cff6e920a03faae1aa92073f284495b *xwinclip-1.15.0-3.tar.xz x86_64: defec20186c24179bdcc3788121546af *xorg-server-1.15.0-3-src.tar.xz 0fbcf1723f69e5ad60b671abcf9ba629 *xorg-server-1.15.0-3.tar.xz 336fb72e0f0cdb8ab1a74a9e87696730 *xorg-server-common-1.15.0-3.tar.xz 0228c041826e2a9f08448030aa943aab *xorg-server-debuginfo-1.15.0-3.tar.xz 48bf6754524d5fb0b1e5a3fd676f1804 *xorg-server-devel-1.15.0-3.tar.xz b9bc92c27bc49f4b367eb251d7bc569d *xorg-server-dmx-1.15.0-3.tar.xz 565d6f9c0f62af0cade69b70ea77c86f *xorg-server-extra-1.15.0-3.tar.xz 46d177a5bf0928215ccf16fe02e656ed *xwinclip-1.15.0-3.tar.xz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Thu Feb 27 17:07:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 27 Feb 2014 17:07:00 -0000 Subject: [ANNOUNCEMENT] Updated: python-pyqt4, qscintilla2 Message-ID: The following packages have been updated for both arches: * libqscintilla2_11-2.8-1 * libqscintilla2-common-2.8-1 * libqscintilla2-devel-2.8-1 * python-pyqt4-4.10.3-1 * python-pyqt4-qsci-2.8-1 * python-sip-4.15.4-1 * python3-pyqt4-4.10.3-1 * python3-pyqt4-qsci-2.8-1 * python3-sip-4.15.4-1 This in an update to the latest upstream releases of PyQt4 and QScintilla, with an ABI version bump for the latter. -- 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 matseitz@cisco.com Thu Feb 27 18:06:00 2014 From: matseitz@cisco.com (Matt Seitz (matseitz)) Date: Thu, 27 Feb 2014 18:06:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: <20140220224047.GC3983@aerie.jexium-island.net> References: <20140220224047.GC3983@aerie.jexium-island.net> Message-ID: > From: Thomas Dickey [mailto:dickey@his.com] > > On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote: > > > From: Ola Str?mfors [mailto:ola.stromfors@gmail.com] > > > > > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > > > my shell specified in /etc/passwd or in the SHELL environment variable. > > > > > > The workaround I have found is to create /etc/shells with a list of > > > permitted shells, e.g. > > > > (whether xterm should use $SHELL incoming is a different issue that I > am reconsidering) Is there any ETA for a resolution of this issue? I've been holding off on upgrading to xterm-301 because of this issue. I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own "/etc/shells". -- 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 dickey@his.com Thu Feb 27 22:00:00 2014 From: dickey@his.com (Thomas Dickey) Date: Thu, 27 Feb 2014 22:00:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: References: <20140220224047.GC3983@aerie.jexium-island.net> Message-ID: <20140227220020.GA3938@aerie.jexium-island.net> On Thu, Feb 27, 2014 at 06:05:48PM +0000, Matt Seitz (matseitz) wrote: > > From: Thomas Dickey [mailto:dickey@his.com] > > > > On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote: > > > > From: Ola Str?mfors [mailto:ola.stromfors@gmail.com] > > > > > > > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > > > > my shell specified in /etc/passwd or in the SHELL environment variable. > > > > > > > > The workaround I have found is to create /etc/shells with a list of > > > > permitted shells, e.g. > > > > > > > (whether xterm should use $SHELL incoming is a different issue that I > > am reconsidering) > > Is there any ETA for a resolution of this issue? I added that to my changes for #302 yesterday, and have a couple more issues to resolve (probably #302 will be available this weekend) > I've been holding off on upgrading to xterm-301 because of this issue. I'm > not sure if there is some patch coming soon (either to xterm or adding a > default /etc/shells to Cygwin), or if I should just plan on manually creating > my own "/etc/shells". With #302, this will work: SHELL=whatever xterm but this is a special case (the program will run - a fix - but will need to be in /etc/shells to have xterm set $SHELL): xterm whatever -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From corinna-cygwin@cygwin.com Fri Feb 28 09:19:00 2014 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Fri, 28 Feb 2014 09:19:00 -0000 Subject: Problem with xterm-301-1 In-Reply-To: <20140227220020.GA3938@aerie.jexium-island.net> References: <20140220224047.GC3983@aerie.jexium-island.net> <20140227220020.GA3938@aerie.jexium-island.net> Message-ID: <20140228091921.GM2246@calimero.vinschen.de> On Feb 27 17:00, Thomas Dickey wrote: > On Thu, Feb 27, 2014 at 06:05:48PM +0000, Matt Seitz (matseitz) wrote: > > > From: Thomas Dickey [mailto:dickey@his.com] > > > > > > On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote: > > > > > From: Ola Str?mfors [mailto:ola.stromfors@gmail.com] > > > > > > > > > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of > > > > > my shell specified in /etc/passwd or in the SHELL environment variable. > > > > > > > > > > The workaround I have found is to create /etc/shells with a list of > > > > > permitted shells, e.g. > > > > > > > > > > (whether xterm should use $SHELL incoming is a different issue that I > > > am reconsidering) > > > > Is there any ETA for a resolution of this issue? > > I added that to my changes for #302 yesterday, and have a couple more > issues to resolve (probably #302 will be available this weekend) > > > I've been holding off on upgrading to xterm-301 because of this issue. I'm > > not sure if there is some patch coming soon (either to xterm or adding a > > default /etc/shells to Cygwin), or if I should just plan on manually creating > > my own "/etc/shells". > > With #302, this will work: > > SHELL=whatever xterm > > but this is a special case (the program will run - a fix - but > will need to be in /etc/shells to have xterm set $SHELL): > > xterm whatever May I politely ask why xterm cares at all? What is the reasoning behind this? Heere's why I'm asking: Xterm is not a login process, like login(1) or sshd(8). If somebody starts xterm, the login process itself has long exec'ed the login shell, and the permission problem what shell is allowed to be started as login shell is done. Afterwards, the user is usually allowed to start whatever process he or she has a right to. It looks really weird to me that a terminal emulator would decide that certain processes are not allowed to a user which otherwise work fine. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: