X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4C77D69C.7020800@cornell.edu> Date: Fri, 27 Aug 2010 11:15:40 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: cygwin Subject: Re: Emacs and DBUS References: <847hjvdyr9.fsf@aol.com> <4C667099.2020103@cornell.edu> <87mxsj69st.fsf@gmx.de> <4C6C2D11.8020003@cornell.edu> <87d3tf685q.fsf@gmx.de> <4C6C4BC8.9010400@cornell.edu> <87lj7vokyt.fsf@gmx.de> <4C74648F.2030203@cornell.edu> <87d3t7nzez.fsf@gmx.de> <4C75226F.9030005@cornell.edu> <4C752AAB.9000304@cornell.edu> <4C752F4F.60203@cornell.edu> <8762yyovon.fsf@gmx.de> <4C76C254.4040802@cornell.edu> <87occpyvsl.fsf@gmx.de> <4C77233A.1090504@cornell.edu> <871v9kbj02.fsf@gmx.de> <4C77CA9C.1090207@cornell.edu> In-Reply-To: <4C77CA9C.1090207@cornell.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 8/27/2010 10:24 AM, Ken Brown wrote: > On 8/27/2010 3:41 AM, Michael Albinus wrote: >> Ken Brown writes: >> >>>> This is also a D-Bus client, which connects to the *same* session bus as >>>> Emacs did due to $DBUS_SESSION_BUS_ADDRESS. Now you should see the >>>> signal sent by dbus-monitor in Emacs. >>> >>> OK, I started the session bus the right way this time, but I still >>> didn't see any signal from dbus-monitor in Emacs. I assume I should >>> have seen something in the echo area? >> >> Yes. You could test whether both Emacs and dbus-monitor use the same bus >> by reordering the calls: >> >> - apply dbus-launch as described >> - echo $DBUS_SESSION_BUS_ADDRESS >> - in *another* shell, set $DBUS_SESSION_BUS_ADDRESS to this value, and >> start dbus-monitor >> - start Emacs in the first shell, and load dbus.el. You shall see in >> the other shell output from dbus-monitor, telling that an application >> has started. It will also tell you the name of that application, like >> ":1.2". > > This doesn't happen. Is it possible that dbus.el doesn't complete its > initialization because the system bus isn't running? To partially answer my own question, I tried removing the line (dbus-init-bus :system) from dbus.el. The good news is that when I then load dbus.el, I do get the expected output from dbus-monitor. The bad news is that Emacs then behaves exactly as in the scenario where I start Emacs with the system bus running. Namely, it prints the trace 'xd_add_watch: fd 9' and then becomes unresponsive. All I can do is press C-g if I want to hear bells or C-x C-c to exit. I suspect we can't go any further with this until you return from your trip and start debugging. 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