R: cyggnome-menu-2.dll -- where to find?

--- Ven 12/11/10, nyc4bos ha scritto: > Hi, > > The binary /usr/bin/gnome-panel.exe needs > cyggnome-menu-2.dll: > > Window manager warning: Failed to read saved session file > /home/UserA/.config/me > tacity/sessions/10e53eb5dc683b6251289536169656875003710.ms: > Failed to op > en file

Re: g95 under cygwin

--- Ven 12/11/10, Larry Hall (Cygwin) ha scritto: > On 11/11/2010 9:02 PM, Monika > Pietrzyk wrote: > > Hello, > > > > > So, I have cygwin on my laptop. I've just installed > fortran compiler g95. On > > previous versions of cygwin I did not have problems > with the installation but > > now sth

Re: Installing new versions of vim doesn't uninstall old versions

On Thu, Nov 11, 2010 at 04:18:06PM -0500, Larry Hall (Cygwin) wrote: >On 11/11/2010 3:29 PM, Christopher Faylor wrote: >> On Thu, Nov 11, 2010 at 01:57:57PM -0500, Larry Hall (Cygwin) wrote: >>> On 11/11/2010 1:45 PM, Ren?? Berber wrote: On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote:

cyggnome-menu-2.dll -- where to find?

Hi, The binary /usr/bin/gnome-panel.exe needs cyggnome-menu-2.dll: Window manager warning: Failed to read saved session file /home/UserA/.config/me tacity/sessions/10e53eb5dc683b6251289536169656875003710.ms: Failed to op en file '/home/UserA/.config/metacity/sessions/10e53eb5dc683b6251289

Re: Python: subprocess running rsync causes broken socket in telnetlib

