Re: 1.14.0-2 XWin does not start, though 1.13.2.0 X Server latest snapshot 20130210-git works

2013-05-07 Thread Yaakov (Cygwin/X) 

On 2013-05-06 21:52, Vasiliy wrote:

- 1.14.0-2 XWin X Server installation is broken after replacing 1.13
in Cygwin (1.17.18 / 1.17.19s)


Do you have only a 3-button mouse?  If so, the issue is known and a fix 
is already queued up for 1.14.1-1.



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: 1.14.0-2 XWin does not start, though 1.13.2.0 X Server latest snapshot 20130210-git works

2013-05-07 Thread Jon TURNEY 
On 07/05/2013 03:52, Vasiliy wrote:
 - 1.14.0-2 XWin X Server installation is broken after replacing 1.13
 in Cygwin (1.17.18 / 1.17.19s)
 - no software interfering with Cygwin is installed
 - reinstalling xorg-server doesn't help
 - with the latest Cygwin snapshot (20130503) it might cause 1.14.0-2
 XWin core dump

Please try again with the Xserver 1.14.1-1 test release I uploaded today.

 XWin-backtrace.log contains:
 1.17.18-backtrace
 1.17.19s-backtrace (XWin.0.log)

Thanks for these.  Unfortunately these aren't as useful as they might be, due
to some recent change which the instructions at
http://x.cygwin.com/devel/backtrace.html haven't caught up with yet.

 $ gdb --args /usr/bin/XWin -multiwindow -wgl
 [...]
 Program received signal SIGSYS, Bad system call.
 CheckForShmSyscall () at /usr/src/debug/xorg-server-1.14.0-2/Xext/shm.c:188
 188 if (shmid != -1) {

When running the X server under gdb, to avoid stopping with SIGSYS when
checking if shared memory is available, either cygserver needs to be running,
or gdb needs to be told to not stop on SIGSYS with 'handle SIGSYS nostop'
before the program 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/

Fwd: 1.14.0-2 XWin does not start, though 1.13.2.0 X Server latest snapshot 20130210-git works

2013-05-07 Thread Vasiliy 
Works Just Fine For Me
http://cygwin.com/acronyms/#WJFFM

Thanks for the test release, and your suggestions.

Kind regards,
Vasiliy

PS. Please, update also the instructions at
http://x.cygwin.com/devel/backtrace.html

On Tue, May 7, 2013 at 6:35 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
 On 07/05/2013 03:52, Vasiliy wrote:
 - 1.14.0-2 XWin X Server installation is broken after replacing 1.13
 in Cygwin (1.17.18 / 1.17.19s)
 - no software interfering with Cygwin is installed
 - reinstalling xorg-server doesn't help
 - with the latest Cygwin snapshot (20130503) it might cause 1.14.0-2
 XWin core dump

 Please try again with the Xserver 1.14.1-1 test release I uploaded today.

 XWin-backtrace.log contains:
 1.17.18-backtrace
 1.17.19s-backtrace (XWin.0.log)

 Thanks for these.  Unfortunately these aren't as useful as they might be, due
 to some recent change which the instructions at
 http://x.cygwin.com/devel/backtrace.html haven't caught up with yet.

 $ gdb --args /usr/bin/XWin -multiwindow -wgl
 [...]
 Program received signal SIGSYS, Bad system call.
 CheckForShmSyscall () at /usr/src/debug/xorg-server-1.14.0-2/Xext/shm.c:188
 188 if (shmid != -1) {

 When running the X server under gdb, to avoid stopping with SIGSYS when
 checking if shared memory is available, either cygserver needs to be running,
 or gdb needs to be told to not stop on SIGSYS with 'handle SIGSYS nostop'
 before the program is started.

 --
 Jon TURNEY
 Volunteer Cygwin/X X Server maintainer


XWin.log
Description: Binary data


XWin.0.log
Description: Binary data
--
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/