Files issueshttps://gitlab.gnome.org/GNOME/nautilus/-/issues2024-03-09T09:26:27Zhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/3349Default applications for filetype not respected2024-03-09T09:26:27ZKuba OrlikDefault applications for filetype not respected### Affected version
GNOME Shell 45.4
Arch Linux
Xorg and Wayland
Also happens without extensions
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Open the "Default Apps" settin...### Affected version
GNOME Shell 45.4
Arch Linux
Xorg and Wayland
Also happens without extensions
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Open the "Default Apps" settings pane
2. Set the default app for opening pictures to Viewnior (for example)
3. Go to Nautilus
4. Find a picture and right-click it
5. Use the context menu to open the picture with Gimp (a different app than in step 2)
6. Close Gimp
7. Doubleclick the picture file
### What happened
It opens in Gimp
### What did you expect to happen
Should've opened in my default app - Viewnior. The default choice is still visible and unchanged in the "Default Apps" settings pane
![Screencast_from_2024-03-05_17-17-57](/uploads/7ed324ae38795f5000c4521f0e0251e3/Screencast_from_2024-03-05_17-17-57.webm)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/3338Search in 46: can't filter files only in a current folder without recursion2024-02-29T20:54:10Zdarkblaze69Search in 46: can't filter files only in a current folder without recursion* OS: Arch
* nautilus from main 46 beta+
I am now confused how the search working in nautilus. It now always searches recursively. Although there's 'Search current folder', it just resets my search, and if I type after that, it searches...* OS: Arch
* nautilus from main 46 beta+
I am now confused how the search working in nautilus. It now always searches recursively. Although there's 'Search current folder', it just resets my search, and if I type after that, it searches recursively again.
In 45 I found it superconvenient to filter out all the needed files in the current folder. And then if I want there was 'Search everywhere' button.
But now it shows all the files recursively through all subfolders and I found no way to limit to only a folder. There's the X button to stop process but when clicked it will be late and the result will be spoiled by unneeded subfolders.
I would say it is very critical for me to get the files only in a folder without subfolders. IMHO this should be a basic functionality available, and recursion should be optional.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3319[abrt] nautilus: g_type_check_instance_is_fundamentally_a(): nautilus killed ...2024-02-28T10:21:06ZAndré Monteiro[abrt] nautilus: g_type_check_instance_is_fundamentally_a(): nautilus killed by SIGSEGV# Affected Version
- Version: nautilus-44.0-1.fc38
- Distribution: Fedora 38 workstation x86_64
- Also happens with development version: ?
Version-Release number of selected component:\
nautilus-44.0-1.fc38
Additional info:\
reporter...# Affected Version
- Version: nautilus-44.0-1.fc38
- Distribution: Fedora 38 workstation x86_64
- Also happens with development version: ?
Version-Release number of selected component:\
nautilus-44.0-1.fc38
Additional info:\
reporter: libreport-2.17.9\
type: CCpp\
reason: nautilus killed by SIGSEGV\
journald_cursor: s=9e72d5632b574a7384472e6604e0d57c;i=12afff;b=915f1a9d532f42eaa555d3f91d98597b;m=7c9fd6e57;t=5f89ea38e8eee;x=4bfebd2cebe9e675\
executable: /usr/bin/nautilus\
cmdline: /usr/bin/nautilus --gapplication-service\
cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Nautilus\
rootdir: /\
uid: 1000\
kernel: 6.2.9-300.fc38.x86_64\
package: nautilus-44.0-1.fc38\
runlevel: N 5\
backtrace_rating: 4\
crash_function: g_type_check_instance_is_fundamentally_a
Truncated backtrace:\
Thread no. 1 (13 frames)\
0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:4167\
1 g_value_set_object at ../gobject/gobject.c:4509\
2 object_get_property at ../gobject/gobject.c:1780\
3 g_object_get_valist at ../gobject/gobject.c:2909\
4 g_object_get at ../gobject/gobject.c:3006\
5 nautilus_view_cell_get_view at ../src/nautilus-view-cell.c:165\
6 on_item_click_stopped at ../src/nautilus-list-base.c:432\
7 \_g_closure_invoke_va at ../gobject/gclosure.c:895\
10 \_gtk_gesture_click_stop at ../gtk/gtkgestureclick.c:113\
11 \_double_click_timeout_cb at ../gtk/gtkgestureclick.c:125\
15 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276\
16 g_main_context_iteration at ../glib/gmain.c:4343\
17 g_application_run at ../gio/gapplication.c:2573
# Additional Information
As requested by fedora admin, this bug https://bugzilla.redhat.com/show_bug.cgi?id=2184849 has been filled upstream here.https://gitlab.gnome.org/GNOME/nautilus/-/issues/7Drag'n'dropping a folder randomly copies instead of moving2024-01-23T08:11:26ZJan Niklas HasseDrag'n'dropping a folder randomly copies instead of movingSteps to reproduce:
1. open a nautilus window and navigate to a folder A that contains several folders
2. open another nautilus window and navigate to another folder B
3. drag a folder from folder A to folder B
4. repeat step 3 several t...Steps to reproduce:
1. open a nautilus window and navigate to a folder A that contains several folders
2. open another nautilus window and navigate to another folder B
3. drag a folder from folder A to folder B
4. repeat step 3 several times
Expected: given that folders A and B are on the same physical filesystem, all folders dragged and dropped should be MOVED, not copied. If A and B were on different physical disks, then all draggged and dropped folders should be systematically copied, but this is not the case.
Observed: some folders get moved, as expected, but some others, randomly, get copied instead. If you then delete the copy and repeat the exact same drag-n-drop operation, most of the times it will be moved, as expected. That is, the behavior is completely random.
Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=742463https://gitlab.gnome.org/GNOME/nautilus/-/issues/3054[Crash] Files crashes while copying from Google Drive2024-01-19T02:09:55ZBineeth CR[Crash] Files crashes while copying from Google DriveCrashing app: Files (Nautilus), Version: 44.2
Distribution: OpenSUSE Tumbleweed
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Copy some large files (> 500 MB in size) from Goo...Crashing app: Files (Nautilus), Version: 44.2
Distribution: OpenSUSE Tumbleweed
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Copy some large files (> 500 MB in size) from Google Drive
2. Paste it into one of the secondary hard disk drives (mine has 7200 RPM as speed).
3. Try to copy some more large files (> 500 MB in size) to the same drive
4. Parallely run Brasero to burn some large files (> 4 GiB) to a Data DVD.
# Current behavior
The Files app is crashing and all the windows suddenly disappear!
I observed the same crash while I tried to relaunch the app and open a new window by pressing the Ctrl+N shortcut.
The issue is random. Sometimes it works fine. Sometimes it just crashes and all the windows close.
Also, I observed this issue while using Brasero to burn some files to a Data DVD.
# Expected behavior
The Files app should be resilient and should not crash.
It would be great if it could auto-recover, even though there is a crash.
# Additional information
Stack trace: [Nautilus-Crash](/uploads/ce0dd22b970f893d0a10dbcf20f33fed/Nautilus-Crash)
System information: [system-information.txt](/uploads/8bef8ac160026608fc3d692e10613450/system-information.txt)
Brasero version: ![image](/uploads/895ecc4f3355f70122f09bea805c596f/image.png)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2958AFP netmounts in limbo after timeout.2024-01-18T11:17:15ZSorenAFP netmounts in limbo after timeout._(not sure if a bug / if fixable or even intended behavior)_
In our work, we use a mixed setup of OSX and Linux laptops and Linux office servers. We use AFP netmounts to access files on the projects shared spaces. Using a Linux machine ..._(not sure if a bug / if fixable or even intended behavior)_
In our work, we use a mixed setup of OSX and Linux laptops and Linux office servers. We use AFP netmounts to access files on the projects shared spaces. Using a Linux machine (Ubuntu 22.04 using GNOME), these time out a while after the screensaver hits and okay.
When unlocking again, they are in a sort of limbo (on the local machine / work laptop). Files/Nautilus seems to not recognize the timeout and often crashes on attempts to access the previously mounted shares or starts to work on "something". Closing Files does not always fix it.
The only reliable solution so far is:
> killall gvfsd
> killall nautilushttps://gitlab.gnome.org/GNOME/nautilus/-/issues/3267Unable to open folders with huge number of files2024-01-17T11:37:03ZFred TUnable to open folders with huge number of files
- Version : 43.2
- Distribution : Debian 12.2
- Did not test development version
# Steps to reproduce
- have a folder with huge number of files on local disk, for example images in Coco Train Dataset 2017 (~118 000 files) (I encounter...
- Version : 43.2
- Distribution : Debian 12.2
- Did not test development version
# Steps to reproduce
- have a folder with huge number of files on local disk, for example images in Coco Train Dataset 2017 (~118 000 files) (I encounter the bug on this dataset)
- open folder in nautilus in 'List mode', it works quite well in 'Thumbnails mode'
- nautilus freezes
# Expected behavior
Display the list of present files in folder in a reasonable delay (<30s).
As comparison, Midnight Commander opens the same folder in less than 1s.
# Actual behavior
On my computer (Bi-Xeon Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz, 32Go RAM), Nautilus freezes for more than 15m (I killed it each time after this delay).
In the same time, it's impossible to open a new Nautilus window when the other window freezes.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3182Nautilus file window consumes shift key event2023-11-30T11:43:29ZJott WeeNautilus file window consumes shift key event# Affected Version
- Version: 44.2.1
- Distribution: Fedora 38
# Steps to reproduce
1. Have right Shift key as global push-to-talk button for Discord
2. Have a file window opened
3. Press right shift key to talk
# Expected Behavior
Dis...# Affected Version
- Version: 44.2.1
- Distribution: Fedora 38
# Steps to reproduce
1. Have right Shift key as global push-to-talk button for Discord
2. Have a file window opened
3. Press right shift key to talk
# Expected Behavior
Discord receives shift key event and you can talk
# Actual Behavior
Nothing happens as Nautilus seems to suppress/consume the shift key eventhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/3192crash when open as root and trying ot edit any directory property2023-11-25T17:10:17ZSwrowar hossaoncrash when open as root and trying ot edit any directory property<!--
Please test if the issue has already been fixed by installing the latest testing version.
It can be installed alongside the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/se...<!--
Please test if the issue has already been fixed by installing the latest testing version.
It can be installed alongside the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in the Terminal or Console app:
flatpak install --from https://nightly.gnome.org/repo/appstream/org.gnome.NautilusDevel.flatpakref
3. Launch the development version (normal Files logo with yellow and black stripes), e.g. with:
flatpak run org.gnome.NautilusDevel
-->
# Affected Version
- Version: 45.rc
- Distribution: Ubuntu 23.10
- Happens with development Flatpak: No
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
1. open the terminal
2. sudo nautilus any/dir or . for current dir path
3. right click of a directory got to properties edit permission it should work properly
# Expected Behavior
i wish i can open any directory as root easily and modify the permissions from the properties section
# Actual Behavior
when i am open any directory as root and go to the properties section its crashing
# Additional Information
if anyone add a option to open as root from the GUI eg (open as root)
**here is some log i have got from my terminal**
```
╰─$ sudo nautilus /opt/lampp/
[sudo] password for shuvo:
** Message: 22:04:16.439: Connecting to org.freedesktop.Tracker3.Miner.Files
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.552: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.552: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.552: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): libunity-CRITICAL **: 22:04:16.555: file unity-launcher.c: line 1638: unexpected error: Failed to execute child process “dbus-launch” (No such file or directory) (g-exec-error-quark, 8)
(org.gnome.Nautilus:93585): libunity-CRITICAL **: 22:04:16.555: unity_launcher_entry_dbus_impl_construct: assertion 'conn != NULL' failed
(org.gnome.Nautilus:93585): libunity-CRITICAL **: 22:04:16.559: unity-inspector.vala:96: Unable to connect to session bus: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): Gtk-WARNING **: 22:04:16.563: Unable to acquire session bus: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.604: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.604: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:93585): GLib-GIO-CRITICAL **: 22:04:16.664: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
(org.gnome.Nautilus:93585): GLib-GIO-CRITICAL **: 22:04:16.664: g_dbus_proxy_get_connection: assertion 'G_IS_DBUS_PROXY (proxy)' failed
(org.gnome.Nautilus:93585): GLib-GIO-CRITICAL **: 22:04:16.664: g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.664: Error creating proxy Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.664: Error creating proxy Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.664: Error creating proxy Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.664: Unable to create connection for session-wide Tracker indexer: Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.665: Unable to get contents of the bookmarks file: Error opening file /root/.gtk-bookmarks: No such file or directory
** (org.gnome.Nautilus:93585): WARNING **: 22:04:16.665: Unable to get contents of the bookmarks file: Error opening file /root/.gtk-bookmarks: No such file or directory
** (org.gnome.Nautilus:93585): CRITICAL **: 22:04:16.728: update_dbus_opened_locations: assertion 'dbus_object_path' failed
(org.gnome.Nautilus:93585): dconf-WARNING **: 22:04:16.729: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
[1] 93583 segmentation fault sudo nautilus /opt/lampp/
```https://gitlab.gnome.org/GNOME/nautilus/-/issues/3157Folder content size is displayed like "3,..."2023-11-25T00:25:16ZArkadiusz BulskiFolder content size is displayed like "3,..."# Affected Version
- Version: 44.2.1
- Distribution: Ubuntu 23.04 (existed in previous release as well)
- Happens with development Flatpak: dont know what that is
# Steps to reproduce
1. Select a folder (directory) that has some conte...# Affected Version
- Version: 44.2.1
- Distribution: Ubuntu 23.04 (existed in previous release as well)
- Happens with development Flatpak: dont know what that is
# Steps to reproduce
1. Select a folder (directory) that has some content in it.
2. Right click and Properties or just use CTRL- I
3. Look at the line below folder's name that says "10 000 elements of total size 3,..." etc
4. Resizing the window does not help one bit.
# Expected Behavior
It should provide a correct amount, in GB or whatever...
# Actual Behavior
...and not "6,5..." or "3,..."
# Additional Information
Screenshot attached.
![Zrzut ekranu z 2023-10-30 19-23-57a.png](/uploads/6515459de796dfd592433976a78275c7/Zrzut_ekranu_z_2023-10-30_19-23-57a.png)https://gitlab.gnome.org/GNOME/nautilus/-/issues/3188Nautilus crashes after search2023-11-21T15:45:59Zcezerim pendikNautilus crashes after search# Affected Version
- Version: 42.6
- Distribution: Ubuntu 22.04
- Happens with development Flatpak: No
# Steps to reproduce
1. Anytime i search for folder, file manager freezes. İ tryed opening nautilus in debug mode so i can see erro...# Affected Version
- Version: 42.6
- Distribution: Ubuntu 22.04
- Happens with development Flatpak: No
# Steps to reproduce
1. Anytime i search for folder, file manager freezes. İ tryed opening nautilus in debug mode so i can see errors. But its just freezes so asks me to wait or force exit. When i force exit the terminal for debug just returns "killed".
# Expected Behavior
Not to freeze so i can search
# Actual Behavior
Freezes so i cant search
# Additional Informationhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/2642Samba Link Shows Empty Folder2023-11-10T23:15:44Zjasker5183Samba Link Shows Empty Folder# Affected version
- Nightly flatpak: Maybe? Still waiting for it to happen.
- Other: Fedora 37 and Nautilus 43.0-2.fc37
# Steps to reproduce
1. Mount Samba share.
2. Go back to bookmarked Samba root folder link and mount another Samba...# Affected version
- Nightly flatpak: Maybe? Still waiting for it to happen.
- Other: Fedora 37 and Nautilus 43.0-2.fc37
# Steps to reproduce
1. Mount Samba share.
2. Go back to bookmarked Samba root folder link and mount another Samba share.
3. Shows "empty folder".
# Current behavior
Been experiencing this issue since around Fedora 31 (possibly before) [Link to Bugzilla issue](https://bugzilla.redhat.com/show_bug.cgi?id=1891358). It happens at least once per boot and despite trying to debug GVFS I still cannot figure out what is causing this problem. To date my current "fix" is to `pkill gvfs` but that does lead to problems if I'm using content on the server.
# Expected behavior
Bookmarked link shows contents of folder.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/3171Banner with "Empty Trash" button missing from trash folder2023-11-09T16:39:11ZUrtsi SantsiBanner with "Empty Trash" button missing from trash folder<!--
Please test if the issue has already been fixed by installing the latest testing version.
It can be installed alongside the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/se...<!--
Please test if the issue has already been fixed by installing the latest testing version.
It can be installed alongside the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in the Terminal or Console app:
flatpak install --from https://nightly.gnome.org/repo/appstream/org.gnome.NautilusDevel.flatpakref
3. Launch the development version (normal Files logo with yellow and black stripes), e.g. with:
flatpak run org.gnome.NautilusDevel
-->
# Affected Version
- Version: 45.1 (nautilus-45.1-1.fc39)
- Distribution: Fedora Workstation 39
- Happens with development Flatpak: No
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
Open trash folder that contains something.
# Expected Behavior
There is a banner with "Empty Trash..." button or another way to easily empty the trash folder.
# Actual Behavior
Banner with "Empty Trash..." button missing from trash folder.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3046folder-color-nautilus causes nautilus 44.2.1 to not open2023-11-03T12:45:52ZJean-Christophe Sekingerjcs@aquilenet.frfolder-color-nautilus causes nautilus 44.2.1 to not open# Affected version
- Nightly flatpak: can’t install folder-color in it
# Current behavior
in Manjaro, gnome 44.3, Files 44.2.1, with folder-color-nautilus 0.3.2-1 (in aur) or folder-color-nautilus-git r42.61382f2-1, doesn’t start.
if...# Affected version
- Nightly flatpak: can’t install folder-color in it
# Current behavior
in Manjaro, gnome 44.3, Files 44.2.1, with folder-color-nautilus 0.3.2-1 (in aur) or folder-color-nautilus-git r42.61382f2-1, doesn’t start.
if I uninstall it, Files start, each time.
# Questions
Is there any workaround/solution ?
# Additional information
I wrote [an issue ](https://github.com/costales/folder-color/issues/28)in https://github.com/costales/folder-color/issues/28#issuecomment-1663414182
Costales answered:
<table>
<tr>
<td>
[@jcsekinger](https://github.com/jcsekinger) I would say it's a Nautilus issue, not a Folder Color issue...
</td>
</tr>
</table>https://gitlab.gnome.org/GNOME/nautilus/-/issues/3102Sorting Search results by any data column2023-11-01T12:07:31ZVojtech SlavnikSorting Search results by any data column# Affected version
- All Nautilus versions.
### Use cases
Searching for a file, but unable to SORT search results
### Available features and workarounds
quit using Nautilus and install alternative file managers
### Difficulties and in...# Affected version
- All Nautilus versions.
### Use cases
Searching for a file, but unable to SORT search results
### Available features and workarounds
quit using Nautilus and install alternative file managers
### Difficulties and insufficiencies
<!-- Why is the current experience unsatisfying? -->
SORTING SEARCH RESULTS is a basic feature that file managers have been able to do dating back to the DOS days prior to Windows OS. Without the ability to sort by type or by location or by modification or creation date leaves the person doing the search unable to find what they are looking for. To put it bluntly: NAUTILUS IS ALMOST USELESS 90% OF THE TIME.
### Suggested enhancements
Go back to the DOS days and at least add the SORT capability. Adding a filter capabilty would be bring it's search into the 21st century.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2300Let the user choose a default MIME types handler2023-10-27T02:33:43ZMaksym HazevychLet the user choose a default MIME types handlerCurrently, when you install an application that can handle a certain MIME type, it becomes the default handler. The bailing point for me is when I install [HandBrake](https://handbrake.fr/), a tool to convert video files, and it becomes ...Currently, when you install an application that can handle a certain MIME type, it becomes the default handler. The bailing point for me is when I install [HandBrake](https://handbrake.fr/), a tool to convert video files, and it becomes the default for many video formats, instead of [VLC](https://www.videolan.org/vlc/) — even though it's the default application for Video category. While this could be fixed by disallowing to automatically override MIME types associated with a category — this solution wouldn't work for everything. Instead, inspired by how Android does things, I believe the following behavior would work better:
1. If no application can open the resource, propose to look for one in Software (already implemented afaik)
0. If there is one application or the default one is set, use it
0. If a new application becomes available, prompt to choose one and set it as the default (having the "Open once" button seems redundant)
0. If the default application is unavailable (e.g., deleted), start at 1
And to make everything more transparent, it would be great to notify users when the just-installed application is set to be the default handler of a certain MIME types category (that would be if there is no default one). And if there already is a default application — instead, prompt to choose which one to use.https://gitlab.gnome.org/GNOME/nautilus/-/issues/504Memory increases when repeatedly switching between two folders with thumbnail...2023-10-27T00:44:23ZHussam Al-TayebMemory increases when repeatedly switching between two folders with thumbnailed files.# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
Using nautilus 3.26.3.1, nautilus memory usage grows very large when switching between two folders on each with many thumbnailed documents...# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
Using nautilus 3.26.3.1, nautilus memory usage grows very large when switching between two folders on each with many thumbnailed documents. Every time time I switch between folderA and folderB, it grows in memory. FolderA is the Pictures folder and FolderB is the Documents folder.
Even pressing F5 repeatedly in Documents folder triggers this.
# Expected behavior
<!-- Describe the expected behavior. -->
Only consume more memory once per folder unless the files themselves were updated.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1035Transfering large amount of data (>100 GB) from external disk to PC on nautil...2023-10-27T00:40:42ZBarrel0LuckTransfering large amount of data (>100 GB) from external disk to PC on nautilus makes system not responsive or very slow# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1.On a freshly installed Fedora 30 (with all updates updates etc performed, no extensions) copy >100 GB data from an external hard disk to ...# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1.On a freshly installed Fedora 30 (with all updates updates etc performed, no extensions) copy >100 GB data from an external hard disk to the computer using Files (3.32.1-stable).
2. Wait for a few minutes and observe as the system slows down.
3. At times, the system becomes completely non-responsive. Using system monitor, I don't see high RAM or CPU usage...
Reproducible in:
<!--
Please test if the issue was already fixed in the unstable version of the app.
For that, follow these steps:
1. Make sure Flatpak is installed or install it following these steps https://flatpak.org/setup
2. Install the unstable version of the app following this link
https://gitlab.gnome.org/GNOME/gnome-apps-nightly/raw/master/NautilusMaster.flatpakref and save
it as a ".flatpakref" file
If these steps failed, write in 'Other' the distribution you’re using and
the version of the app.
-->
- Flatpak unstable: not tested
- Other:
# Current behavior
Large file or large data transfer (I've tested >100 GB) from an external drive to the PC using Nautilus slows the entire system (shell?) down and at times makes it non responsive.
# Expected behavior
The large data transfer must occur steadily in the background without affecting other processes or slowing down the shell in general, thus allowing normal work to proceed in parallel with data transfer.
# Additional information
Memory: 7.7 GB (8GB)
Processor: Intel® Core™2 Quad CPU Q9650 @ 3.00GHz × 4
Graphics: AMD® Rv620
Gnome: Version 3.32.2
Non SSD disk.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2554Nautilus freezes when searching2023-10-27T00:39:06ZSteffen StellNautilus freezes when searching# Affected version
- Nightly flatpak: Yes
- Other:
```
> nautilus --version
Initializing Nextcloud-client-nautilus extension
Using python version sys.version_info(major=3, minor=11, micro=0, releaselevel='candidate', serial=2)
GNOME nau...# Affected version
- Nightly flatpak: Yes
- Other:
```
> nautilus --version
Initializing Nextcloud-client-nautilus extension
Using python version sys.version_info(major=3, minor=11, micro=0, releaselevel='candidate', serial=2)
GNOME nautilus 43.0
```
After upgrading to Fedora 37, Nautilus freezes whenever I search for anything.
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Open Nautilus
2. start typing to search
# Current behavior
Sometimes it 2-4 letters of the search term appear in the search bar before freezing sometimes it doesn't get that far and you can see the transitioning icons stacked over each other. Sounds like #2010 , except it occurs not only after login but always. After a couple of seconds `"Files" not responding.` pops up and you have to force quit, waiting does not help.
# Expected behavior
highlight what I search for, no freezing
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
<!-- Ignore the text under this line. -->GNOME 45https://gitlab.gnome.org/GNOME/nautilus/-/issues/2856Rename dialog does not appear2023-10-27T00:34:04ZSasha HaleRename dialog does not appear<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see http...<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in a Terminal:
flatpak install --from https://nightly.gnome.org/repo/appstream/org.gnome.NautilusDevel.flatpakref
3) The Nightly version can now be launched from Activities, or with this command: flatpak run org.gnome.NautilusDevel
-->
# Affected version
- Nightly flatpak: Yes
- Other: Any distro with GNOME 43+ (Observed on OpenSUSE, Fedora, and Ubuntu)
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Have a Dell Inspiron 14 5425 with a Ryzen 7 (This issue doesn't occur on any other computer I've used)
2. Right click on a file or folder and select `Rename`
3. The rename dialog will not appear most of the time
# Current behavior
<!-- Describe the current behavior. -->
When clicking `Rename`, the rename dialog does not appear. No errors are logged anywhere when this happens. Also, UI elements are sometimes shown in their active or selected states when they should not be (This happens with sidebar rows and titlebuttons).
# Expected behavior
<!-- Describe the expected behavior. -->
The rename dialog should appear
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
This may not be an issue with nautilus, although I have not had any of these problems with any other app. It only occurs in the Libadwaita/GTK4 versions of nautilus (started around 43.beta and still happens in 44.beta)
<!-- Ignore the text under this line. -->