From gbarrick@kent.edu Sun Mar 1 14:06:00 2015 From: gbarrick@kent.edu (GEORGE BARRICK) Date: Sun, 01 Mar 2015 14:06:00 -0000 Subject: Dfficulty with xorg-server-1.17.1-2. In-Reply-To: <54F2077C.9080802@dronecode.org.uk> References: <54ECD29B.7050001@dronecode.org.uk> <54ECEFDC.5080107@dronecode.org.uk> <54F2077C.9080802@dronecode.org.uk> Message-ID: 2015.03.01.09:06:13 EST Hi Jon, Thanks for the tips. George gee_barrick_at_kent_dot_edu On 2/28/15, Jon TURNEY wrote: > On 25/02/2015 14:30, GEORGE BARRICK wrote: >> I have one small note for other folks who might like to run their >> system in a way similar to mine. I like to have xlaunch automatically >> start a single colored xterm for me (in multi-window mode). After >> that I just open more from the command line as it suits me. If I use >> the command line embedded in the installed xlaunch.lnk file: >> >> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/xlaunch.exe >> >> it always prompts me through the tiresome "configure & start" GUI at >> the beginning. Adding the phrase >> >> -run ~/config/config.xlaunch >> >> at the end of that command line always gets ignored in favor of the >> "configure & start" GUI. > > You need to quote the whole command line for bash after the -c, > otherwise bash treats words after the first one as positional parameters. > > However, getting this quotation passed correctly through run requires a > little bit of gymnastics, but this should work: > > C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "xlaunch -run > ~/config/config.xlaunch" > >> However, when I strip the invocation of the >> bash from that command: >> >> C:\cygwin\bin\run.exe /usr/bin/xlaunch.exe -run ~/config/config.xlaunch >> >> the xlaunch goes right ahead to run the single xterm that's described >> in my ~/config/config.xlaunch file. > > This is not quite equivalent as there is no login shell in the ancestry > of whatever your config.xlaunch starts, so your ~/.profile may not have > been read. > > For that reason, using 'bash -l -c ""' is preferred and that's what > start menu links that cygwin installs generally use. > > -- > 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 mikedep333@gmail.com Sun Mar 1 18:15:00 2015 From: mikedep333@gmail.com (Michael DePaulo) Date: Sun, 01 Mar 2015 18:15:00 -0000 Subject: Display issue In-Reply-To: <54ED03DE.7010904@gmail.com> References: <54ED03DE.7010904@gmail.com> Message-ID: On Tue, Feb 24, 2015 at 6:06 PM, Maarten Hoes wrote: > Hi, > > > Im experiencing an issue where the graphics arent displayed correctly. When > I start LibreOffice on my Fedora 21 Linux system from a cygwin/x system, the > left hand side (open file, template, writer document, etc.) isnt displayed > properly initially. After clicking around some, the display updates and gets > displayed right. > > Here's a screenshot of the badly displayed graphics: > http://imgur.com/bTD4yQ3 > > And this is what it looks like (correctly) after some clicking around: > http://imgur.com/adj5mKD > > I have no idea on how to start troubleshooting the issue; all thoughts and > ideas are more than welcome. I just tried to reproduce this, but I was unable to. The icons looked correct even before I selected help -> about: http://i.imgur.com/Tp50WK8.png I am using XWin 1.17.1-2 32-bit in multiwindow mode on Windows 10 64-bit. I launched XWin via "startxwin" and then ran "ssh -Y " from the xterm. I then ran "libreoffice". Server is Fedora 21 64-bit. There was no command-line output from LibreOffice. -Mike -- 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 hoes.maarten@gmail.com Sun Mar 1 18:46:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Sun, 01 Mar 2015 18:46:00 -0000 Subject: Display issue In-Reply-To: References: <54ED03DE.7010904@gmail.com> Message-ID: <54F35E85.9040402@gmail.com> Hi, On 1-3-2015 19:15, Michael DePaulo wrote: > > I just tried to reproduce this, but I was unable to. > The icons looked correct even before I selected help -> about: > http://i.imgur.com/Tp50WK8.png > I can reproduce it 100% of the time. > > I am using XWin 1.17.1-2 32-bit in multiwindow mode on Windows 10 > 64-bit. I launched XWin via "startxwin" and then ran "ssh -Y > " from the xterm. I then ran "libreoffice". > I am running a single window XDCMP session with a KDM display manager (xwin -query x.x.x.x or Xlaunch). There is no ssh usage. I am running Windows 8.1 64 bit. I open a terminal window and run ./soffice. > > Server is Fedora 21 64-bit. > Same here. > > There was no command-line output from LibreOffice. > My guess is that my building with --enable-dbg-util etc. has something to do with that. - Maarten -- 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@cygwin.com Mon Mar 2 23:34:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 02 Mar 2015 23:34:00 -0000 Subject: Cannot run Qt5 applications. In-Reply-To: <54DE4334.9060101@dronecode.org.uk> References: <54D2A922.3060507@tiscali.co.uk> <54D2CA12.5080701@dronecode.org.uk> <54DE4334.9060101@dronecode.org.uk> Message-ID: <1425339264.7292.8.camel@cygwin.com> On Fri, 2015-02-13 at 18:32 +0000, Jon TURNEY wrote: > On 05/02/2015 01:40, Jon TURNEY wrote: > > On 04/02/2015 23:20, David Stacey wrote: > >> I'm having difficulty running any Qt5 application. These are the > >> commands I'm issuing: > >> [snip] > >> and I see the clock, so X is up and running. Then: > >> [snip] > > > > Possibly you need to install and start cygserver (See [1]) > > > > If so, this is because Qt5 is assuming shared memory is available, which > > could possibly be handled in a better way... > > This looks like a portability problem in Qt5, where it only handles > shmget() failing with a return value of -1, not with SIGSYS, to fallback > to using an image in unshared memory. > > Patch attached. Or is it a problem with our shmget()? http://pubs.opengroup.org/onlinepubs/9699919799/functions/shmget.html http://man7.org/linux/man-pages/man2/shmget.2.html Perhaps we should be just returning -1 with an errno (ENOSYS?) instead of raise(SIGSYS)? -- 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 corinna-cygwin@cygwin.com Tue Mar 3 09:04:00 2015 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Tue, 03 Mar 2015 09:04:00 -0000 Subject: Cannot run Qt5 applications. In-Reply-To: <1425339264.7292.8.camel@cygwin.com> References: <54D2A922.3060507@tiscali.co.uk> <54D2CA12.5080701@dronecode.org.uk> <54DE4334.9060101@dronecode.org.uk> <1425339264.7292.8.camel@cygwin.com> Message-ID: <20150303090407.GA31622@calimero.vinschen.de> On Mar 2 17:34, Yaakov Selkowitz wrote: > On Fri, 2015-02-13 at 18:32 +0000, Jon TURNEY wrote: > > On 05/02/2015 01:40, Jon TURNEY wrote: > > > On 04/02/2015 23:20, David Stacey wrote: > > >> I'm having difficulty running any Qt5 application. These are the > > >> commands I'm issuing: > > >> [snip] > > >> and I see the clock, so X is up and running. Then: > > >> [snip] > > > > > > Possibly you need to install and start cygserver (See [1]) > > > > > > If so, this is because Qt5 is assuming shared memory is available, which > > > could possibly be handled in a better way... > > > > This looks like a portability problem in Qt5, where it only handles > > shmget() failing with a return value of -1, not with SIGSYS, to fallback > > to using an image in unshared memory. > > > > Patch attached. > > Or is it a problem with our shmget()? > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/shmget.html > http://man7.org/linux/man-pages/man2/shmget.2.html > > Perhaps we should be just returning -1 with an errno (ENOSYS?) instead > of raise(SIGSYS)? Or you just add signal(SIGSYS, SIG_IGN) prior to calling shmget. SIGSYS is raised when calling a system call which isn't available. That's perfectly valid. Of course, it would be nice if Qt5 used POSIX shared memory objects iunstead, but that's asked too much, probably. 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: From jon.turney@dronecode.org.uk Tue Mar 3 14:49:00 2015 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 03 Mar 2015 14:49:00 -0000 Subject: Cannot run Qt5 applications. In-Reply-To: <20150303090407.GA31622@calimero.vinschen.de> References: <54D2A922.3060507@tiscali.co.uk> <54D2CA12.5080701@dronecode.org.uk> <54DE4334.9060101@dronecode.org.uk> <1425339264.7292.8.camel@cygwin.com> <20150303090407.GA31622@calimero.vinschen.de> Message-ID: <54F5C9DA.2040703@dronecode.org.uk> On 03/03/2015 09:04, Corinna Vinschen wrote: > On Mar 2 17:34, Yaakov Selkowitz wrote: >> On Fri, 2015-02-13 at 18:32 +0000, Jon TURNEY wrote: >>> On 05/02/2015 01:40, Jon TURNEY wrote: >>>> On 04/02/2015 23:20, David Stacey wrote: >>>>> I'm having difficulty running any Qt5 application. These are the >>>>> commands I'm issuing: >>>>> [snip] >>>>> and I see the clock, so X is up and running. Then: >>>>> [snip] >>>> >>>> Possibly you need to install and start cygserver (See [1]) >>>> >>>> If so, this is because Qt5 is assuming shared memory is available, which >>>> could possibly be handled in a better way... >>> >>> This looks like a portability problem in Qt5, where it only handles >>> shmget() failing with a return value of -1, not with SIGSYS, to fallback >>> to using an image in unshared memory. >>> >>> Patch attached. >> >> Or is it a problem with our shmget()? >> >> http://pubs.opengroup.org/onlinepubs/9699919799/functions/shmget.html >> http://man7.org/linux/man-pages/man2/shmget.2.html >> >> Perhaps we should be just returning -1 with an errno (ENOSYS?) instead >> of raise(SIGSYS)? I think it was a BSD-ism to raise SIGSYS if shared memory is not available due to policy. Historically, there must have been some OS which did this, because there is code to detect this situation in the X server [1] [1] http://cgit.freedesktop.org/xorg/xserver/tree/Xext/shm.c#n167 Looking at [2],[3] it seems perhaps this was added in Cygwin because some FreeBSD test code was used? [2] https://cygwin.com/ml/cygwin-cvs/2003-q4/msg00130.html [3] https://cygwin.com/ml/cygwin-cvs/2003-q4/msg00128.html I'd kind of assumed that modern BSDs behave in the same way, but that doesn't actually seem likely. I have absolutely no problem with changing this to return ENOSPC (there is a limit of 0 SHM identifiers, and we have reached it), or whatever is appropriate in this state. > Or you just add signal(SIGSYS, SIG_IGN) prior to calling shmget. > SIGSYS is raised when calling a system call which isn't available. > That's perfectly valid. This is true. I guess it's not how Linux behaves, though, so I think changing it ought to be considered to minimize porting effort. I'll also note that checking once at startup, as the X server does, is not enough. If the cygserver is stopped, it will die with an unexpected SIGSYS when a client tried to use shared memory. > Of course, it would be nice if Qt5 used POSIX shared memory objects > instead, but that's asked too much, probably. Unfortunately, it has to use whatever the X server's MIT-SHM extension uses... -- 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 corinna-cygwin@cygwin.com Tue Mar 3 17:11:00 2015 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Tue, 03 Mar 2015 17:11:00 -0000 Subject: Cannot run Qt5 applications. In-Reply-To: <54F5C9DA.2040703@dronecode.org.uk> References: <54D2A922.3060507@tiscali.co.uk> <54D2CA12.5080701@dronecode.org.uk> <54DE4334.9060101@dronecode.org.uk> <1425339264.7292.8.camel@cygwin.com> <20150303090407.GA31622@calimero.vinschen.de> <54F5C9DA.2040703@dronecode.org.uk> Message-ID: <20150303171123.GR3213@calimero.vinschen.de> On Mar 3 14:48, Jon TURNEY wrote: > On 03/03/2015 09:04, Corinna Vinschen wrote: > >Or you just add signal(SIGSYS, SIG_IGN) prior to calling shmget. > >SIGSYS is raised when calling a system call which isn't available. > >That's perfectly valid. > > This is true. > > I guess it's not how Linux behaves, though, so I think changing it ought to > be considered to minimize porting effort. Done. HTH, 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: From corinna-cygwin@cygwin.com Tue Mar 3 20:24:00 2015 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Tue, 03 Mar 2015 20:24:00 -0000 Subject: [ANNOUNCEMENT] Merge of cygwin-xfree-announce into cygwin-announce Message-ID: Hi folks, it's becoming awkward having to split package announcements between two mailing lists. In fact, there's neither a good reason having to decide where to send an announcement, nor having to subscribe to two lists for Cygwin package announcements. Therefore, effectiv immediately, we're going to give up the cygwin-xfree-announce mailing list in favor of only the cygwin-announce mailing list. ======================================================================= In future, new Cygwin packages and package updates will be announced on cygwin-announce only. ======================================================================= If you're not subscribed to cygwin-announce, only to cygwin-xfree-announce, I'll suggest to subscribe to cygwin-announce instead. For reference and archeological diggings, the cygwin-xfree-announce archives will stay available. Peace, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From corinna-cygwin@cygwin.com Tue Mar 3 20:45:00 2015 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Tue, 03 Mar 2015 20:45:00 -0000 Subject: [ANNOUNCEMENT] Merge of cygwin-xfree-announce into cygwin-announce Message-ID: Hi folks, it's becoming awkward having to split package announcements between two mailing lists. In fact, there's neither a good reason having to decide where to send an announcement, nor having to subscribe to two lists for Cygwin package announcements. Therefore, effectiv immediately, we're going to give up the cygwin-xfree-announce mailing list in favor of only the cygwin-announce mailing list. ======================================================================= In future, new Cygwin packages and package updates will be announced on cygwin-announce only. ======================================================================= If you're not subscribed to cygwin-announce, only to cygwin-xfree-announce, I'll suggest to subscribe to cygwin-announce instead. For reference and archeological diggings, the cygwin-xfree-announce archives will stay available. Peace, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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 Mar 4 13:57:00 2015 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 04 Mar 2015 13:57:00 -0000 Subject: [ANNOUNCEMENT] cygwin-xfree list deprecation Message-ID: Dear Internet, It no longer makes much sense to have a separate list for Cygwin X related traffic, so the cygwin-xfree list is now officially deprecated. Reasons for this decision include: - the level of traffic on the cygwin-xfree list is low - splitting the traffic in this way currently serves no useful purpose - the distinction between what is and is not an X issue is artificial, vague, and often ignored The cygwin-xfree list will continue to operate, but I suggest and encourage you to use the main cygwin list for all your cygwin X server and X application related questions, bug reports, moans, gripes, whines and patches ;-). The Cygwin X website and documentation will be updated to point to the main cygwin list. Mail delivery for the cygwin-xfree list may be turned off at some future date, but even if that happens, the list archives will continue to be available. Live Long and Prosper, Jon -- 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 mikedep333@gmail.com Sat Mar 7 12:59:00 2015 From: mikedep333@gmail.com (Michael DePaulo) Date: Sat, 07 Mar 2015 12:59:00 -0000 Subject: Display issue In-Reply-To: <54F35E85.9040402@gmail.com> References: <54ED03DE.7010904@gmail.com> <54F35E85.9040402@gmail.com> Message-ID: (I know that cygwin-xfree is deprecated. But I believe I should continue this existing conversation on it.) On Sun, Mar 1, 2015 at 1:46 PM, Maarten Hoes wrote: > Hi, > > > On 1-3-2015 19:15, Michael DePaulo wrote: >> >> >> I just tried to reproduce this, but I was unable to. >> The icons looked correct even before I selected help -> about: >> http://i.imgur.com/Tp50WK8.png >> > I can reproduce it 100% of the time. > > >> >> I am using XWin 1.17.1-2 32-bit in multiwindow mode on Windows 10 >> 64-bit. I launched XWin via "startxwin" and then ran "ssh -Y >> " from the xterm. I then ran "libreoffice". >> > I am running a single window XDCMP session with a KDM display manager (xwin > -query x.x.x.x or Xlaunch). There is no ssh usage. I am running Windows 8.1 > 64 bit. I open a terminal window and run ./soffice. I recreated your setup on my Fedora 21 64-bit test VM, but I was unable to reproduce it: 1. Install package group: KDE 2. Install package kdm (not sure if it was part of the package group or not) 3. Enable XDMCP in KDM (this involved rebooting) 4. X :1 -query 5. Login to KDM 6. Open up Konsole 7. Install package libreoffice 8. soffice (did not reproduce the bug) 9. Install the libreoffice-kde package 10. soffice (did not reproduce the bug) >> Server is Fedora 21 64-bit. >> > Same here. > > >> >> >> There was no command-line output from LibreOffice. >> > My guess is that my building with --enable-dbg-util etc. has something to do > with that. That's possible. Did you build from upstream source or from the Fedora SRPM? The Fedora SRPM has a TON of patches: http://pkgs.fedoraproject.org/cgit/libreoffice.git/tree/?h=f21 -Mike -- 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 faithyu@mail.com Thu Mar 12 12:44:00 2015 From: faithyu@mail.com (Lance) Date: Thu, 12 Mar 2015 12:44:00 -0000 Subject: Data Recovery Services and Hardware Repair Services Message-ID: We have made helping people our business. We only do data recovery, we do it all day, every day - we have become the very best in this field. We have seen all types of problems and solved nearly all of them! Why we are here? Data ??? Important assets of enterprises and individuals, is the key element of great success. Virus Attack, Back-up failure, Hard Disk Drive Crash, System Failure, Nature Disasters, Human Errors are one of the causes of Data Loss, which might potentially cause million and billions loss of profit. IntelliRecovery experts with their overwhelming experience, state-of-the-art tools and deep knowledge provide finest and innovative Data Recovery Solutions for all types of storage media and file systems in case of data loss. We are dedicated to provide you unmatchable, updated and quality data recovery services and we have enduring commitments to customer satisfaction. Nowadays, personal computer, mobile devices, networks, servers etc are so popular and they have become something we can???t miss in our daily life. This kind of digital platform can drive efficiency and convenience, unfortunately there is a huge risk behind ??? Data loss. Hence, IntelliRecovery team are here to recover and salvage lost data from disaster stricken hard drives, computer workstations, laptops, e-mails, smartphones, PDA's, iPods and portable storage media of every brand, manufacturer, model and capacity. What can we do? Hard disk data recovery RAID array data recovery Emergency data recovery USB flash drive data recovery Memory card data recovery Mobile phone data recovery Apple iPhone Passcode/PIN Removal Mobile Phone Spyware & Virus Detection NAS Data Recovery Data destruction Hard disk duplication Hard disk password removal We believe in doing business in an honest, friendly and professional way. We are always up front, honest and provide realistic time estimates, quotes and believe in providing the best service possible. No data recovery company can guarantee that they can recover your data (e.g if your disk platter is scratched or data is overwritten) but we promise not to give up until we recover your data or completely exhaust all possible options to help you! If your data cannot be recovered for any reason, we'll give you an honest explanation of the reason and assure you that we have done everything in our power to try to help you. In over 90% of cases, we can recover data from hard disks and other data storage devices. We look forward to helping you! We also provide Mobile Phone Repair services for Iphone, Ipad, and we specialize in repairing cell phones, smart phones, computers, laptops, game consoles, cameras, mp3 players, and most any other electronic gadget you can throw at us. We strive to create solutions where there weren???t any before. Best regards, Lance Email: drdataback@tom.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 xflr6@orange.fr Thu Mar 12 14:56:00 2015 From: xflr6@orange.fr (xflr6) Date: Thu, 12 Mar 2015 14:56:00 -0000 Subject: Cygwin/X : display error with latest x-related packages Message-ID: <1930538333.15658.1426164241046.JavaMail.www@wwinf1m22> Dear Cygwin/X users and developpers, I recently experienced a problem with a program using the X window system. With the latest Cygwin release, the latter is not able to open the display, whereas with previous versions of cygwin (+ the x-window machinery, i.e the Cygwin/X installation as described in the installation notes, with xlaunch, xinit, xorg-server etc.) (prior to mid-February 2015), it was working correctly. Other programs using the X window system, such as ghostview for example, is working correctly on my installation. I have seen on the Cygwin/X news that X server and X.Org X11 packages have been upgraded to newer versions, and I was wondering if there was a known loss of backward compatibility with these fresh versions (even a simple change, like in the DISPLAY variable or something like that) ? Best regards, xflr6 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From corinna-cygwin@cygwin.com Thu Mar 19 23:14:00 2015 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Thu, 19 Mar 2015 23:14:00 -0000 Subject: Cygwin/X : display error with latest x-related packages In-Reply-To: <1930538333.15658.1426164241046.JavaMail.www@wwinf1m22> References: <1930538333.15658.1426164241046.JavaMail.www@wwinf1m22> Message-ID: <20150312145632.GV5732@calimero.vinschen.de> On Mar 12 13:44, xflr6 wrote: > Dear Cygwin/X users and developpers, Please note that the cygwin-xfree list has been deprecated. Use the cygwin AT cygwin DOT com list instead. Thanks, 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: From cygwin@tlinx.org Tue Mar 31 18:36:00 2015 From: cygwin@tlinx.org (Linda Walsh) Date: Tue, 31 Mar 2015 18:36:00 -0000 Subject: Disable xterm auto-wrap: Mess up vi-like command line In-Reply-To: References: Message-ID: <550B5840.3020600@tlinx.org> Paul wrote: > If I disable auto-wrap, the vi editing at the comand line misbehaves > when the line being edited is long, especially when yanking a lot of > text and pasting it. I suppose that this might be technically correct > behaviour, since an extra long command line needs to wrap in order to > see it properly. But I use the vi command line exclusively, and > almost always, I don't want autowrap in the results from commands > being sent to the screen. Is there a way to get both at the same > time, without having to always toggle the xterm autowrap? --- What do you mean by "mess up"? It "shouldn't". I just cut and pasted some text from an xterm into an editor, and the lines weren't split... they got copied as one line. However, if I was to cut from a Windows Console window (cmd.exe for example), it DOES, physically, split long lines. It's a property of the console. The main problem I've seen in bash is when you paste content that has tabs in it. Then bash tries to auto complete in the middle of your typing... often asking a question or pausing -- which means it *swallows* up the tab and 1-2 keys after the tab. It didn't use to do this back in the 3.x series, but was added as a new feature in the 4.x series. I ended up changing my "completion character" to BACKQUOTE to try to get around this. Maybe tabs are causing your problem? Example. At a prompt, I typed: cat " (I hit enter after that first quote and went to the next line and hit my completion char (BACKQUOTE "`"), Then I got: > cat " > Display all 186 possibilities? (y or n) --- At this point, whatever character is next in my paste buffer will be swallowed up (in addition to the completion character). --- Since the long line cut/paste worked for me in 'xterm', that's why I thought maybe you were hitting bash'es "input mangling"-feature!... -- 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 michel.poirier@cea.fr Tue Mar 31 20:31:00 2015 From: michel.poirier@cea.fr (Michel Poirier) Date: Tue, 31 Mar 2015 20:31:00 -0000 Subject: Cygwin XWin 1.17.1 crash at startup Message-ID: <551AE926.5050905@cea.fr> Dear Cygwin maintainer Since last X-Cygwin update several of my X-Win applications are not working properly. Googling "cygwin xorg 1.17 crash" gave many posts reporting probably similar issues but I couldn't find a fix for the error. I also looked at the Cygwin-FAQ and mailing list without real success. The issue appeared using a long-time tested DOS script launching xmgrace which failed with a message telling "A fatal error has occurred and Cygwin/X will now exit." And other XWin programs were not working properly. So I tried to make a fresh install of X-Cygwin (32 bits) on another computer and went through the procedure explained on page http://x.cygwin.com/devel/backtrace.html which produced the debug info attached as "backtrace for X server crashing at startup.txt". The X Server crashed when the r command was launched and a copy of the Windows error message is provided at "Capture of Windows error message.txt". I checked that no other X Server was then running and clicked Ok button to finish the procedure. The content of the file /var/log/xwin/XWin.0.log is listed at the end of the first attached file. I also tried to install the most recent xlaunch program as suggested here https://www.cygwin.com/ml/cygwin-xfree/2015-02/msg00089.html but it did not solve the issue. Sorry for asking something that might be FAQ but as I told I could not find a clear answer elsewhere and indeed xlaunch reproduced the error consistently. Thanking you in advance for your assistance, and of course for providing this invaluable software that is cygwin. Regards -- Michel Poirier CEA, IRAMIS Laboratoire Interactions, Dynamique et Lasers Centre d'??tudes de Saclay, b??t. 522 F91191 Gif/Yvette (France) T??l. : +33 1 69 08 46 29 FAX : +33 1 69 08 87 07 e-mail: michel.poirier@cea.fr -------------- next part -------------- IRAM-FA-004439+admin-local@IRAM-FA-004439 ~ $ gdb --args /usr/bin/XWin -multiwindow GNU gdb (GDB) 7.8 Copyright (C) 2014 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-pc-cygwin". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/XWin...Reading symbols from /usr/lib/debug//usr/bi n/XWin.exe.dbg...Can't read data for section '.debug_frame' in file '/usr/lib/de bug/usr/bin/XWin.exe.dbg' (gdb) handle SIGSYS nostop Signal Stop Print Pass to program Description SIGSYS No Yes Yes Bad system call (gdb) r Starting program: /usr/bin/XWin -multiwindow [New Thread 5852.0xc88] [New Thread 5852.0x1a0c] [New Thread 5852.0xcec] [New Thread 5852.0x1548] [New Thread 5852.0x50c] [New Thread 5852.0x4e0] [Thread 5852.0x4e0 exited with code 1] [Thread 5852.0x1a0c exited with code 1] [Thread 5852.0x50c exited with code 1] [Thread 5852.0xcec exited with code 1] [Inferior 1 (process 5852) exited with code 01] (gdb) bt full No stack. (gdb) q IRAM-FA-004439+admin-local@IRAM-FA-004439 ~ $ cat /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-6.1-WOW IRAM-FA-004439 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command line: /usr/bin/XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1200 winInitializeScreenDefaults - native DPI x 96 y 96 _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't alread y running(EE) [ 17451.691] (EE) Server terminated with error (1). Closing log file. -------------- next part -------------- A fatal error has occurred and Cygwin/X will now exit. Cannot establish any listening sockets - Make sure an X server isn't already running Please open /var/log/xwin/XWin.0.log for more information. Vendor: The Cygwin/X Project Release: 1.17.1.0 Contact: cygwin-xfree@cygwin.com Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command-line: /usr/bin/XWin -multiwindow -------------- 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 marco.atzeri@gmail.com Tue Mar 31 22:15:00 2015 From: marco.atzeri@gmail.com (Marco Atzeri) Date: Tue, 31 Mar 2015 22:15:00 -0000 Subject: Cygwin XWin 1.17.1 crash at startup In-Reply-To: <551AE926.5050905@cea.fr> References: <551AE926.5050905@cea.fr> Message-ID: <551B03FC.7050900@gmail.com> On 3/31/2015 8:36 PM, Michel Poirier wrote: > Dear Cygwin maintainer > > Since last X-Cygwin update several of my X-Win applications are not > working properly. > > Googling "cygwin xorg 1.17 crash" gave many posts reporting probably > similar issues but I couldn't find a fix for the error. I also looked at > the Cygwin-FAQ and mailing list without real success. can you just run startxwin from mintty and report the outcome ? There were several changes in the default https://www.cygwin.com/ml/cygwin-xfree-announce/2015-02/msg00000.html https://www.cygwin.com/ml/cygwin-xfree-announce/2015-02/msg00014.html may be you are hitting one of them. Regards Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ceuso@yahoo.com.br Tue Mar 31 22:22:00 2015 From: ceuso@yahoo.com.br (Ceuso) Date: Tue, 31 Mar 2015 22:22:00 -0000 Subject: Cygwin/X : display error with latest x-related packages References: <1930538333.15658.1426164241046.JavaMail.www@wwinf1m22> Message-ID: xflr6 orange.fr> writes: > > Dear Cygwin/X users and developpers, > > I recently experienced a problem with a program using the X window system. > With the latest Cygwin release, the latter is not able to open the display, whereas with previous versions > of cygwin (+ the x-window machinery, i.e the Cygwin/X installation as described in the installation > notes, with xlaunch, xinit, xorg-server etc.) (prior to mid-February 2015), it was working correctly. > Other programs using the X window system, such as ghostview for example, is working correctly on my installation. > I have seen on the Cygwin/X news that X server and X.Org X11 packages have been upgraded to newer versions, > and I was wondering if there was a known loss of backward compatibility with these fresh versions (even a > simple change, like in the DISPLAY variable or something like that) ? > > Best regards, > xflr6 > > -- > 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/ > > seeing similar behavior here after upgrading to: $ uname -a CYGWIN_NT-6.1-WOW xxx 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin It seems that the server is not opening the tcp/6000 port for remote connections. -- 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/