unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, 55832@debbugs.gnu.org
Subject: bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29
Date: Sat, 11 Jun 2022 19:46:08 +0000	[thread overview]
Message-ID: <87pmjft1vu.fsf@posteo.net> (raw)
In-Reply-To: <87fskbgfv7.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]


Michael Albinus <michael.albinus@gmx.de> writes:

> Thierry Volpiatto <thievol@posteo.net> writes:
>
> Hi Thierry,
>
>> Ah ok, I noticed I have always in ~/.emacs.d/tramp an UNKNOW entry for
>> uid and gid, is it normal?
>
> When the remote uid or gid cannot be determined, Tramp sets the default
> value "UNKNOWN" (for the uid-string resp. remote-gid property), and -1
> (for the uid-integer resp. gid-integer property). See
> tramp-unknown-id-string and tramp-unknown-id-integer.
>
> However, I would be surprised if these values are used for a "sudo"
> connection. Checking my own ~/.emacs.d/tramp I find such entries,
> indeed, for a "sudo" connection. Very strange. But although incorrect,
> they haven't disturbed my use of Tramp.
>
> After exiting Emacs, deleting ~/.emacs.d/tramp, and starting Emacs again
> with a "sudo" connection, there arer proper values "root" and 0 in the
> cached properties. Hmm, don't know where these values came from in
> history, but I don't believe they should disturb Tramp. But who
> knows. Perhaps you move the ~/.emacs.d/tramp file away (in order to use
> it later if necessary), start a new Emacs instance, and see, whether it
> still crashes with your scenario.

Will try this now.

>>> Sad. Since I cannot reproduce the problem locally, what happens if you
>>> invoke "emacs -Q" similar to how I've done?
>>
>> I can't reproduce the crash using helm -P path/to/emacs though there is
>> not much difference with my helm-find-files config, the difference comes
>> I guess from the usage of normal emacs (or possibly only -q) and emacs
>> -Q which affect tramp in some ways.
>>
>> What I would like to understand is why the crash appears AFTER
>> tramp-cleanup-all-connections and not before on first shot.
>
> Also a mystery to me.
>
> If the removing of the ~/.emacs.d/tramp file does not help, you might
> try the following settings:
>
> (setq tramp-verbose 10 tramp-debug-to-file t)

Ah nice, with those setting instead of crashing emacs hang and I can
recuperate with C-g, here the tramp log:

https://gist.github.com/thierryvolpiatto/96b5d3bacc92deac1fad275eede69354

Thanks.

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  reply	other threads:[~2022-06-11 19:46 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:16 bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29 Thierry Volpiatto
2022-06-07 16:08 ` Eli Zaretskii
2022-06-07 17:02   ` Thierry Volpiatto
2022-06-07 17:18     ` Eli Zaretskii
2022-06-07 18:33       ` Thierry Volpiatto
2022-06-07 18:53         ` Eli Zaretskii
2022-06-07 19:20   ` Thierry Volpiatto
2022-06-08 13:01     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-08 16:30     ` Eli Zaretskii
2022-06-08 18:17       ` Lars Ingebrigtsen
2022-06-08 18:25         ` Eli Zaretskii
2022-06-09 10:34           ` Lars Ingebrigtsen
2022-06-09 10:42           ` Thierry Volpiatto
2022-06-09 13:05             ` Eli Zaretskii
2022-06-09 15:18               ` Thierry Volpiatto
2022-06-09 15:29                 ` Lars Ingebrigtsen
2022-06-09 16:36                 ` Eli Zaretskii
2022-06-09 16:51                   ` Thierry Volpiatto
2022-06-09 17:48                     ` Eli Zaretskii
2022-06-09 18:28                       ` Thierry Volpiatto
2022-06-09 18:55                         ` Eli Zaretskii
2022-06-10  7:53                           ` Michael Albinus
2022-06-10 10:00                             ` Thierry Volpiatto
2022-06-10 12:20                               ` Michael Albinus
2022-06-11  6:14                                 ` Thierry Volpiatto
2022-06-11 19:27                                   ` Michael Albinus
2022-06-11 19:46                                     ` Thierry Volpiatto [this message]
2022-06-11 20:07                                       ` Michael Albinus
2022-06-11 20:12                                         ` Thierry Volpiatto
2022-06-12 18:16                                         ` Thierry Volpiatto
2022-06-14 11:39                                           ` Michael Albinus
2022-06-14 11:49                                             ` Thierry Volpiatto
2022-06-09 15:37               ` Thierry Volpiatto
2022-06-14 11:05 ` Michael Albinus
2022-06-14 11:36   ` Thierry Volpiatto
2022-06-14 11:44     ` Michael Albinus
2022-06-14 17:42 ` Michael Albinus
2022-06-16 17:27 ` Michael Albinus
2022-06-16 18:11   ` Thierry Volpiatto
2022-06-17 16:54     ` Michael Albinus
2022-06-17 17:10       ` Thierry Volpiatto
2022-06-19 14:25         ` Michael Albinus
2022-06-19 16:21           ` Thierry Volpiatto
2022-06-19 17:51             ` Michael Albinus
2022-06-21  8:24             ` Michael Albinus
2022-06-21  9:35               ` Thierry Volpiatto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmjft1vu.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=55832@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).