Re: Cannot launch ssh from X11 system tray icon

2012-04-02 Thread Craig
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/



Re: [ANNOUNCEMENT] Updated: xorg-server-1.12.0-1 (TEST)

2012-04-02 Thread Jon TURNEY
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/



Re: X server crash when running texworks

2012-04-02 Thread Ken Brown

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

Re: X server crash when running texworks

2012-04-02 Thread Jim Reisert AD1C
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, jjreis...@alum.mit.edu, 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/



Re: X server crash when running texworks

2012-04-02 Thread Ken Brown

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 

Re: X server crash when running texworks

2012-04-02 Thread Yaakov (Cygwin/X)

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/