GNU bug report logs -
#31167
27.0.50; When the computer has no network connection, Emacs can take minutes to start
Previous Next
Reported by: Lars Ingebrigtsen <larsi <at> gnus.org>
Date: Sun, 15 Apr 2018 19:24:02 UTC
Severity: normal
Tags: wontfix
Found in version 27.0.50
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31167 in the body.
You can then email your comments to 31167 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Sun, 15 Apr 2018 19:24:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Lars Ingebrigtsen <larsi <at> gnus.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 15 Apr 2018 19:24:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
And that obviously sucks, especially when you're trying to set up a new
machine.
I think the way to reproduce this error is to have the network
configured, but not actually working. I suspect that Emacs is doing
some DNS stuff at startup that it shouldn't be doing.
In GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
of 2018-04-15 built on corrigan
Repository revision: 1ad6184c37a0e0f537688ea7d5e6ceca5f364eaa
Windowing system distributor 'The X.Org Foundation', version 11.0.11902000
System Description: Debian GNU/Linux 9 (stretch)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Sun, 15 Apr 2018 19:38:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 31167 <at> debbugs.gnu.org (full text, mbox):
Hm. Or has this finally been fixed, after all these years? I'm unable
to reproduce it now on my laptop, but perhaps I'm confing the network
"wrong" in the wrong way...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Sun, 15 Apr 2018 20:21:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 31167 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> I think the way to reproduce this error is to have the network
> configured, but not actually working. I suspect that Emacs is doing
> some DNS stuff at startup that it shouldn't be doing.
> Hm. Or has this finally been fixed, after all these years? I'm unable
> to reproduce it now on my laptop, but perhaps I'm confing the network
> "wrong" in the wrong way...
It sounds like this entry in etc/PROBLEMS
*** Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
This can happen if the system is misconfigured and Emacs can't get the
full qualified domain name, FQDN. You should have your FQDN in the
/etc/hosts file, something like this:
127.0.0.1 localhost
129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04
The way to set this up may vary on non-GNU systems.
According to this message from 2014 [1] it was resolved, and the
etc/PROBLEMS entry was removed. But the entry is still there in current
master.
[1]: https://lists.nongnu.org/archive/html/emacs-devel/2014-12/msg02313.html
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Sun, 15 Apr 2018 20:26:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 31167 <at> debbugs.gnu.org (full text, mbox):
Noam Postavsky <npostavs <at> gmail.com> writes:
> According to this message from 2014 [1] it was resolved, and the
> etc/PROBLEMS entry was removed. But the entry is still there in current
> master.
Hm... I remember running into this a couple of weeks ago on a Debian
jessie system, and the Emacs there is... let's see... 25.1.1. That's
after 2014, I think, so perhaps that explains why it returned?
vc-mode seems to say that it's been in etc/PROBLEMS since around
2001-2004.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Thu, 19 Apr 2018 00:26:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 31167 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
> According to this message from 2014 [1] it was resolved, and the
> etc/PROBLEMS entry was removed. But the entry is still there in current master.
That's due to a botched merge of etc/PROBLEMS in March 2015. Thanks for
mentioning it. I installed the attached patch into master to fix it.
> I remember running into this a couple of weeks ago on a Debian
> jessie system, and the Emacs there is... let's see... 25.1.1. That's
> after 2014
Yes, the problem that I fixed in 2014 should not be present in Emacs
25.1. Of course there could be some other problem with similar symptoms.
I can't reproduce the symptoms, though. I tried running Emacs master on
Fedora 27 with networking disabled (using Gnome's "Wired Connected >
Turn Off" UI), and Emacs started up fine.
[0001-Fix-botched-merge-of-FQDNs-in-PROBLEMS.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Mon, 23 Apr 2018 19:51:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 31167 <at> debbugs.gnu.org (full text, mbox):
Paul Eggert <eggert <at> cs.ucla.edu> writes:
>
>> I remember running into this a couple of weeks ago on a Debian
>> jessie system, and the Emacs there is... let's see... 25.1.1. That's
>> after 2014
>
> Yes, the problem that I fixed in 2014 should not be present in Emacs
> 25.1. Of course there could be some other problem with similar
> symptoms.
I was mistaken -- the system in question has Emacs 24.4.1 installed.
Does that version include your fix?
> I can't reproduce the symptoms, though. I tried running Emacs master
> on Fedora 27 with networking disabled (using Gnome's "Wired Connected
> > Turn Off" UI), and Emacs started up fine.
In those cases (where the system knows that it has lost the network
connection), then Emacs starts up fast. The problem is if the network
is up, but non-functional.
I've tried to reproduce it on a wired machine now just by pulling the
plug, but that didn't work, either. Hm...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Mon, 23 Apr 2018 20:00:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 31167 <at> debbugs.gnu.org (full text, mbox):
On 04/23/2018 12:50 PM, Lars Ingebrigtsen wrote:
> Paul Eggert <eggert <at> cs.ucla.edu> writes:
>
>>> I remember running into this a couple of weeks ago on a Debian
>>> jessie system, and the Emacs there is... let's see... 25.1.1. That's
>>> after 2014
>> Yes, the problem that I fixed in 2014 should not be present in Emacs
>> 25.1. Of course there could be some other problem with similar
>> symptoms.
> I was mistaken -- the system in question has Emacs 24.4.1 installed.
> Does that version include your fix?
No. So perhaps the problem is fixed after all.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#31167
; Package
emacs
.
(Mon, 23 Apr 2018 20:12:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 31167 <at> debbugs.gnu.org (full text, mbox):
Paul Eggert <eggert <at> cs.ucla.edu> writes:
> On 04/23/2018 12:50 PM, Lars Ingebrigtsen wrote:
>> Paul Eggert <eggert <at> cs.ucla.edu> writes:
>>
>>>> I remember running into this a couple of weeks ago on a Debian
>>>> jessie system, and the Emacs there is... let's see... 25.1.1. That's
>>>> after 2014
>>> Yes, the problem that I fixed in 2014 should not be present in Emacs
>>> 25.1. Of course there could be some other problem with similar
>>> symptoms.
>> I was mistaken -- the system in question has Emacs 24.4.1 installed.
>> Does that version include your fix?
>
> No. So perhaps the problem is fixed after all.
Yes.
But I've now tried reproducing this on a different machine with 24.4.1
(since the one I experienced the problem on is now a production server
:-)) and any combination of setting up bad routing tables, on the
machine itself and on the router, doesn't manage to trigger the
problem...
This is all so odd. I guess I have to make precise notes on what the
state of the networking is the next time I see this thing so that I can
test the same thing on a newer Emacs...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) wontfix; removed tag(s) moreinfo.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Wed, 09 Jan 2019 00:41:01 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
31167 <at> debbugs.gnu.org and Lars Ingebrigtsen <larsi <at> gnus.org>
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Wed, 09 Jan 2019 00:41:01 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 06 Feb 2019 12:24:15 GMT)
Full text and
rfc822 format available.
This bug report was last modified 6 years and 139 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.