Created attachment 441442 [details] emerge --info I'm observing this annoying behaviour on the first use of tramp when trying to open a file via 'su[do]' 1. Start emacs with $ emacs -Q -D -nw -nsl 2. C-x C-f (Find file) and start typing /su 3. then type ':'. Emacs hangs for some minutes -- C-g needed to abort. In graphical mode (i.e. no "-nw" option on the command line), several C-g are needed to resume, after which, sometimes tramps work correctly. The same happens when typing "/sudo" then ":". Starting with extra option --eval " (setq debug-on-error t debug-on-signal t) " spits out a backtrace (see attachment) exactly when typing ":".
Created attachment 441444 [details] tramp backtrace
Mmh, it also happens on '/ssh:'... Might be network-related...
WTF! Indeed it's a stupid DNS issue: my ISP redirects resolution failures to a dumb address which breaks tramp as, AFAIK, it uses a fake host name to expand/test connections, grrr. See: https://lists.gnu.org/archive/html/bug-gnu-emacs/2015-03/msg00203.html http://emacs.stackexchange.com/questions/18438/emacs-suspend-at-startup-ssh-connection-issue Reconfiguring networking with good DNS servers solves the problem :-) I don't know if there's anything that can be fixed on Emacs/tramp side up/downstream. Otherwise this bug would be invalid...
Upstream had some plans for asynchronous DNS resolution: https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00830.html I fear that we cannot do much about this at the distro level, because any changes would be very intrusive. Therefore resolving as UPSTREAM.