Re: Cannot launch ssh from X11 system tray icon
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 -- 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/
Re: X server crash when running texworks
On 28/03/2012 13:44, Ken Brown wrote: On 3/28/2012 8:28 AM, Ken Brown wrote: On 3/28/2012 7:16 AM, Jon TURNEY wrote: I'm afraid I can't reproduce your issue, but looking at the backtrace and the somewhat intermittent nature of the fault, I think perhaps this crash is caused by a race condition which exists in the conversion of the window icon from an X property to a Windows icon. I've uploaded a snapshot with some fixes for that at [1], perhaps you could try that out and see if it helps? [1] ftp://cygwin.com/pub/cygwinx/XWin.20120328-git-ab32650607c59327.exe.bz2 Yes, that seems to fix it. I just started texworks and compiled 6 or 7 tex documents without a crash. I've never been able to do more than 1 or 2 before. Good. I spoke too soon. I closed texworks and was doing other things (not even involving X to my knowledge), and the X server just crashed. I'm attaching XWin.0.log. 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. [1] ftp://cygwin.com/pub/cygwinx/XWin.20120329-git-6d4583d53c249549.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/
Re: X server crash when running texworks
On 3/29/2012 8:14 AM, Jon TURNEY wrote: On 28/03/2012 13:44, Ken Brown wrote: On 3/28/2012 8:28 AM, Ken Brown wrote: On 3/28/2012 7:16 AM, Jon TURNEY wrote: I'm afraid I can't reproduce your issue, but looking at the backtrace and the somewhat intermittent nature of the fault, I think perhaps this crash is caused by a race condition which exists in the conversion of the window icon from an X property to a Windows icon. I've uploaded a snapshot with some fixes for that at [1], perhaps you could try that out and see if it helps? [1] ftp://cygwin.com/pub/cygwinx/XWin.20120328-git-ab32650607c59327.exe.bz2 Yes, that seems to fix it. I just started texworks and compiled 6 or 7 tex documents without a crash. I've never been able to do more than 1 or 2 before. Good. I spoke too soon. I closed texworks and was doing other things (not even involving X to my knowledge), and the X server just crashed. I'm attaching XWin.0.log. 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). After I kill texworks, `ps' shows a dbus-daemon process and a dbus-launch process that weren't there before I started texworks, but maybe that's to be expected. 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/
Re: X server crash when running texworks
On 2012-03-29 14:59, Ken Brown wrote: 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. fork() errors? Are there any messages on the console? 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). After I kill texworks, `ps' shows a dbus-daemon process and a dbus-launch process that weren't there before I started texworks, but maybe that's to be expected. texworks uses QtDBus, so it needs a DBus session bus. If one isn't present (which nowadays you need for just about anything), it will start its own instance. If you are using multiwindow with startxwin, I strongly recommend adding the following to the beginning of your ~/.startxwinrc: eval `dbus-launch --sh-syntax` 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/
Re: X server crash when running texworks
On 3/29/2012 4:20 PM, Yaakov (Cygwin/X) wrote: On 2012-03-29 14:59, Ken Brown wrote: 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. fork() errors? Are there any messages on the console? Here's what I see in the xterm window from which I started texworks: $ QFileSystemWatcher: failed to add paths: /home/kbrown pdfTeX 3.1415926-2.3-1.40.12 (TeX Live 2011) kpathsea version 6.0.1 Copyright 2011 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Compiled with libpng 1.4.8; using libpng 1.4.8 Compiled with zlib 1.2.5; using zlib 1.2.5 Compiled with poppler version 0.18.2 Everything looks normal except for the QFileSystemWatcher message. When I do `ps' at this point, it shows a defunct pdftex process. 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). After I kill texworks, `ps' shows a dbus-daemon process and a dbus-launch process that weren't there before I started texworks, but maybe that's to be expected. texworks uses QtDBus, so it needs a DBus session bus. If one isn't present (which nowadays you need for just about anything), it will start its own instance. If you are using multiwindow with startxwin, I strongly recommend adding the following to the beginning of your ~/.startxwinrc: eval `dbus-launch --sh-syntax` I normally do this, but this time I had started the X server without my .startxwinrc for testing purposes. I've just restarted it in my normal way. I still get the texworks hang, but there are no longer extra dbus processes. So that 's not the issue. -- 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/
[ANNOUNCEMENT] Updated: fvwm-2.6.4-1
The following package has been updated for the Cygwin distribution: *** fvwm-2.6.4-1 Fvwm is a window manager for X11. It is designed to minimize memory consumption, provide a 3D look to window frames, and a virtual desktop. This is a long-overdue 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@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/
