Re: X.org 7.4 dying under Geomview
I should add that after doing startx 21, the console error I'm seeing once I launch geomview from an xterm with ./geomview -run ../savi1.4.2/savi and the local Cygwin/X display crashes under Geomview is: xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on Xserver :0.0 xinit: connection to X server lost. /var/log/XWin.0.og doesn't show anything beyond 'XOpenDisplay () returned and successfully opened the display'. At Thursday 2/19/2009 09:11 AM +, Lloyd Wood wrote: I have also noticed that, in -multiwindow mode, graphical updates for Geomview's camera window now only happen for the area covered by the original camera position. That is, if you move the Windows window on screen, only the area of that window that overlaps with the area of original window content's position will be updated with new animations prompted by SaVi. (Rooted desktop drawing behaviour is fine. Either windowing mode crashes the Xserver after about 30 seconds of use of SaVi and Geomview.) This drawing behaviour is a regression in behaviour from the previous X multiwindow behaviour, where SaVi and Geomview animated fine. http://www.geomview.org/ http://savi.sf.net/ I'm using SaVi and Geomview under Cygwin/X and WinXP SP2 (a 2MB Thinkpad T43). See: http://savi.sf.net/ The new X server has a nasty habit of dying horribly when I begin using SaVi and Geomview - there's your test case. I can live without the hardware acceleration - it's a good way of tightening SaVi's geomview commands to remove redundant drawing and group drawing commands together to remove unnecessary geomview updates - but other geomview users will have a different view. And only getting thirty seconds or so of use before the X server dies and takes everything else with it is a showstopper for all of us. Geomview now seems to be easier to build under the new Xserver regime - ./configure and make just work and do the right thing without command-line nudges - but it's far less robust and reliable in use under the new X server. SaVi satellite constellation visualization: http://savi.sf.net/ http://www.ee.surrey.ac.uk/Personal/L.Wood/l.w...@surrey.ac.uk -- 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/
BLODA list
Hi, Is there any BLODA list ? If not I would like to start one and report that the following software is not compatible : Manufacturer : Logitech Process : LVComSrv.exe,LVPrcSvr.exe When I try to compile, everything starts to be very slow and sometimes sh crashs but as soon as I kill LVPrcSvr.exe, things are getting normal. My system : Windows XP SP3, Core2Duo E8200 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BLODA list
On Sat, 21 Feb 2009 13:23:57 +0100, Vincent R. foru...@smartmobili.com wrote: Hi, Is there any BLODA list ? If not I would like to start one and report that the following software is not compatible : Manufacturer : Logitech Process : LVComSrv.exe,LVPrcSvr.exe When I try to compile, everything starts to be very slow and sometimes sh crashs but as soon as I kill LVPrcSvr.exe, things are getting normal. My system : Windows XP SP3, Core2Duo E8200 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Forget to say that these COM services are used with Logitech QuickCam Pro 5000. I am using the latest version. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: BLODA list
On 2009-02-21 12:23Z, Vincent R. wrote: Is there any BLODA list ? Yes, it's in the FAQ: http://cygwin.com/faq/faq.using.html#faq.using.bloda and it includes this reference: Logitech webcam software with Logitech process monitor service to the dodgy app you mentioned. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.25-15 : Python interpreter hangs on Server 2k8 64-bit
Hi, I have a problem which I thought was fixed by release 1.5.25-11 : python 2.5.2 hangs at 100% CPU when launched without a script to obtain the interpreter prompt. It did not hang running scripts though. Python also crashes when trying to run the embedded web server from the Django framework, this may be related. My OS : Windows Server 2k8 64-bit Standard, SP1 What could it be this time? thanks, Joel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
wget, ssh, ssh-agent hang in socket_cleanup
Currently when using cygwin (other software works fine) to communicate over the network, some network connections will hang. This affects rsync, ssh, and wget (so far). I ran an strace on wget http://www.google.com and it hangs here (ssh hangs in the same place): Connecting to www.google.com|74.125.19.103|:80... 1870 2067824 [main] wget 214768 fhandler_console::write: 50 = write_c onsole (,..50) 3637 2071461 [main] wget 214768 cygwin_socket: socket (2, 1, 0) 3889 2075350 [main] wget 214768 fdsock: reset socket inheritance 2096 2077446 [main] wget 214768 build_fh_pc: fh 0x61169E10 1749 2079195 [main] wget 214768 fhandler_base::set_flags: flags 0x10002, supplied_bin 0x0 1920 2081115 [main] wget 214768 fhandler_base::set_flags: O_TEXT/O_BINARY set in flags 0x1 1825 2082940 [main] wget 214768 fhandler_base::set_flags: filemode set to binary 1968 2084908 [main] wget 214768 fdsock: fd 3, name '', soc 0x1FC 1763 2086671 [main] wget 214768 cygwin_socket: 3 = socket (2, 1, 0) 2374 2089045 [main] wget 214768 sig_send: sendsig 0x13C, pid 214768, signal -34, its_me 1 1844 2090889 [main] wget 214768 sig_send: wakeup 0x1F4 2028 2092917 [main] wget 214768 sig_send: Waiting for pack.wakeup 0x1F4 1818 2094735 [sig] wget 214768 wait_sig: signalling pack.wakeup 0x1F4 1961 2096696 [main] wget 214768 sig_send: returning 0x0 from sending signal -34 1801 2098497 [main] wget 214768 fhandler_socket::ioctl: socket is now nonblocking 2020 2100517 [main] wget 214768 fhandler_socket::ioctl: 0 = ioctl_socket (8004667E, 27C43C) 3710 2104227 [main] wget 214768 __set_errno: void __set_winsock_errno(const char*, int):234 val 119 2775 2107002 [main] wget 214768 __set_winsock_errno: connect:788 - winsock error 10036 - errno 119 2719 2109721 [main] wget 214768 cygwin_select: 4, 0x0, 0x27C3F0, 0x27C3D0, 0x0 2212 2111933 [main] wget 214768 dtable::select_write: fd 3 1774 2113707 [main] wget 214768 dtable::select_except: fd 3 2143 2115850 [main] wget 214768 cygwin_select: to NULL, ms 1763 2117613 [main] wget 214768 cygwin_select: sel.always_ready 0 1953 2119566 [main] wget 214768 start_thread_socket: Handle 0x1FC 1754 2121320 [main] wget 214768 start_thread_socket: Added to writefds 1931 2123251 [main] wget 214768 start_thread_socket: Added to exceptfds 2250 2125501 [main] wget 214768 start_thread_socket: opened new socket 0x208 1923 2127424 [main] wget 214768 start_thread_socket: exitsock 0x208 1810 2129234 [main] wget 214768 start_thread_socket: stuff_start 0x27C354 2635 2131869 [select_socket] wget 214768 cygthread::stub: thread 'select_socket', id 0x3421C, stack_ptr 0x1B2FCDA0 1790 2133659 [select_socket] wget 214768 thread_socket: stuff_start 0xF5582C 3188 2136847 [select_socket] wget 214768 thread_socket: Win32 select returned 1 2146 2138993 [select_socket] wget 214768 thread_socket: s 0xF527E8, testing fd 3 () 5712 2144705 [main] wget 214768 select_stuff::wait: m 2, ms 4294967295 5 2144710 [select_socket] wget 214768 thread_socket: write_ready 3987 2148697 [main] wget 214768 select_stuff::wait: woke up. wait_ret 1. verifying 2044 2150741 [main] wget 214768 select_stuff::wait: gotone 1 2042 2152783 [main] wget 214768 select_stuff::wait: returning 0 1853 2154636 [main] wget 214768 select_stuff::cleanup: calling cleanup routines 2033 2156669 [main] wget 214768 socket_cleanup: si 0xF52818 si-thread 0x61106F30 2254 2158923 [main] wget 214768 socket_cleanup: sent a byte to exitsock 0x208, res -1 2038 2160961 [main] wget 214768 socket_cleanup: reading a byte from exitsock 0x208 For reasons I can't really guess at, wget works 3/4 times, ssh only 1/3 times. I can get through by pressing CTRL-C and re-running the command (sometimes I have to do this several times), except with rsync which seems to trap the CTRL-C and I have to kill it using the Task Manager before it will stop and I can try again. This also affects ssh-add which seems to hang trying to connect to the ssh-agent on localhost, so it's not related to connecting to other machines. This is something that started happening recently, in the last few weeks. Windows Update has run a few times and I thought it may have updated my network driver; however, after I observed this problem I used Windows Update to install a network card driver update, which didn't fix (or worsen) the problem. Also, the fact that this affects connections to localhost, which theoretically would bypass the network card driver, seems to discredit the network card driver theory and cast suspicion on the entire networking stack instead. This only affects cygwin, so far, though ... so maybe it's something funny cygwin is doing. I'm running Windows Vista Home Basic 64-bit, the network card is a Realtek PCI-E GB NIC. Any ideas? I'm not really sure where to go next with this, my best idea right now is to try reinstalling windows since reinstalling cygwin didn't fix it... any help will be appreciated! -- View this message in context:
Re: Help with cygheap base mismatch on Vista 32-bit
Dave Korn wrote: Ari Halberstadt wrote: Every program I've tried in my cygwin installation (1.5.25-15) gives base mismatch errors on my Vista Home Premium 32-bit system. Cygwin was BitDefender seems to break Cygwin. There's a detailed explanation of how AV and firewall apps can sometimes cause problems for Cygwin at BitDefender was indeed breaking cygwin. Thanks to Dave's answer, I uninstalled BitDefender and am now running a trial version of Kaspersky, which seems to mostly work with cygwin, though it did hang once on a find command. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