On Fri, Nov 12, 2010 at 16:26, David Antliff wrote: > On Fri, Nov 12, 2010 at 16:19, David Antliff wrote: >> Then the script uses subprocess to do something else (the line is >> actually longer than this but I've simplified it to the most basic >> version that exhibits the problem): >> >>    proce

Re: Python: subprocess running rsync causes broken socket in telnetlib

On Fri, Nov 12, 2010 at 16:19, David Antliff wrote: > Then the script uses subprocess to do something else (the line is > actually longer than this but I've simplified it to the most basic > version that exhibits the problem): > >    process = subprocess.Popen("rsync", stdout=subprocess.PIPE) FWI

Python: subprocess running rsync causes broken socket in telnetlib

I'm reporting a problem I see on Cygwin because I do not see the same behaviour on Ubuntu Linux - both systems are running Python 2.6.5. I have a script that opens a long-term telnet connection (telnetlib) to a remote host. There is an object called Telnet().socket that is created and represents a

Re: g95 under cygwin

On 11/11/2010 9:02 PM, Monika Pietrzyk wrote: Hello, Maybe someone can help me. I've installed a new version of cygwin (however without two packages, arj and csih, for they were causing terrible problems on my laptop, they were marked by Emsisoft Anti-Malware as trojans). Check'em with

g95 under cygwin

Hello, Maybe someone can help me. I've installed a new version of cygwin (however without two packages, arj and csih, for they were causing terrible problems on my laptop, they were marked by Emsisoft Anti-Malware as trojans). So, I have cygwin on my laptop. I've just installed fortran compiler

Re: How can autossh start remote connection, if computer is off?

Le 10/11/2010 02:38, David Rothenberger a écrit : > > On 11/9/2010 5:26 PM, cygwin.20.gyur...@spamgourmet.com wrote: >> How Can I do autossh connection with any computer which is off, but >> sometime coming to power on? >> I used this: >> cygrunsrv -I AutoSSH -n -O -u name -w pass -p /usr/bin/aut

Perl DateTime::Locale and Params::Validate woes

FYI - I spent all day figuring out a problem with installing the Perl module DateTime::Locale. Turns out that Reini's suggestion from long ago fixed it as described here: http://cygwin.com/ml/cygwin/2008-07/msg00144.html I was then able to install DateTime::Locale successfully. I later used cp

Re: Installing new versions of vim doesn't uninstall old versions

On 11 November 2010 18:45, René Berber wrote: > On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote: > >> On 11/11/2010 1:07 PM, Harrington, John wrote: >>> I recently had a problem with vim that was the result of my unwittingly >>> having two previous versions of vim in my /usr/bin.  Is it normal fo

bash-completion 1.2-1 breaks bash with tail -f

I've run into an issue with bash-completion v1.2-1.  After I tail -f a file and then press ctrl-c to stop tailing I can no longer see any text I type.  My text is being entered, just not being ... echoed back. This does not happen after uninstalling 1.2-1.  It also does not happen if I downgrad

bash-completion 1.2-1 breaks bash with tail -f

I've run into an issue with bash-completion v1.2-1. After I tail -f a file and then press ctrl-c to stop tailing I can no longer see any text I type. My text is being entered, just not being ... echoed back. This does not happen after uninstalling 1.2-1. It also does not happen if I downgrad

Re: Installing new versions of vim doesn't uninstall old versions

On 11/11/2010 3:29 PM, Christopher Faylor wrote: On Thu, Nov 11, 2010 at 01:57:57PM -0500, Larry Hall (Cygwin) wrote: On 11/11/2010 1:45 PM, Ren?? Berber wrote: On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote: On 11/11/2010 1:07 PM, Harrington, John wrote: I recently had a problem with vim

Re: Installing new versions of vim doesn't uninstall old versions

On Thu, Nov 11, 2010 at 01:57:57PM -0500, Larry Hall (Cygwin) wrote: >On 11/11/2010 1:45 PM, Ren?? Berber wrote: >> On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote: >> >>> On 11/11/2010 1:07 PM, Harrington, John wrote: I recently had a problem with vim that was the result of my unwittingly >

Re: Installing new versions of vim doesn't uninstall old versions

On 11/11/2010 1:45 PM, René Berber wrote: On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote: On 11/11/2010 1:07 PM, Harrington, John wrote: I recently had a problem with vim that was the result of my unwittingly having two previous versions of vim in my /usr/bin. Is it normal for the cygwin i

Re: Installing new versions of vim doesn't uninstall old versions

On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote: > On 11/11/2010 1:07 PM, Harrington, John wrote: >> I recently had a problem with vim that was the result of my unwittingly >> having two previous versions of vim in my /usr/bin. Is it normal for the >> cygwin installer not to delete or clobber t

Re: Installing new versions of vim doesn't uninstall old versions

On 11/11/2010 1:07 PM, Harrington, John wrote: I recently had a problem with vim that was the result of my unwittingly having two previous versions of vim in my /usr/bin. Is it normal for the cygwin installer not to delete or clobber the previous versions? I'm not sure what I did wrong, if anyt

Installing new versions of vim doesn't uninstall old versions

I recently had a problem with vim that was the result of my unwittingly having two previous versions of vim in my /usr/bin. Is it normal for the cygwin installer not to delete or clobber the previous versions? I'm not sure what I did wrong, if anything, in updating my cygwin installation. Be

Re: Typing trouble?

> At 10:24 AM 12/13/2000, Richard Dixon wrote: > > >Dear All, > > > >A novice's question here - just got Cygwin running using an older version > >(a 10MB-or-so executable containing all the relevant files). > > > >It seems to be OK in terms of running but when typing in the bash shell, > >there are

Re: perl debugger v5.10.1 in CYGWIN_NT-5.1 1.7.7(0.230/5/3) 2010/-08-31 -- is hanging

2010/11/10 Justin Amburn: > Perl debugger was working at one time, but it's not now. I've tried > searching google and cygin mailing list archives for a solution, but > there's not much on the matter. I renamed C:\cygwin to C:\cygwin.0 and > did a clean install of the latest version of Cygwin. The