Path problem with xterm
If I open a bash terminal in cygwin, then I create an xterm (either by running startxwin.bat or by running the relevant lines from it manually) then I type set, my environment settings get listed. Among them is my current PATH variable. However, the displayed path is not the same as the path I had previously (in the bash terminal). Basically, it's the same path but with some extra entries added (most of these being duplicates of entries that were already present). Cygwin's 'startxwin.bat' does introduce some extra entries - but even if I comment them out I still end up with unwanted entries that look like they must either be getting added by Xwin or xterm. Can anyone suggest where they might be coming from, so I can see if I can get rid of them? Thanks, John -- 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: Path problem with xterm
- Original Message - From: Mike Ayers Subject: RE: Path problem with xterm Are you perhaps modifying PATH in .bashrc? No Mike, not as far as I can tell. In fact it's the original .bashrc that was installed with Cygwin. I haven't edited it and I can't see anything in it that refers to my path. :-( John -- 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/
startx command is not working
Hi, I am trying to install cygwin ,it is getting installedin the system,but the problem is when I type startx command .I am getting a fatal error and the error details in a fileare printed as follows Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.5.3.0 (20090205) Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running winDeinitMultiWindowWM - Noting shutdown in progress Thanks, Bindu -- 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: Path problem with xterm
On 9/24/2009 12:04 PM, John Emmas wrote: If I open a bash terminal in cygwin, then I create an xterm (either by running startxwin.bat or by running the relevant lines from it manually) then I type set, my environment settings get listed. Among them is my current PATH variable. However, the displayed path is not the same as the path I had previously (in the bash terminal). Basically, it's the same path but with some extra entries added (most of these being duplicates of entries that were already present). Cygwin's 'startxwin.bat' does introduce some extra entries - but even if I comment them out I still end up with unwanted entries that look like they must either be getting added by Xwin or xterm. Can anyone suggest where they might be coming from, so I can see if I can get rid of them? I think this was already answered in your other thread on this problem (http://cygwin.com/ml/cygwin/2009-09/msg00653.html): Most of the extra entries probably come from the various bash startup files (including /etc/profile). These startup files will be invoked every time you start a new bash login shell. You may also be getting some extra instances of /usr/bin because xterm is started in startxwin.bat with 'run -p /usr/bin'. I'm not sure about this. 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/
Emacs-GTK hangs with dialog boxes
For completeness, I want to flag that my GTK build of Emacs has the same problem described here: http://cygwin.com/ml/cygwin-xfree/2009-09/msg00051.html. Practically, after starting Emacs, $ G_SLICE=always-malloc emacs -q its first three icons on tool-bar (new file, read existing file, read directory) do not work. Emacs hangs for 20-30 seconds, and at prompt it writes: $ Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali I think that the problem happens after a recent (one or two weeks) upgrading of gtk | glib | GNOME libraries, when Emacs showed new icons. Cheers, Angelo. -- 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: Emacs-GTK hangs with dialog boxes
Angelo Graziosi ha scritto: For completeness, I want to flag that my GTK build of Emacs has the same problem described here: http://cygwin.com/ml/cygwin-xfree/2009-09/msg00051.html. Practically, after starting Emacs, $ G_SLICE=always-malloc emacs -q its first three icons on tool-bar (new file, read existing file, read directory) do not work. Emacs hangs for 20-30 seconds, and at prompt it writes: $ Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali I think that the problem happens after a recent (one or two weeks) upgrading of gtk | glib | GNOME libraries, when Emacs showed new icons. Using the current snapshot of cygwin1.dll (20090924, only dll) seems to solve *partially* the above problem: now it looks that the first three icons are working, but when I try to close Emacs, it hangs for some time. This happens only if I use those icons. Using 'ps' while Emacs is hanging, does not show the Emacs process any more but this 4036 13152 3716? 1006 01:56:54 /usr/lib/gamin/gam_server Cheers, Angelo. -- 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: Emacs-GTK hangs with dialog boxes
On 24/09/2009 18:35, Angelo Graziosi wrote: For completeness, I want to flag that my GTK build of Emacs has the same problem described here: http://cygwin.com/ml/cygwin-xfree/2009-09/msg00051.html. That has been fixed in the 20090920 snapshot. Practically, after starting Emacs, $ G_SLICE=always-malloc emacs -q its first three icons on tool-bar (new file, read existing file, read directory) do not work. Emacs hangs for 20-30 seconds, and at prompt it writes: $ Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali I think that the problem happens after a recent (one or two weeks) upgrading of gtk | glib | GNOME libraries, when Emacs showed new icons. I would try the latest snapshot; this may have been fixed there as well. Yaakov Cygwin/X -- 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: Emacs-GTK hangs with dialog boxes
On Thu, Sep 24, 2009 at 08:41:47PM -0500, Yaakov (Cygwin/X) wrote: On 24/09/2009 18:35, Angelo Graziosi wrote: For completeness, I want to flag that my GTK build of Emacs has the same problem described here: http://cygwin.com/ml/cygwin-xfree/2009-09/msg00051.html. That has been fixed in the 20090920 snapshot. Practically, after starting Emacs, $ G_SLICE=always-malloc emacs -q its first three icons on tool-bar (new file, read existing file, read directory) do not work. Emacs hangs for 20-30 seconds, and at prompt it writes: $ Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 Failed to connect to socket /tmp/fam-graziosi/fam- (emacs:3556): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali (emacs:3556): Gtk-WARNING **: Impossibile trovare il tipo di monitor predefinito per directory locali I think that the problem happens after a recent (one or two weeks) upgrading of gtk | glib | GNOME libraries, when Emacs showed new icons. I would try the latest snapshot; this may have been fixed there as well. I'm not aware of anything which would address this in the latest snapshot. cgf -- 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: Emacs-GTK hangs with dialog boxes
On 24/09/2009 20:47, Christopher Faylor wrote: I'm not aware of anything which would address this in the latest snapshot. The Failed to connect to socket error from GIO was, AFAICS, a fork() issue like the others plaguing GTK+, in this case a timeout from libfam waiting for the gam_server socket. 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: Emacs-GTK hangs with dialog boxes
On Thu, Sep 24, 2009 at 10:19:26PM -0500, Yaakov (Cygwin/X) wrote: On 24/09/2009 20:47, Christopher Faylor wrote: I'm not aware of anything which would address this in the latest snapshot. The Failed to connect to socket error from GIO was, AFAICS, a fork() issue like the others plaguing GTK+, in this case a timeout from libfam waiting for the gam_server socket. Right. The fork problem was fixed in the 20090920 snapshot. There was nothing fork-related in yesterday's snapshot. cgf -- 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/
