[ANNOUNCEMENT] Updated: freetype2-2.4.9-1
The following packages have been updated in the Cygwin distribution: *** freetype2-demos-2.4.9-1 *** libfreetype6-2.4.9-1 *** libfreetype-devel-2.4.9-1 FreeType 2 is a software font engine that is designed to be small, efficient, highly customizable and portable while capable of producing high-quality output (glyph images). This release includes bugfixes for security vulnerabilities CVE-2011-3439 and CVE-2012-1126 through -1144. -- 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/
Re: X server crash when running texworks
On 3/24/2012 3:47 PM, Ken Brown wrote: To reproduce: 1. Install texworks-0.4.3-1 from Cygwin Ports. 2. Create two tex files in your home directory, say test1.tex and test2.tex. I don't know if the contents matter, but in my case both files contain the following: \documentclass{article} \begin{document} Hello \end{document} 3. Start the X server by using the Start Menu shortcut. 4. Start texworks by typing "texworks&" in an xterm window. 5. Click on the "Open" icon to open one of the tex files. Then do the same to open the second. At this point the X server crashes and gives the message "Caught signal 11 (segmentation fault)". Server aborting." Before the crash I get the following warning in the xterm window when I open a file: QFileSystemWatcher: failed to add paths: /home/kbrown I don't know if this is significant.su I'm attaching cygcheck output and XWin.0.log. Ken P.S. I'm currently using the test version of xorg-server (1.12.0-1), but I can reproduce the crash with 1.11.4-5 also. Also, I'm currently testing the latest Cygwin snapshot. I just tried reverting to 1.7.11, and the X server still crashed, but not just from opening two files. I had to open and compile several tex documents before it happened. One further detail for anyone trying to reproduce this: I just tried it on a second computer, and my recipe didn't immediately produce the crash. But I simply started trying to use texworks (loading and compiling various tex documents), and the X server crashed within a few minutes. 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 26/03/2012 20:47, Ken Brown wrote: > On 3/24/2012 3:47 PM, Ken Brown wrote: >> To reproduce: >> >> 1. Install texworks-0.4.3-1 from Cygwin Ports. >> >> 2. Create two tex files in your home directory, say test1.tex and >> test2.tex. I don't know if the contents matter, but in my case both >> files contain the following: >> >> \documentclass{article} >> \begin{document} >> Hello >> \end{document} >> >> 3. Start the X server by using the Start Menu shortcut. >> >> 4. Start texworks by typing "texworks&" in an xterm window. >> >> 5. Click on the "Open" icon to open one of the tex files. Then do the >> same to open the second. >> >> At this point the X server crashes and gives the message "Caught signal >> 11 (segmentation fault)". Server aborting." >> >> Before the crash I get the following warning in the xterm window when I >> open a file: >> >> QFileSystemWatcher: failed to add paths: /home/kbrown >> >> I don't know if this is significant.su >> >> I'm attaching cygcheck output and XWin.0.log. >> >> Ken >> >> P.S. I'm currently using the test version of xorg-server (1.12.0-1), but >> I can reproduce the crash with 1.11.4-5 also. Also, I'm currently >> testing the latest Cygwin snapshot. I just tried reverting to 1.7.11, >> and the X server still crashed, but not just from opening two files. I >> had to open and compile several tex documents before it happened. > > One further detail for anyone trying to reproduce this: I just tried it on a > second computer, and my recipe didn't immediately produce the crash. But I > simply started trying to use texworks (loading and compiling various tex > documents), and the X server crashed within a few minutes. Thanks very much for the detailed report. On the off chance this is a known issue, would you mind downloading the X server symbols and getting a backtrace using the instruction on [1], before I try to reproduce it. [1] http://x.cygwin.com/devel/backtrace.html -- 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/26/2012 4:06 PM, Jon TURNEY wrote: On 26/03/2012 20:47, Ken Brown wrote: On 3/24/2012 3:47 PM, Ken Brown wrote: To reproduce: 1. Install texworks-0.4.3-1 from Cygwin Ports. 2. Create two tex files in your home directory, say test1.tex and test2.tex. I don't know if the contents matter, but in my case both files contain the following: \documentclass{article} \begin{document} Hello \end{document} 3. Start the X server by using the Start Menu shortcut. 4. Start texworks by typing "texworks&" in an xterm window. 5. Click on the "Open" icon to open one of the tex files. Then do the same to open the second. At this point the X server crashes and gives the message "Caught signal 11 (segmentation fault)". Server aborting." Before the crash I get the following warning in the xterm window when I open a file: QFileSystemWatcher: failed to add paths: /home/kbrown I don't know if this is significant.su I'm attaching cygcheck output and XWin.0.log. Ken P.S. I'm currently using the test version of xorg-server (1.12.0-1), but I can reproduce the crash with 1.11.4-5 also. Also, I'm currently testing the latest Cygwin snapshot. I just tried reverting to 1.7.11, and the X server still crashed, but not just from opening two files. I had to open and compile several tex documents before it happened. One further detail for anyone trying to reproduce this: I just tried it on a second computer, and my recipe didn't immediately produce the crash. But I simply started trying to use texworks (loading and compiling various tex documents), and the X server crashed within a few minutes. Thanks very much for the detailed report. On the off chance this is a known issue, would you mind downloading the X server symbols and getting a backtrace using the instruction on [1], before I try to reproduce it. OK, the backtrace is attached. Ken $ gdb --pid=5152 GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special) [...] Reading symbols from /usr/bin/XWin.exe...Reading symbols from /usr/lib/debug/usr/bin/XWin.dbg... warning: section .gnu_debuglink not found in /usr/lib/debug/usr/bin/XWin.dbg done. done. (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 6040.0x1ac] 0x004097c2 in NetWMToWinIconAlpha (icon=0xfed20010) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c:295 295 /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c: No such file or directory. in /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c (gdb) bt full #0 0x004097c2 in NetWMToWinIconAlpha (icon=0xfed20010) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c:295 hdc = ii = {fIcon = 1, xHotspot = 0, yHotspot = 0, hbmMask = 0xf050f17, hbmColor = 0x93051250} bmh = {bV4Size = 108, bV4Width = 512, bV4Height = -512, bV4Planes = 1, bV4BitCount = 32, bV4V4Compression = 3, bV4SizeImage = 0, bV4XPelsPerMeter = 0, bV4YPelsPerMeter = 0, bV4ClrUsed = 0, bV4ClrImportant = 0, bV4RedMask = 16711680, bV4GreenMask = 65280, bV4BlueMask = 255, bV4AlphaMask = 4278190080, bV4CSType = 0, bV4Endpoints = {ciexyzRed = {ciexyzX = 0, ciexyzY = 0, ciexyzZ = 0}, ciexyzGreen = {ciexyzX = 0, ciexyzY = 0, ciexyzZ = 0}, ciexyzBlue = {ciexyzX = 0, ciexyzY = 0, ciexyzZ = 0}}, bV4GammaRed = 0, bV4GammaGreen = 0, bV4GammaBlue = 0} width = height = 512 pixels = 0xfed20018 result = 0x2610b75 DIB_pixels = 0x4ff #1 NetWMToWinIcon (bpp=, icon=0xfed20010) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c:369 hasIconAlphaChannel = 1 versionChecked = 1 '\001' #2 0x0040a085 in winXIconToHICON (pWin=0x805399d8, iconSize=32) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-1/src/xserver-cygwin-1.12.0-1/hw/xwin/winmultiwindowicons.c:449 mask = image = imageMask = dst = src = iconPtr = maskPtr = planes = 1 bpp = 32 effBPP = i = biggest_size = 512 hDC = ii = {fIcon = 1969585604, xHotspot = 196958, yHotspot = 283154527, hbmMask = 0x0, hbmColor = 0x0} hints = {flags = 1969585433, input = 11, initial_state = 11, icon_pixmap = 0, icon_window = 4292791408, icon_x = 1969578512, icon_y = -2142004644, icon_mask = 1024, window_group = 4292791464} hIcon = 0x0 biggest_icon = _XA_NET_WM_ICON = 361 generation = 1 icon = icon_data = size = #3 0x0040a5be in winUpdateIcon (id=10487015) at /opt/wip/cygport-git/xorg-server/xorg