From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58721@debbugs.gnu.org
Subject: bug#58721: 28.2; dired with delete-by-moving-to-trash can't trash directory twice
Date: Fri, 28 Oct 2022 07:43:08 -0300 [thread overview]
Message-ID: <CAM9ALR_9aKt8C0a_8_pbKE8K8Cqur2_ykhrcZasFcNT+VFAE_Q@mail.gmail.com> (raw)
In-Reply-To: <83lep0jspb.fsf@gnu.org>
On Fri, 28 Oct 2022 at 04:47, Eli Zaretskii <eliz@gnu.org> wrote:
> This sounds very strange.
It baffles me too. Yet it still fails like clockwork here.
> Why would the failure depend on the size of
> the file/directory and on whether it does or doesn't cross
> filesystems? I see nothing in the code involved in this that could
> cause that.
Well, "crossing filesystems" and "large enough" are admittedly a
working hypothesis. I don't really know that's what makes it fail. I
just know that I could create other cases which do not fail, out of
these conditions.
I take this means you still cannot reproduce... I'm sorry, I don't
know what else I can try, I'm out of my depth here. Do you have
anything you'd like me to try? Can anyone else reproduce this, or is
it really just me?
> Perhaps on your system something happens in the
> background, due to one of the filesystems being encrypted or
> something?
The encrypted partition is open and mounted, as far as the system can
see, it is just another ext4 partition. More clearly, it cannot be
encryption per se, since the "/tmp/" folder is not encrypted at all,
it is just a tmpfs mount. It's fstab entry is:
tmpfs /tmp tmpfs nodev,nosuid,size=6G 0 0
Of course, it might still be "or something". But I don't do anything
out of the ordinary here that I'm aware of.
next prev parent reply other threads:[~2022-10-28 10:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 18:23 bug#58721: 28.2; dired with delete-by-moving-to-trash can't trash directory twice Gustavo Barros
2022-10-27 16:09 ` Eli Zaretskii
2022-10-27 17:07 ` Gustavo Barros
2022-10-27 17:22 ` Gustavo Barros
2022-10-27 17:30 ` Eli Zaretskii
2022-10-27 17:51 ` Gustavo Barros
2022-10-27 18:20 ` Eli Zaretskii
2022-10-27 18:41 ` Gustavo Barros
2022-10-27 19:04 ` Eli Zaretskii
2022-10-27 19:13 ` Gustavo Barros
2022-10-27 22:01 ` Gustavo Barros
2022-10-28 7:46 ` Eli Zaretskii
2022-10-28 10:43 ` Gustavo Barros [this message]
2022-10-28 11:44 ` Eli Zaretskii
2022-10-28 12:35 ` Gustavo Barros
2022-10-28 15:26 ` Stefan Kangas
2022-10-28 16:06 ` Gustavo Barros
2022-10-28 19:07 ` Gustavo Barros
2022-10-29 5:25 ` Mike Kupfer
2022-10-29 10:35 ` Gustavo Barros
2022-10-29 15:24 ` Mike Kupfer
2022-10-29 15:48 ` Eli Zaretskii
2022-10-29 16:32 ` Mike Kupfer
2022-10-29 16:56 ` Eli Zaretskii
2022-10-30 0:09 ` Mike Kupfer
2022-10-30 6:41 ` Eli Zaretskii
2022-10-30 17:40 ` Mike Kupfer
2022-10-30 18:02 ` Eli Zaretskii
2022-10-30 18:18 ` Mike Kupfer
2022-10-30 19:51 ` Eli Zaretskii
2022-10-30 22:20 ` Mike Kupfer
2022-10-30 23:10 ` Gustavo Barros
2022-10-31 0:01 ` Mike Kupfer
2022-10-31 0:23 ` Gustavo Barros
2022-10-31 12:49 ` Eli Zaretskii
2022-10-31 13:16 ` Gustavo Barros
2022-11-21 1:08 ` Mike Kupfer
2022-11-21 1:45 ` Gustavo Barros
2022-11-21 1:52 ` Mike Kupfer
2022-11-24 11:19 ` Eli Zaretskii
2022-11-24 11:28 ` Gustavo Barros
2022-10-27 19:07 ` Gustavo Barros
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM9ALR_9aKt8C0a_8_pbKE8K8Cqur2_ykhrcZasFcNT+VFAE_Q@mail.gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=58721@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.