X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <50BCEF59.9080005@cornell.edu> Date: Mon, 03 Dec 2012 13:28:41 -0500 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Jim Reisert AD1C CC: cygwin Subject: Re: Updated: emacs*-24.2.90-1 (TEST) References: <50BB4D0D DOT 7010204 AT cornell DOT edu> <50BBEBB1 DOT 2010400 AT cornell DOT edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown AT cornell DOT edu - Mon Dec 3 13:28:40 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 12/3/2012 12:53 PM, Jim Reisert AD1C wrote: > On Mon, Dec 3, 2012 at 10:48 AM, Jim Reisert AD1C > wrote: > >>> Yes, that's why you should have a D-Bus session daemon running before >>> starting emacs. >> >> And that's why I should read the entire release note. Working find now, thanks! > > I started emacs, exited, then started it again. the second time I got > this same stuff: > > (emacs:1672): GLib-WARNING **: In call to g_spawn_sync(), exit status > of a child process was requested but SIGCHLD action was set to SIG_IGN > and ECHILD was received by waitpid(), so exit status can't be > returned. This is a bug in the program calling g_spawn_sync(); either > don't request the exit status, or don't set the SIGCHLD action. > > ** (emacs:1672): WARNING **: Abnormal program termination spawning > command line `dbus-launch > --autolaunch=3f052ecf1e24145e3fdb40554f55370e --binary-syntax > --close-stderr': > > > Could the dBus daemon have crashed? I do see dbus stuff running in > the Windows 7 task manager. Let's keep this discussion on the list, because I'm sure there will be other people having trouble with the new dbus requirement. I doubt if the dbus daemon crashed. How did you start emacs the second time? Did you do it by typing `emacs' in an xterm window? If so, you shouldn't have gotten those error messages (assuming you started the D-Bus daemon the way I suggested in the release announcement). Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple