Message-ID: <4CACC49B.1000008@cornell.edu>
Date: Wed, 06 Oct 2010 14:48:59 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: cygwin <cygwin@cygwin.com>
Subject: Re: emacs-23.2-3 and DBus
References: <844od1b8rx.fsf@aol.com> <4CAB2230.4090500@cornell.edu>	<877hhwiih3.fsf@gmx.de> <4CAB84CF.2010604@cornell.edu>	<8739skhs26.fsf@gmx.de> <4CAC73AF.1020209@cornell.edu>	<87ocb7mlhq.fsf@gmx.de> <4CACB32F.2070501@cornell.edu> <87y6abgqg3.fsf@gmx.de> <4CACBBFA.9040509@cornell.edu>
In-Reply-To: <4CACBBFA.9040509@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 10/6/2010 2:12 PM, Ken Brown wrote:
> On 10/6/2010 1:51 PM, Michael Albinus wrote:
>> Ken Brown writes:
>>
>>>> The binary has the following checksum:
>>>>
>>>> $ cksum /usr/bin/emacs
>>>> 658187514 16254990 /usr/bin/emacs
>>>
>>> That's not actually the binary; it's a symlink that resolves to either
>>> /usr/bin/emacs-X11.exe or /usr/bin/emacs-nox.exe, depending on whether
>>> or not you've installed the emacs-X11 package.  Is it possible that
>>> you upgraded the emacs package but are still using an old emacs-X11?
>>> If not, I don't know what the problem could be.  If you can't figure
>>> it out, you could try giving the command
>>>
>>>     cygcheck -svr>   cygcheck.out
>>>
>>> and sending the resulting cygcheck.out as an attachment.  Maybe I (or
>>> someone) will be able to spot something.
>>
>> I haven't the cygwin notebook with me, next access for me is tomorrow.
>> I'll check then.
>>
>> The only difference I could imagine is that I haven't started the system
>> bus; only the session bus was running. Could you, please, check with
>> your environment? Maybe there is still a problem.
>
> Yes, that's it.  Emacs does freeze if I load dbus.el and the system bus
> isn't running.  But the problem doesn't occur in a build of Emacs from
> the trunk.  I vaguely recall that someone reported this problem last
> summer, and you fixed it.  But maybe you only fixed it in the trunk, and
> not in the emacs-23 branch.  Do I remember that correctly?

Here's what I was thinking of:

   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6579

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