From: krummm <krummm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Nautilus refresh bug
Date: Fri, 02 Jun 2023 14:22:05 +0200 [thread overview]
Message-ID: <20230602122205.NZGTKsV-ck9J5T5rrKcWgvtofzsUHvPAegpW4wg3Pkk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44089@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
Closed issue by krummm on void-packages repository
https://github.com/void-linux/void-packages/issues/44089
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.29_1 x86_64 GenuineIntel uptodate F
### Package(s) Affected
nautilus-44.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941
### Expected behaviour
Upon deleting selected files, Nautilus should refresh to reflect the correct state of the current directory.
### Actual behaviour
Upon deleting selected files in Nautilus, an equivalent amount of folders will disappear. The files that were chosen and moved to the trash bin will still appear in the directory, if one were to undo this operation the deleted files would appear to duplicate. Only upon a manual refresh will it update to reflect the correct state of the directory.
### Steps to reproduce
1. Create multiple files in a directory that is a parent of other directories
2. Drag to select the newly created files
3. Delete newly created files via either DEL key or context menu
prev parent reply other threads:[~2023-06-02 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 2:42 [ISSUE] " krummm
2023-05-26 2:49 ` krummm
2023-05-26 6:02 ` oreo639
2023-05-26 6:06 ` oreo639
2023-05-26 10:06 ` oreo639
2023-05-26 10:06 ` oreo639
2023-06-02 12:22 ` krummm
2023-06-02 12:22 ` krummm [this message]
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=20230602122205.NZGTKsV-ck9J5T5rrKcWgvtofzsUHvPAegpW4wg3Pkk@z \
--to=krummm@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).