Files issueshttps://gitlab.gnome.org/GNOME/nautilus/-/issues2021-05-02T09:48:31Zhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/1531Nautilus fails to open files properly from network folders2021-05-02T09:48:31ZGiusy MargaritaNautilus fails to open files properly from network folders# Affected version
Latest version of Nautilus on Arch Linux. I thinks there's no need to check the nightly, it should be quite updated.
# Description of the issue
I switched to Gnome from Plasma. Used Dolphin for years and wanted to swi...# Affected version
Latest version of Nautilus on Arch Linux. I thinks there's no need to check the nightly, it should be quite updated.
# Description of the issue
I switched to Gnome from Plasma. Used Dolphin for years and wanted to switch to Nautilus also, but I can't because of a big issue with network folders.
I manage a FTP server with lots of documents that I used to open from Dolphin to the text editor. I can access the folder from Nautilus, but when I open a document, like a text file, Nautilus launches a browser rather than the default application. The interesting thing is that the browser launched is not even the default set in system settings. I set Firefox and the first time it opened Chromium, the second one Falkon.
I have gvfs packages installed.
# Steps to reproduce
1. Set an FTP folder and access to it through Nautilus.
2. Double click on a file.
3. A browser will be started showing and error page.
# Expected behavior
The default application for the selected file type should be started.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1548Nautilus crashes when clicking properties of avif files.2020-07-09T08:30:56ZArunNautilus crashes when clicking properties of avif files.It closes when: right click avif file -> select properties.
OS: Arch LinuxIt closes when: right click avif file -> select properties.
OS: Arch Linuxhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/1559NextCloud (owncloud) remote file mounts from GNOME Online Accounts sometimes ...2020-08-03T07:02:43ZJeff FortinNextCloud (owncloud) remote file mounts from GNOME Online Accounts sometimes get re-mounted/re-connected by themselvesA big annoyance I have is that the nextcloud account I have set in GNOME Online Accounts in the control center... sometimes automatically connects/mounts when I wake up my laptop (or desktop) computer from sleep, even if I had unmounted ...A big annoyance I have is that the nextcloud account I have set in GNOME Online Accounts in the control center... sometimes automatically connects/mounts when I wake up my laptop (or desktop) computer from sleep, even if I had unmounted from Nautilus before. It happens often but not everytime, but when it does, it's in my face, it slows some things (like gthumb) down, and it represents an unnecessary network connection.
Instead it should be present in the sidebar, but not mounted/connected until I click on it. Other remote protocols (FTP, SFTP, etc.) do not exhibit this issue.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1602segfault randomly when attemping to copy file to thumbdrive2021-08-15T02:56:58Zsimon placesegfault randomly when attemping to copy file to thumbdrive
version 3.26.4
```
[31817.530664] sdd: sdd1
[31817.632157] sd 4:0:0:0: [sdd] Attached SCSI removable disk
[32201.955697] nautilus[10174]: segfault at d0 ip 00007fc1e360e173 sp 00007fff10dc7060 error 4 in libgtk-3.so.0.2404.18[7fc1e337...
version 3.26.4
```
[31817.530664] sdd: sdd1
[31817.632157] sd 4:0:0:0: [sdd] Attached SCSI removable disk
[32201.955697] nautilus[10174]: segfault at d0 ip 00007fc1e360e173 sp 00007fff10dc7060 error 4 in libgtk-3.so.0.2404.18[7fc1e337c000+2c7000]
[32201.955736] Code: 45 00 48 85 c0 74 05 48 39 30 74 36 48 89 ef e8 13 3b d7 ff 85 c0 75 2a 48 8b 43 10 48 85 c0 74 12 48 39 e8 74 12 48 8b 40 18 <48> 8b 80 d0 00 00 00 eb e9 48 39 e8 75 0a 31 f6 4c 89 e7 e8 ba c8
```
maybe once in 100+https://gitlab.gnome.org/GNOME/nautilus/-/issues/1613Bad cut2020-11-16T21:34:40ZAlexandr K-shBad cutHello. When I cut a file and paste it into another explorer (pcmanfm-qt), it does not disappear in your explorer (Files) and must be manually deleted.Hello. When I cut a file and paste it into another explorer (pcmanfm-qt), it does not disappear in your explorer (Files) and must be manually deleted.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1617PROBLEM: SLOW WHEN LISTING SHARED DIRECTORY VIA VPN2023-07-09T16:28:28ZRodrigo BrazPROBLEM: SLOW WHEN LISTING SHARED DIRECTORY VIA VPNI have a samba4 configured as a file server in the cloud, I connect via vpn in the cloud to access the file server, then I set up the shared cloud directory on my linux, but when I access via nautilus a folder containing many files, it t...I have a samba4 configured as a file server in the cloud, I connect via vpn in the cloud to access the file server, then I set up the shared cloud directory on my linux, but when I access via nautilus a folder containing many files, it takes a long time to list its contents.
NOTE: Listing by windows in the same folder the speed is normal and fast!
![photo](/uploads/329afd81271be910aab77c8bfa0a100d/photo.jpg)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1624quicker keyboard navigation to get to files. (something like "skip to content...2020-10-05T16:37:16ZDhananjayquicker keyboard navigation to get to files. (something like "skip to content" features we see on websites)### Use cases
When I open nautilus and want to keyboard to navigate the directory structure I first need to press tab many times(4-5)
so that focus(or whatever it is called) is inside on files and folders.
### Desired behaviour
I woul...### Use cases
When I open nautilus and want to keyboard to navigate the directory structure I first need to press tab many times(4-5)
so that focus(or whatever it is called) is inside on files and folders.
### Desired behaviour
I would like to get to my files quicker and without pressing 4-5 Tabs first. Many websites solve the same problem with a
"Skip to content" button that appears after the first Tab press.
### Benefits of the solution
Clear Productivity benefits from saving time/keypresses.
### Possible drawbacks
The "Skip to content" button approch may not be possible due to UI limitation but any other ways that solve the same problem for example changing default focus position are also fine.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1638Increase the maximum limit of thumbnails from 4096 MB to a higher value in th...2022-12-26T20:19:54ZGhost UserIncrease the maximum limit of thumbnails from 4096 MB to a higher value in the preferences### Use cases
Currently thumbnail previews are limited to files up to 4096MB.
Many files have a higher size so lets increase the limit.
### Desired behavior
See thumbnail previews on files bigger than 4096MB.
### Benefits of the solu...### Use cases
Currently thumbnail previews are limited to files up to 4096MB.
Many files have a higher size so lets increase the limit.
### Desired behavior
See thumbnail previews on files bigger than 4096MB.
### Benefits of the solution
With the increase of data comes bigger files, nautilus has had a hard limit on the size of previews that is small for some files nowadays.
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1647[Invalid Name]Error while copying "Screencast from 2020-10-18 18:52:10.webm"2022-09-03T02:09:57ZFeldwor[Invalid Name]Error while copying "Screencast from 2020-10-18 18:52:10.webm"Ubuntu 20.04
Gnome shell: 3.36
It is either [Gnome Shell](https://gitlab.gnome.org/GNOME/gnome-shell) fault for choosing these recorded screencasts file names by default or Nautilus itself does not completely implement something. Re...Ubuntu 20.04
Gnome shell: 3.36
It is either [Gnome Shell](https://gitlab.gnome.org/GNOME/gnome-shell) fault for choosing these recorded screencasts file names by default or Nautilus itself does not completely implement something. Recorded using Gnome Shell screencast shortcut, not any kind of external program.
![image](/uploads/19bb2170488a9d1ddc86d5cab954c8d3/image.png)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1650Unable to move a files to another folder in google drive2021-08-15T03:17:37ZSergey KrylovUnable to move a files to another folder in google driveVersion 3.38.1-stable
Moving a files in google drive to a folder in (the same) google drive throws an "override file named edit" warning.
Edit file contains html page generated by google web server.Version 3.38.1-stable
Moving a files in google drive to a folder in (the same) google drive throws an "override file named edit" warning.
Edit file contains html page generated by google web server.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1657Nautilus list view imperformant and unusable in larger directories (half-rend...2023-07-09T16:28:32ZAndre KlapperNautilus list view imperformant and unusable in larger directories (half-rendered rows, scrolling and jumping)```
nautilus-3.38.1-1.fc33.x86_64
tracker3-3.0.1-1.fc33.x86_64
tracker3-miners-3.0.1-1.fc33.x86_64
```
* Populating the directory content (list view) takes minutes
* Visual artifacts when scrolling while populating
* Search results take...```
nautilus-3.38.1-1.fc33.x86_64
tracker3-3.0.1-1.fc33.x86_64
tracker3-miners-3.0.1-1.fc33.x86_64
```
* Populating the directory content (list view) takes minutes
* Visual artifacts when scrolling while populating
* Search results take minutes to display
* After going to another folder and back, no caching (very same game starts again)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1658Cannot dismiss context menu by click the on the left area2021-08-15T03:26:12ZWilliam TangCannot dismiss context menu by click the on the left areaHere is a demo video of the bug:
![Screencast_from_10-31-2020_12_18_05_AM](/uploads/48f0adb39d03e6717ad26a8508c8a847/Screencast_from_10-31-2020_12_18_05_AM.webm)
Distro: Arch Linux
Natilus: 3.38.1-1Here is a demo video of the bug:
![Screencast_from_10-31-2020_12_18_05_AM](/uploads/48f0adb39d03e6717ad26a8508c8a847/Screencast_from_10-31-2020_12_18_05_AM.webm)
Distro: Arch Linux
Natilus: 3.38.1-1https://gitlab.gnome.org/GNOME/nautilus/-/issues/1661Allow for remotely stored thumbnails2022-12-24T18:31:40ZChristoph MüllerAllow for remotely stored thumbnails### Use cases
Having many photos stored on a NAS, mounted in Nautilus via SFTP and GVFS. The photos are accessed from multiple machines.
### Desired behavior
Thumbnails should be shown quickly. It shall not be necessary for everyone to ...### Use cases
Having many photos stored on a NAS, mounted in Nautilus via SFTP and GVFS. The photos are accessed from multiple machines.
### Desired behavior
Thumbnails should be shown quickly. It shall not be necessary for everyone to pull all the photos through the network before seeing the previews.
### Solution approaches
Allow e.g. for a `.thumbnails` directory to be located somewhere on the remote location (be it the root of the mount or the directory containing the photos), in which the thumbnails are stored.
The behavior of storing thumbnails remotely shall be configurable and disabled by default, because it could reduce the privacy of the user generating the thumbnails (could reveal which photos where viewed when, by whom and with which software (Nautilus)). It would make sense to only have the thumbnails stored remotely when explicitly configured by the user for that certain remote location as privacy considerations might vary between remote storages. It also would be advisable to implement some countermeasures like replacing modification timestamps on new thumbnail files (or make them equal to the timestamps of the photos) as well as replacing the user creating the thumbnails. Fetching previews from the server does probably not notably affect privacy.
It should be possible to fetch random previews quickly (without reducing the speed of fetching *all* the previews too much).
When images are detected to be modified (e.g. rotated) or removed, the old previews should be deleted automatically.
The format of the thumbnails should be portable (in the sense of cross-plattform compatible). It shall finally be possible to pregenerate the thumbnails on the server. At best, it would be compatible with Windows and Mac OS.
### Benefits of the solution
- More speed of getting previews of images on remote locations.
### Possible drawbacks
- Privacy could be affected (see above).
- Loss of available remote storage might be not desired.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1676Crashing when batch renaming2021-08-15T03:27:43ZGhost UserCrashing when batch renaming<!--
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
3.38.1-1ubuntu1
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1.select multiple files, press f2 to bring up batch renaming dialog
2.select "Find and replace text"
# Current behavior
<!-- Describe the current behavior. -->
randomly crash after selected "Find and replace text"
# Additional information
system log
```bash
$ journalctl -f
-- Logs begin at Sun 2020-11-15 23:45:02 AWST. --
Nov 18 14:10:28 bluewhale nautilus[19512]: invalid unclassed pointer in cast to 'NautilusFile'
Nov 18 14:10:28 bluewhale nautilus[19512]: nautilus_directory_get_for_file: assertion 'NAUTILUS_IS_FILE (file)' failed
Nov 18 14:10:28 bluewhale nautilus[19512]: nautilus_file_unref: assertion 'NAUTILUS_IS_FILE (file)' failed
Nov 18 14:10:30 bluewhale dbus-daemon[1011]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.129' (uid=1000 pid=19807 comm="nautilus . " label="unconfined")
Nov 18 14:10:30 bluewhale audit: BPF prog-id=23 op=LOAD
Nov 18 14:10:30 bluewhale audit: BPF prog-id=24 op=LOAD
Nov 18 14:10:30 bluewhale systemd[1]: Starting Hostname Service...
Nov 18 14:10:30 bluewhale dbus-daemon[1011]: [system] Successfully activated service 'org.freedesktop.hostname1'
Nov 18 14:10:30 bluewhale audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 18 14:10:30 bluewhale systemd[1]: Started Hostname Service.
Nov 18 14:10:41 bluewhale dbus-daemon[2319]: [session uid=1000 pid=2319] Activating service name='org.gnome.Nautilus' requested by ':1.71' (uid=1000 pid=2810 comm="/usr/libexec/gsd-media-keys " label="unconfined")
Nov 18 14:10:41 bluewhale dbus-daemon[2319]: [session uid=1000 pid=2319] Successfully activated service 'org.gnome.Nautilus'
Nov 18 14:10:42 bluewhale nautilus[19835]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
Nov 18 14:10:56 bluewhale nautilus[19835]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
Nov 18 14:11:12 bluewhale systemd[1]: systemd-hostnamed.service: Succeeded.
Nov 18 14:11:12 bluewhale audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 18 14:11:12 bluewhale audit: BPF prog-id=24 op=UNLOAD
Nov 18 14:11:12 bluewhale audit: BPF prog-id=23 op=UNLOAD
Nov 18 14:11:30 bluewhale org.gnome.Nautilus[19835]: **
Nov 18 14:11:30 bluewhale org.gnome.Nautilus[19835]: ERROR:../src/nautilus-directory.c:873:add_to_hash_table: assertion failed: (g_hash_table_lookup (directory->details->file_hash, name) == NULL)
Nov 18 14:11:30 bluewhale audit[19835]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined pid=19835 comm="pool-org.gnome." exe="/usr/bin/nautilus" sig=6 res=1
Nov 18 14:11:30 bluewhale org.gnome.Nautilus[19835]: Bail out! ERROR:../src/nautilus-directory.c:873:add_to_hash_table: assertion failed: (g_hash_table_lookup (directory->details->file_hash, name) == NULL)
Nov 18 14:12:13 bluewhale NetworkManager[1017]: <info> [1605679933.8935] manager: NetworkManager state is now CONNECTED_SITE
Nov 18 14:12:13 bluewhale dbus-daemon[1011]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Nov 18 14:12:13 bluewhale systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 18 14:12:13 bluewhale dbus-daemon[1011]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 18 14:12:13 bluewhale systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 18 14:12:13 bluewhale audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 18 14:12:14 bluewhale NetworkManager[1017]: <info> [1605679934.5967] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 18 14:12:24 bluewhale systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Nov 18 14:12:24 bluewhale audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
^C
```
crashed after this line: Nov 18 14:11:30 bluewhale org.gnome.Nautilus[19835]: Bail out! ERROR:../src/nautilus-directory.c:873:add_to_hash_table: assertion failed: (g_hash_table_lookup (directory->details->file_hash, name) == NULL)
Thanks.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1679Multi factor authentication support2020-11-24T08:12:52ZghurandomMulti factor authentication support### Use cases
Allow connecting to remote resources protected by MFA when using 'connect to server'
### Desired behavior
A pop up text entry box should allow 2FA auth code to be provided
### Benefits of the solution
Allow connecting t...### Use cases
Allow connecting to remote resources protected by MFA when using 'connect to server'
### Desired behavior
A pop up text entry box should allow 2FA auth code to be provided
### Benefits of the solution
Allow connecting to remote resources protected by MFA using 'connect to server'
### Possible drawbacks
I don't really see any, I was expecting a similar popup as when a password is required.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1696RTL File Name2020-12-12T13:18:34ZنیستیRTL File NameI use Persian language for naming files. The direction of writing in this language is right to left.
There is a problem here:
When I write the file name in Persian, it should normally be right to left, while the direction is right alighn!I use Persian language for naming files. The direction of writing in this language is right to left.
There is a problem here:
When I write the file name in Persian, it should normally be right to left, while the direction is right alighn!https://gitlab.gnome.org/GNOME/nautilus/-/issues/1701[master] heavy memory leak on focus change2020-12-21T18:49:51ZDamian Ivanov[master] heavy memory leak on focus changeI'm using master. Every focus change to nautilus causes 0.3 MB leak.
Reproduce:
1) Open 1 Nautilus window.
2) Focus different application.
3) Focus Nautilus.
4) Repeat 2 and 3.
Memory will increase endlessly.I'm using master. Every focus change to nautilus causes 0.3 MB leak.
Reproduce:
1) Open 1 Nautilus window.
2) Focus different application.
3) Focus Nautilus.
4) Repeat 2 and 3.
Memory will increase endlessly.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1707Nautilus uses the last display rather than the one from the environment2020-12-20T23:10:39ZRobert WlodarczykNautilus uses the last display rather than the one from the environment# Affected version
- Nightly flatpak: Can't test it because it's a production machine.
- Other:
Debian 10 (buster)
```
<gnome-version>
<platform>3</platform>
<minor>30</minor>
<micro>2</micro>
<distributor>Debian</distributor>
</gno...# Affected version
- Nightly flatpak: Can't test it because it's a production machine.
- Other:
Debian 10 (buster)
```
<gnome-version>
<platform>3</platform>
<minor>30</minor>
<micro>2</micro>
<distributor>Debian</distributor>
</gnome-version>
```
# Steps to reproduce
1. When using x11docker, it uses xinit with either Xpra or Xephyr. In my case, I'm using Xpra. After exiting an application running with x11docker, such as Jess' firefox container, Nautilus will not launch. In `/var/log/messages` I see `nautilus[14536]: cannot open display: :113`.
2. Prior to running x11docker, Nautilus launches without issue using the theme that I have set.
3. While running with x11docker, Nautilus will launch without issue, but using the default white theme, not the custom theme that I have.
A simple repro can be don using the following steps:
1. Run:
```
Xephyr :50 &
sleep 2
nautilus
```
2. Exit Nautilus and Xephyr, ensuring that Xephyr has exited.
3. Try launching Nautilus again, notice that `/var/log/messages` shows `nautilus[3738]: cannot open display: :101`.
# Current behavior
Nautilus does not attach to the `DISPLAY` that is defined in the environment.
# Expected behavior
Nautilus should always attach to the `DISPLAY` that is defined in the environment rather than the last `DISPLAY` used. Users should be able to override this default behavior.
# Additional information
Linked issue on x11docker: https://github.com/mviereck/x11docker/issues/313.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1718Show error message when file cannot be deleted due to permission failure2022-12-29T20:58:12ZJonnyShow error message when file cannot be deleted due to permission failure
# Affected version
Gnome Files 3.36.3-stable Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal
# Steps to reproduce
1. create a file as another user in your home directory, eg root # touch test
2. i...
# Affected version
Gnome Files 3.36.3-stable Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal
# Steps to reproduce
1. create a file as another user in your home directory, eg root # touch test
2. in Nautilus select the file, and press Delete key
3. Observe no error, file still present.
# Current behavior
No permission error
# Expected behavior
Some sort of popup error "Unable to delete file "test" Permission denied. File owned by user 'root' group 'root'"
# Additional information
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1724file operations should be autoremove after a time2021-01-04T10:50:43ZonePlayerfile operations should be autoremove after a timeHey
Tonight i did massive moving and copying Files. The File operation Button in the Menu Bar from Nautilus is helpful but not perfect. Operations done should be autoremove after a time (5 seconds or so) but they stay as long one operat...Hey
Tonight i did massive moving and copying Files. The File operation Button in the Menu Bar from Nautilus is helpful but not perfect. Operations done should be autoremove after a time (5 seconds or so) but they stay as long one operation is still running. (i added a Picture)
Even if i can scroll down to the running operation, it moves to the top again after a second.
Hope it helps, Steve
PS: i use Ubuntu 18.04 LTS and Nautilus V 3.26.4
![Auswahl_001](/uploads/da5ca74ca5f1dda02676537f10e05ab5/Auswahl_001.png)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1738Allow to open properties on more than one file at a time2021-01-09T23:32:43ZJonnyAllow to open properties on more than one file at a time### Use cases
View properties on more than one file at a time. Separate dialogues, as on Ms Windows.
### Desired behavior
View properties on more than one file at a time. Separate dialogues, as on Ms Windows.
### Benefits of the solut...### Use cases
View properties on more than one file at a time. Separate dialogues, as on Ms Windows.
### Desired behavior
View properties on more than one file at a time. Separate dialogues, as on Ms Windows.
### Benefits of the solution
Useful to not have Nautilus window locked up while Properties are open.
### Possible drawbacks
None.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1746GtkProgressBar is not always redrawn2023-06-13T08:43:11ZAntónio Fernandesantoniof@gnome.orgGtkProgressBar is not always redrawnThe following discussion from !605 should be addressed:
- [ ] @oholy started a [discussion](https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/605#note_928289): (+1 comment)
> There is one more related issue which I would li...The following discussion from !605 should be addressed:
- [ ] @oholy started a [discussion](https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/605#note_928289): (+1 comment)
> There is one more related issue which I would like to solve, however, seems unrelated. The `GtkProgressBar` is not always redrawn, even though `gtk_progress_bar_set_fraction` is called with correct values. This is especially annoying when the progress is updated only after each successfully updated file. It doesn't help even if I add explicit `gtk_widget_queue_draw`. If I reopen the popover, it shows the correct fraction. Any idea what is wrong with it, or how to debug it?https://gitlab.gnome.org/GNOME/nautilus/-/issues/1748"Selected files bar" or status bar is covering the bottom file in list view -...2021-01-25T13:51:36ZGh0stBustr"Selected files bar" or status bar is covering the bottom file in list view - add dedicated bar for selected files and status# Affected version
Fresh install of the latest CentOS 8.3:
- GNOME Shell 3.32.2
- GNOME nautilus 3.28.1
- CentOS Linux release 8.3.2011
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platfor...# Affected version
Fresh install of the latest CentOS 8.3:
- GNOME Shell 3.32.2
- GNOME nautilus 3.28.1
- CentOS Linux release 8.3.2011
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
CentOS Linux release 8.3.2011
CentOS Linux release 8.3.2011
# Steps to reproduce
1. Open Gnome Files
2. Set view to LIST VIEW (by clicking on Toggle View on the top right - that's the middle icon with 4 squares)
3. Set zoom to 50% (by clicking on the rightmost icon on top right - looks like a sandwich menu button - and click on the "-" sign to zoom out)
4. Go to a folder that has more files that can fit into your view. (or create a new folder and using this command create many files in that folder: touch bspl{0001..0050}.c )
5. Scroll to the bottom of the list and select the last file on the bottom.
# Current behavior
You can't see the details of the file in the columns (like size or date modified) because it is covered by the "<filename> selected (x bytes)" popup box on the bottom right. This is extremely annoying.
# Expected behavior
Instead of this popup box there should be a dedicated row on the bottom for this like in every major operating systems (like macOS).
Please find screenshot attached demonstrating this very annoying problem.
![bugreport_01](/uploads/05db40719132d87514b187c498322f0a/bugreport_01.png)
Please find screenshot attached demonstrating how this works perfectly on Apple macOS.
![macOS](/uploads/adaaca381d0d8dcd9c301d7599751c6f/macOS.jpg)
![macOS_2](/uploads/fe1e0a08a007e586b793dca404abc138/macOS_2.jpg)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1751write errors in shell on SMB share mounted from Nautilus (gvfs/fuse)2021-01-22T12:28:14Zteridonwrite errors in shell on SMB share mounted from Nautilus (gvfs/fuse)<!--
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:Can't test it because flatpak failed to install nightly ( https://gitlab.gnome.org/-/snippets/1471 )
- Other: nautilus 3.26.3.1 from Centos 7.9.2009 distro
# Steps to reproduce
1. Mount SMB share via Nautils
2. open gnome-terminal and navigate to /run/user/1000/gvfs/smb-share:server=servername,share=sharename
3. attempt to append to a new or existing text file with "echo"; e.g. "echo foo > bar"
# Current behavior
bash fails to write the file with the error: "Invalid argument":
```
$ echo foo > bar
-bash: bar: Invalid argument
```
# Expected behavior
File should be appended
# Additional information
"gedit" on a file on the share seems to work without issue. Creating folders in Nautilus works.
But from a terminal all my attempts to write to files result in some kind of error.
e.g. using "vim" on a new file 1) vim reports the file is read-only 2) forcing a write with 'w!' results in a write error in vim ("E212: Can't open file for writing") and 3) after a forced write attempt a numbered empty file is left in the CWD (e.g. file named '4913', where 4913 is seemingly random?)
using vim on an EXISTING file results in different errors: 1) vim reports a swap file already exists, even though it did NOT exist at vim start time
```
$ ls -a1
.
..
foobar.txt
$ vim foobar.txt
E325: ATTENTION
Found a swap file by the name ".foobar.txt.swp"
owned by: rladmin dated: Thu Jan 21 15:01:37 2021
[cannot be read]
While opening file "foobar.txt"
dated: Thu Jan 21 14:59:39 2021
(1) Another program may be editing the same file. If this is the case,
be careful not to end up with two different instances of the same
file when making changes. Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r foobar.txt"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file ".foobar.txt.swp"
to avoid this message.
Swap file ".foobar.txt.swp" already exists!
## ABORTED vim
$ ls -a1 | grep foobar
foobar.txt
.foobar.txt.swo
.foobar.txt.swp
I have mounted the share using mount.cifs with the uid and gid options; in this case the user can read and write files via the shell with no problems.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1780Clipboard work 1 time out of 102021-03-25T22:07:34ZqbyClipboard work 1 time out of 10Both middle-click one and Ctrl-C one
On XOrg it works all the timeBoth middle-click one and Ctrl-C one
On XOrg it works all the timehttps://gitlab.gnome.org/GNOME/nautilus/-/issues/1785no option to disable automatic extraction of archives2022-08-28T21:06:49Zclophno option to disable automatic extraction of archivesnautilus defaults to extract archives on open. There needs to be a setting to disable it globally.
This pollutes the folders with extracted files and differs from the behavior of other operating systems/Desktop environments. While e.g. ...nautilus defaults to extract archives on open. There needs to be a setting to disable it globally.
This pollutes the folders with extracted files and differs from the behavior of other operating systems/Desktop environments. While e.g. windows allows you to browse/access the file contents of an archive from within explorer, it doesn't actually extract the files in the current folder, but is more akin to opening the archive in file-roller.
While you can override the default action for each filetype separately, that is not sufficient. Especially since you probably forgot to add variant xy and run into the problem when you least expect it. I never ever want to have to deal with manually removing the files that were extracted needlessly. If I want to extract them, I use the context-menu of extract-here/to.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1786Cannot drag the Properties Window2021-03-04T07:05:43ZPrateek PardeshiCannot drag the Properties WindowIt is not possible to drag the Properties window alone without affecting the tab window behind it.
OS: Ubuntu 20.04 (Focal Fossa)
Video for more explaination:
![Screencast_from_04-03-21_04_43_36_AM_IST](/uploads/716b25ac975f3639224bd7e...It is not possible to drag the Properties window alone without affecting the tab window behind it.
OS: Ubuntu 20.04 (Focal Fossa)
Video for more explaination:
![Screencast_from_04-03-21_04_43_36_AM_IST](/uploads/716b25ac975f3639224bd7ee05f9ec7c/Screencast_from_04-03-21_04_43_36_AM_IST.webm)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1808Rename a file with text from clipboard which includes LF/CR , fail without er...2021-03-20T19:59:40ZGhost UserRename a file with text from clipboard which includes LF/CR , fail without error msg.# Affected version
- Nightly flatpak: Can't test it because time
- Other: Ubuntu 20.04 / Gnome 3.36.8 / Nautilus 3.36.3-stable ?
# Steps to reproduce
As example, copy a multiline title from a pdf document, close pdf and try to rename it...# Affected version
- Nightly flatpak: Can't test it because time
- Other: Ubuntu 20.04 / Gnome 3.36.8 / Nautilus 3.36.3-stable ?
# Steps to reproduce
As example, copy a multiline title from a pdf document, close pdf and try to rename it with the text from clipboard.
Copying multiline text can happen by accident.
# Current behavior
Renaming fail without an error message.
# Expected behavior
Should at least give an error message about why it fail to rename a file.
# Additional information
The problem seems to be the input handling when it comes to LF/CR in the copied text.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1815Files/nautilus does not sync with updated ownership immediately2021-03-30T19:38:30ZMichael VelimirovFiles/nautilus does not sync with updated ownership immediatelyAfter changing ownership from terminal it is not reflected in files immediately.
Only after navigating to a different folder and then back again.After changing ownership from terminal it is not reflected in files immediately.
Only after navigating to a different folder and then back again.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1834Files Network Share (Windows network) does not list my Samba Share and "Conne...2021-04-26T21:40:19ZAlienusgamingFiles Network Share (Windows network) does not list my Samba Share and "Connect" button on the "Connect to Server" section gets disabled if there's a double dot (:) in it<!--
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: Can't test it because nightly got updated during my installation (not sure, if so i'll retry) (error-> Failed to install org.gnome.Platform: While pulling runtime/org.gnome.Platform/x86_64/master from remote gnome-nightly: Error reading data from TLS socket: Error decoding the received TLS packet.) <!-- Delete the unwanted anwsers -->
- Other: 5.8.0-50-generic 56~20.04.1-Ubuntu nautilus/focal-updates,now 1:3.36.3-0ubuntu1 amd64 <!-- Write the distribution you’re using and the version of the app. -->
# Current behavior
<!-- Describe the current behavior. -->
I can't see my Samba files on the list or connect to the server manually with the menu on the bottom or Ctrl+L
list and manual entry
![Screenshot_from_2021-04-25_00-14-46](/uploads/89d537557cb197883d94bc223aa82cd3/Screenshot_from_2021-04-25_00-14-46.png)
Ctrl+L
![Screenshot_from_2021-04-25_00-19-43](/uploads/d21692cc0fd45f65fbcb8931b391be32/Screenshot_from_2021-04-25_00-19-43.png)
![Screenshot_from_2021-04-25_00-20-01](/uploads/9dade3ace96472c9bac9c4ca8b087d15/Screenshot_from_2021-04-25_00-20-01.png)
# Expected behavior
<!-- Describe the expected behavior. -->
My Ubuntu 18.04 VM can see and connect to its own Samba share.
# 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
-->
I can connect to it via `smbclient`
Similar to #17 but i couldn't find gvfs-nfs so i reinstalled all the Nautilus and gvfs packages that was installed, didn't fix.
`sudo apt-get install --reinstall --fix-broken --fix-missing --fix-policy gir1.2-nautilus-3.0 libnautilus-extension1a nautilus-data nautilus-extension-gnome-terminal nautilus-sendto nautilus-share nautilus python3-nautilus`
`sudo apt-get install --reinstall --fix-broken --fix-missing --fix-policy gvfs gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs`
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1858[3.36] Empty space at the bottom of the right-click menu when a single folder...2021-05-13T06:31:07ZTim Hofstede[3.36] Empty space at the bottom of the right-click menu when a single folder is selected# Affected version
Nautilus version 3.36.3-stable
Ubuntu 20.04
Yaru GTK theme, but also happens with Adwaita
# Steps to reproduce
1. Open Nautilus.
2. Right-click _a single folder_.
# Current behavior
There should be a strange ...# Affected version
Nautilus version 3.36.3-stable
Ubuntu 20.04
Yaru GTK theme, but also happens with Adwaita
# Steps to reproduce
1. Open Nautilus.
2. Right-click _a single folder_.
# Current behavior
There should be a strange empty space at the bottom, like an entry that's missing.
Interestingly, selecting multiple folders or any file other than a folder does not cause the empty space.
This does not happen anymore in GNOME/Nautilus 3.38 or newer.
# Expected behavior
The empty space should not be there.
# Additional information
Screenshot:
![nautilus-empty-spacejpg](/uploads/cd0fc1fd87d1b15bbc348004e501ad3d/nautilus-empty-spacejpg.jpg)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1876Sorting files and directories differently2022-09-03T02:09:27ZJohann-TreeSorting files and directories differently### Use cases
I would like to sort directories alphabetically (have them shown first) and files sorted by Modified date. By that, I could navigate faster to the file(s) I would like to work with: I can find the directory I need best when...### Use cases
I would like to sort directories alphabetically (have them shown first) and files sorted by Modified date. By that, I could navigate faster to the file(s) I would like to work with: I can find the directory I need best when the directories are shown first and sorted alphabetically, followed by the files sorted by Modified date.
Other users requested this too: https://askubuntu.com/questions/1095118/sorting-files-and-directories-differently-in-the-file-browser
### Desired behavior
A sub-option (option only accessible when _Sort-> Sort directories before files_ is ticked) in the preferences of nautilus to sort directories and files differently and to choose how directories shall get sorted.
I would suggest that only the sorting of directories has to be set in the preferences, and clicking the column title sorts only the files.
### Benefits of the solution
More adaptability to workflows of different users.
Resulting in users can work more efficiently.
### Possible drawbacks
More options in the preferences dialog.https://gitlab.gnome.org/GNOME/nautilus/-/issues/1878Ubuntu 20.04/Nautilus 3.36.3 Message recipient disconnected from message bus ...2021-05-27T13:13:34Zmanu-pUbuntu 20.04/Nautilus 3.36.3 Message recipient disconnected from message bus without replying when clicking in Recent filesOn a Ubuntu 20.04.2 running nautilus 3.36.3, when I click in Recent files (or whatever it is in english, I get a french version), comes a popup saying something like:
"Oops! Something went wrong.
Unmanaged error message: Message recipien...On a Ubuntu 20.04.2 running nautilus 3.36.3, when I click in Recent files (or whatever it is in english, I get a french version), comes a popup saying something like:
"Oops! Something went wrong.
Unmanaged error message: Message recipient disconnected from message bus without replying"
Here's what syslog displays when I click in Recent files:
`May 26 19:10:58 localhost gvfsd[118376]: Unable to init server: Impossible de se connecter : Connexion refusée`
`May 26 19:10:58 localhost gvfsd-recent[118376]: cannot open display: `
`May 26 19:10:58 localhost gvfsd[1769]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Message recipient disconnected from message bus without replying`
`May 26 19:10:58 localhost gvfsd[118381]: Unable to init server: Impossible de se connecter : Connexion refusée`
`May 26 19:10:58 localhost gvfsd-recent[118381]: cannot open display: `
`May 26 19:10:58 localhost gvfsd[1769]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Message recipient disconnected from message bus without replying`https://gitlab.gnome.org/GNOME/nautilus/-/issues/1892segfault when trying to open properties dialog on a mjpeg file2021-08-22T14:46:19Zsimon placesegfault when trying to open properties dialog on a mjpeg file# Affected version
- Nightly flatpak: Yes
- Other: 40.2
# Steps to reproduce
1. open properties on an mjpeg file
also confirmed using: https://filesamples.com/samples/video/mjpeg/sample_1280x720_surfing_with_audio.mjpeg# Affected version
- Nightly flatpak: Yes
- Other: 40.2
# Steps to reproduce
1. open properties on an mjpeg file
also confirmed using: https://filesamples.com/samples/video/mjpeg/sample_1280x720_surfing_with_audio.mjpeghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/1903Show total size of trashed files2021-11-27T15:56:58Zrdgh8Show total size of trashed files### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
I usually empty my trash when it grows too large, so it would be useful to be able to see the size of the trash.
### Des...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
I usually empty my trash when it grows too large, so it would be useful to be able to see the size of the trash.
### Desired behavior
<!-- Describe the desired functionality. -->
Show size of all trashed files in the trash folder.
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
- Automatically shows a figure I/the user would have to calculate anyways
- Can also indicate if something was accidentally trashed that wasn't supposed to be, ex. a video file or something else with a large size
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
- May take a long time to calculate size of nested directory structures
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1907Nautilus takes up to 50 seconds to open2021-07-02T17:01:40ZAlfredo CasanovaNautilus takes up to 50 seconds to openEverytime i open Nautilus it takes up to 50 seconds to open. Attached is the output for `time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus`
[nautilus.strace2](/uploads/c1a35564f50829563f6220068d7956d2/nautilus.strace2)Everytime i open Nautilus it takes up to 50 seconds to open. Attached is the output for `time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus`
[nautilus.strace2](/uploads/c1a35564f50829563f6220068d7956d2/nautilus.strace2)https://gitlab.gnome.org/GNOME/nautilus/-/issues/1912crash when deleting folder with many files2021-07-16T15:31:01ZChristian Rauchrauch.christian@gmx.decrash when deleting folder with many files<!--
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: Can't test it because I am getting the error `bwrap: Can't find source path /tmp/.X11-unix/X0: No such file or directory`
- Other: 3.36.3
# Steps to reproduce
1. delete folder with many (~10k) files
# Current behavior
Nautilus sometimes crashes.
# Expected behavior
No crashes.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1914Nautilus header toolbar not expanding2021-07-13T12:20:22ZJames ZNautilus header toolbar not expanding<!--
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: Can't test it because I don't use blob
- Other: > 3.38
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Open Nautilus
2. Maximize it or
3. Extend Nautilus width wider
# Current behavior
<!-- Describe the current behavior. -->
The header toolbar does not expand, its static.
# Expected behavior
<!-- Describe the expected behavior. -->
The header toolbar should expand
# 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
-->
I checked the following gtk widgets via GTKInspector
- header_toolbar
- toolbar_switcher_container
- NautilusContainerMaxWidth
indeed, they confirm to having the `expand` property set to `FALSE`, thus the behavior
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1916Feature: Make empty space in header toolbar perform actions2022-03-27T20:09:13ZJames ZFeature: Make empty space in header toolbar perform actions### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
The first time I saw the new Nautilus header toolbar, I was glad I can now click the bar and search for stuffs or do somet...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
The first time I saw the new Nautilus header toolbar, I was glad I can now click the bar and search for stuffs or do something. Boy I was wrong, its unclickable! :)
Usually, the empty section of a text-like bar, such as in the Nautilus header toolbar, is a common UX for actions such as search or text input. This is a wide spread UI that can be seen in browsers, search engines, and even in gitlab.
![Screenshot_from_2021-07-13_08-08-01_2](/uploads/6d3dae3f84093dca8a06f057113b023a/Screenshot_from_2021-07-13_08-08-01_2.png)
### Desired behavior
<!-- Describe the desired functionality. -->
Should initiate search bar or transform into text base path
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
This feature is beneficial because:
1. makes Nautilus faster to use,
2. makes Nautilus more user friendly,
3. the empty bar will not be mistaken as bugged search bar because it really is now.
4. also makes header toolbar more usable for expected UX behavior
Since clicking is easier to do than CTRL+L. This solves 3 shortcut issues:
1. solves shortcut too far from the left of the keyboard,
2. solves shortcut too difficult crossing the left hand to the right of the keyboard ,
3. solves shortcut too disrupting using the right hand since you have to lift from the mouse then back again.
Touch device
1. makes Nautilus more touch friendly,
2. clicking the empty portion of a text-like bar is a UX for search and text input in touch devices,
3. users need not manually launch the keyboard because clicking the empty portion of the bar it lunch the search bar and will automatically initiate keyboard.
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
- When the path is long, this feature will be difficult to discover.
Counter arguments:
1. But, when you open nautilus, you are most likely in surface directory and being able to access the top bar easily via mouse click or touch is a plus point to usability.
2. How long should we really stay in deep directory vs top level directories? If one of GNOME's goal is to keep it simple for user then users will most likely be in top level directories ie. Pictures, Downloads, Documents, etc.
3. If you are seeing deep directory often, you are most likely a dev, and we know, the terminal is best for dev jobs, moreover, you will be in an IDE of some sort most of the time and probably knows the CRTL+L shortcut as well :)
Possible solution:
- double click the breadcrumbs to show the text box
- in touch device, long press breadcrumbs to show text box
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1922Truncated image preview for a file created in real time on a USB storage2021-07-20T07:29:53ZDmitry KuteynikovTruncated image preview for a file created in real time on a USB storageI connected my Android smartphone via USB cable and opened it's Screenshots folder with nautilus. Then I made a screenshot on the phone. Nautilus detected a new image file and started to make a preview for it. However, the data of the fi...I connected my Android smartphone via USB cable and opened it's Screenshots folder with nautilus. Then I made a screenshot on the phone. Nautilus detected a new image file and started to make a preview for it. However, the data of the file wasn't yet fully written to the disk, so the file manager got only part of the image and the rest was painted in grey. This truncated preview didn't change after I have refreshed the view. The file itself is 100% valid and can be opened in an image viewer.
The issue is always reproducible.
I have filed this bug to Ubuntu as well, see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935677
![truncated](/uploads/4345922c825da4e59a03e4f133e55851/truncated.png)
[Dependencies.txt](/uploads/1582262ce95b58233bcbac1ef9c6c4e9/Dependencies.txt)
[GsettingsChanges.txt](/uploads/aaa51044b24305d29b35e7116d38a03f/GsettingsChanges.txt)
[ProcCpuinfoMinimal.txt](/uploads/1b562ec32cc182cff4e048f8e250b91f/ProcCpuinfoMinimal.txt)
[ProcEnviron.txt](/uploads/71e81b28f445686fe0911dcc3cecc394/ProcEnviron.txt)
| key | value |
| ------ | ------ |
| ProblemType | Bug |
| DistroRelease | Ubuntu 20.04 |
| Package | nautilus 1:3.36.3-0ubuntu1 |
| ProcVersionSignature | Ubuntu 5.4.0-77.86-generic 5.4.119 |
| Uname | Linux 5.4.0-77-generic x86_64 |
| NonfreeKernelModules | nvidia_modeset nvidia |
| ApportVersion | 2.20.11-0ubuntu27.18 |
| Architecture | amd64 |
| CasperMD5CheckResult | skip |
| CurrentDesktop | ubuntu:GNOME |
| Date | Fri Jul 9 14:08:02 2021 |
| InstallationDate | Installed on 2019-09-17 (660 days ago) |
| InstallationMedia | Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) |
| SourcePackage | nautilus |
| UpgradeStatus | Upgraded to focal on 2020-05-25 (409 days ago) |
| usr_lib_nautilus | |https://gitlab.gnome.org/GNOME/nautilus/-/issues/1924Add the Windows List view2021-07-22T19:09:22Zasync84Add the Windows List view### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
Add additional view option
### Desired behavior
<!-- Describe the desired functionality. -->
Add additional view option...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
Add additional view option
### Desired behavior
<!-- Describe the desired functionality. -->
Add additional view option
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
Adding the Windows List view will allow me to be more productive by showing more content on the screen with less scrolling. This can be added as a optional extra that can be hidden in the settings if it is not deemed popular
Cinnamon Files calls the feature "Compact View"
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
None
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1928Unable to get contents of the bookmarks file: Error opening file /home/st/.gt...2022-09-03T02:47:33ZsoloturnUnable to get contents of the bookmarks file: Error opening file /home/st/.gtk-bookmarks: No such file or directorynautilus puts the following message in journal, with "error" it becomes frightening. apart from there should not be a dotfile in the home directory, it would be nice if the message would not be there at all.
```
Unable to get contents ...nautilus puts the following message in journal, with "error" it becomes frightening. apart from there should not be a dotfile in the home directory, it would be nice if the message would not be there at all.
```
Unable to get contents of the bookmarks file: Error opening file /home/st/.gtk-bookmarks: No such file or directory
```https://gitlab.gnome.org/GNOME/nautilus/-/issues/1964Incorrect calculation of the number of files when moving2021-10-16T17:36:04ZLinuxoid85Incorrect calculation of the number of files when movingNautilus 40.2 (rpm package)
Flatpak: no
GNOME: 40.3
Host: Fedora 34
# Steps to reproduce
1. Copied a large number of files. For example, as in the photo below.
![Снимок_экрана_от_2021-08-25_18-01-04](/uploads/6e3c80453c4dc5dc5dcf38d...Nautilus 40.2 (rpm package)
Flatpak: no
GNOME: 40.3
Host: Fedora 34
# Steps to reproduce
1. Copied a large number of files. For example, as in the photo below.
![Снимок_экрана_от_2021-08-25_18-01-04](/uploads/6e3c80453c4dc5dc5dcf38db25abe4c6/Снимок_экрана_от_2021-08-25_18-01-04.png)
(273214 files)
Result in the list of operations:
![Снимок_экрана_от_2021-08-25_17-55-48](/uploads/034d582d655495105802e8f2ee112276/Снимок_экрана_от_2021-08-25_17-55-48.png)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/1990Virtual file system for the Online Account Nextcloud and may other to.2021-10-16T18:50:41ZMannshochVirtual file system for the Online Account Nextcloud and may other to.<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
https://nextcloud.com/blog/nextcloud-introduces-virtual-drive-...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
https://nextcloud.com/blog/nextcloud-introduces-virtual-drive-in-desktop-client-to-simplify-desktop-integration/
This feature developed for Nextcloud-desktop seems stalled but the idea is great. I would like to see such a feature on gnome shell
If possible open the implementation (if possible) for several protocols. e.g. sftp
### How would you like it to work
- It should work unseen by common user.
- If a Nextcloud Online account is added a mount point appear in files.
- gnome-shell should be able to work inside this.
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2034Duplicated entry for multi-device BTRFS (and weird behaviour)2021-11-30T08:55:34ZFabrizio PelosiDuplicated entry for multi-device BTRFS (and weird behaviour)<!--
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
-->
With a multi-device BTRFS filesystem (in "RAID 0" mode), GNOME Disks shows an entry for each partition that is part of the FS.
When one entry is mounted, clicking on the "unmounted" entry makes it mounted under another path.
![image_2021-11-22_20-25-00](/uploads/a74fa30d293923890c5842a3166e9752/image_2021-11-22_20-25-00.png)
I'd also like to add that GNOME Disks also says that the other disk is not mounted and shows a button to mount it (in addition to bug GNOME/gnome-disk-utility#24).
![image_2021-11-22_19-58-18](/uploads/f4f84ad5b3897b3a235cc979d38eadcf/image_2021-11-22_19-58-18.png)
I have this line in `/etc/fstab`: `UUID=d5051876-e61b-4e1a-96cf-xxxxxxxf43 /mnt/FastExtraLinuxFiles auto nosuid,nodev,nofail,x-gvfs-show 0 0`.
# Affected version
- Nightly flatpak: Yes
- Other: ArchLinux / GNOME Files 41.1
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Use `btrfs device add` to add another disk to an existing FS.
2. Open GNOME Files.
3. Click the "not mounted" entry on the left (this works as many times as you want).
# Current behavior
The duplicated-but-unmounted entry is mounted under /run/media/.../FastExtraLinuxFiles{,1,2,3,...}
# Expected behavior
The entry should not exist.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2048Better search by date (choose range of dates)2021-12-08T01:05:47ZAlexey FedorovBetter search by date (choose range of dates)### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
I am using: Gnome files 41.1 (fedora 35)
Sometimes a user needs to find a file in a range of dates.
Something like:
1. S...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
I am using: Gnome files 41.1 (fedora 35)
Sometimes a user needs to find a file in a range of dates.
Something like:
1. Search
2. by date
3. choose the range
would be a great thing to have
### Desired behavior
<!-- Describe the desired functionality. -->
That would be nice to have easier search by date dialogue
and the option to choose the range of dates in gnome files
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
It is will be more helpful for people who work with big databases
That is an example of how windows does that
![Screenshot](/uploads/eecd331d3ed6a58ba3c8b857e6aa91c8/Screenshot.png)
### Possible drawbacks
<!--
Night change the layout of search in gnome files
needs to be implemented(?)
-->
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2049Cannot create symlink between different hard drives2022-12-27T22:11:33Zmawiabdurahman.elmawi06@gmail.comCannot create symlink between different hard drivesWhen I use ctrl-shift-drag to create a symlink, it only works if the symlink and the original file are on the same drive. If I try to do it between different drives, it doesn't work. I can use the context menu to create a link and it wor...When I use ctrl-shift-drag to create a symlink, it only works if the symlink and the original file are on the same drive. If I try to do it between different drives, it doesn't work. I can use the context menu to create a link and it works if I then drag over the created symlink to the other drive in question.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2075Incorrect tooltip position on ultra widescreen2022-12-24T00:47:35ZArtur O.Incorrect tooltip position on ultra widescreen# Affected version
- Other: Files 41.1 (wayland)
# Steps to reproduce
1. Open on ultra wide (currently tested on 5120x1440 monitor)
2. Ctrl + L (to enter path)
# Current behavior
When Files is open on the ultra wide screen the autocomp...# Affected version
- Other: Files 41.1 (wayland)
# Steps to reproduce
1. Open on ultra wide (currently tested on 5120x1440 monitor)
2. Ctrl + L (to enter path)
# Current behavior
When Files is open on the ultra wide screen the autocomplete dropdown is not shown directly below but right side of the application. Opening same files on a different monitor will show as expected.
![image](/uploads/2f71205663378ea6671eb805fcf76d96/image.png)
![image](/uploads/bae2475235f028f91604b75f4ed8350d/image.png)
# Expected behavior
Directly below (opened on my portrait monitor 2560x1440)
![image](/uploads/ee79a2d343cb1c3499ba5b407c52871b/image.png)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2127When manually replacing or skipping a lot of files, the dialog keeps change t...2023-10-27T00:24:14ZGhost UserWhen manually replacing or skipping a lot of files, the dialog keeps change the position![output](/uploads/646f3a50af5787649038cf76e67a27a1/output.mp4)
### How to reproduce
1. Duplicate the files and then merge to the previous folder to trigger the replace/skip dialog.
### Expected behavior
The dialog shouldn't change the...![output](/uploads/646f3a50af5787649038cf76e67a27a1/output.mp4)
### How to reproduce
1. Duplicate the files and then merge to the previous folder to trigger the replace/skip dialog.
### Expected behavior
The dialog shouldn't change the place randomly.
### Additional info
GNOME 41, Nautilus 41.2https://gitlab.gnome.org/GNOME/nautilus/-/issues/2150Trying to open a file from the overview doesn't work, results in `nautilus --...2022-03-01T16:05:41ZAdam WilliamsonTrying to open a file from the overview doesn't work, results in `nautilus --gapplication-service` process stuck at 100% CPUIn GNOME 42, if I try to open a file from the overview - e.g. search for a recently-edited text file, find it, and click on it - it does not open as expected (in my default text editor). Nothing appears to happen, except my CPU fan start...In GNOME 42, if I try to open a file from the overview - e.g. search for a recently-edited text file, find it, and click on it - it does not open as expected (in my default text editor). Nothing appears to happen, except my CPU fan starts spinning up. On closer inspection, a `/usr/bin/nautilus --gapplication-service` process is stuck at 100% CPU usage until I kill it, whereupon it goes away. If I open the overview again and search for the file again, the process starts again, but isn't stuck hogging the CPU; if I try to open the file again, it again doesn't work and the process starts hogging the CPU.
I'm on Fedora Rawhide, with gnome-shell-42~alpha-3.fc36.x86_64 and nautilus-42~alpha-3.fc36.x86_64 .https://gitlab.gnome.org/GNOME/nautilus/-/issues/2162Incorrect zipped filenames & permissions when compressing remote object2022-02-23T19:19:08ZClocksIncorrect zipped filenames & permissions when compressing remote object# Affected version
- Nightly flatpak: Yes
- Fedora, 41.2
# Steps to reproduce
1. Connect a network drive, such as google drive.
2. Create a folder with contents. Contents can be files or folders
3. Compress the folder
4. Copy newly com...# Affected version
- Nightly flatpak: Yes
- Fedora, 41.2
# Steps to reproduce
1. Connect a network drive, such as google drive.
2. Create a folder with contents. Contents can be files or folders
3. Compress the folder
4. Copy newly compressed file to a local storage
5. Extract compressed file.
6. Examine the contents of the newly created folder & permissions
# Current behavior
The file names are hashed(?) and the permissions require sudo to open up.
# Expected behavior
The file names are correct, and the permissions properly set.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2174The "show hidden" files setting turns off after reboot/logoff2022-02-28T00:12:36ZPavanThe "show hidden" files setting turns off after reboot/logoff# Affected version
- 40.2
# Steps to reproduce
- Open files,
- Enable "show hidden" files
- logoff or reboot
- login back to your user account and open files.
- Files don't remember "show hidden" enable setting as a result all hidden f...# Affected version
- 40.2
# Steps to reproduce
- Open files,
- Enable "show hidden" files
- logoff or reboot
- login back to your user account and open files.
- Files don't remember "show hidden" enable setting as a result all hidden files don't show-uphttps://gitlab.gnome.org/GNOME/nautilus/-/issues/2179Crash when remounting share2022-08-28T09:10:50ZSebastiaan LokhorstCrash when remounting shareWhen I connect to a share, e.g. sftp://localhost/, it is mounted and shown in the sidebar. If I then disconnect from it by clicking the "eject" button, and reconnect to it again, Nautilus crashes.
I get the following message in the term...When I connect to a share, e.g. sftp://localhost/, it is mounted and shown in the sidebar. If I then disconnect from it by clicking the "eject" button, and reconnect to it again, Nautilus crashes.
I get the following message in the terminal:
```
ERROR:../nautilus/src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file))
Bail out! ERROR:../nautilus/src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file))
fish: Job 1, 'nautilus' terminated by signal SIGABRT (Abort)
```
Note: I already reported this in 2015 with GNOME 3.18.0. See [Bugzilla 755671](https://bugzilla.gnome.org/show_bug.cgi?id=755671) Behavior now (with nautilus 41.2) is exactly then same, but the error message has changed.
Possibly related to #1324?https://gitlab.gnome.org/GNOME/nautilus/-/issues/2200Adding a bookmark briefly freezes the app2022-04-06T23:18:53ZTobias BernardAdding a bookmark briefly freezes the appWhen hitting Ctrl+D to add the current location to bookmarks, the app hangs for about 5s. During this time it doesn't respond to any input and it just frozen. After that the bookmark shows up in the sidebar and the app is usable again.
...When hitting Ctrl+D to add the current location to bookmarks, the app hangs for about 5s. During this time it doesn't respond to any input and it just frozen. After that the bookmark shows up in the sidebar and the app is usable again.
Removing a bookmark has the same effect.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2216Files crashes when "Link here" is used2022-04-06T07:20:42ZsantiagoFiles crashes when "Link here" is used<!--
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: Can't test it because Alt key (which when pressed while drag&drop opens the "wthat-to-do-with-the-file-here" menu) doesn't seem to work in my installed Nightly version.
- Other: 40.2
# Steps to reproduce
1. Select a file
2. Drag & drop the file to a folder while pressing Alt key
3. Choose the option "Link Here" in the menu that opens.
# Current behavior
Files crashes (although the link is created). The last two lines are the ones written when the crash happens:
![image](/uploads/684f05d7bf5090a7ca9141794e6fbe3a/image.png)
# Expected behavior
Files should create the link and continue to work normally.
# Additional information
- I was in a Wayland session.
- Log fron gdb when running Files:
```
(org.gnome.Nautilus:667855): Gtk-WARNING **: 00:46:23.747: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
[Thread 0x7fffcb7fe640 (LWP 667874) exited]
[Thread 0x7fffda253640 (LWP 667872) exited]
[Thread 0x7fffdab6a640 (LWP 667871) exited]
[Thread 0x7ffff18c8640 (LWP 667863) exited]
[Thread 0x7fffcbfff640 (LWP 667873) exited]
[New Thread 0x7fffcbfff640 (LWP 667884)]
[New Thread 0x7fffdab6a640 (LWP 667885)]
[New Thread 0x7fffda253640 (LWP 667886)]
[Thread 0x7fffdab6a640 (LWP 667885) exited]
[Thread 0x7fffcbfff640 (LWP 667884) exited]
[Thread 0x7fffda253640 (LWP 667886) exited]
[New Thread 0x7fffda253640 (LWP 667887)]
[New Thread 0x7fffcbfff640 (LWP 667888)]
[Thread 0x7fffd99a4640 (LWP 667870) exited]
[Thread 0x7fffda253640 (LWP 667887) exited]
(org.gnome.Nautilus:667855): Gdk-CRITICAL **: 00:46:31.770: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed
Gdk-Message: 00:46:33.145: Error reading events from display: Invalid argument
[Thread 0x7fffcbfff640 (LWP 667888) exited]
[Thread 0x7ffff0859640 (LWP 667864) exited]
[Thread 0x7ffff20f3640 (LWP 667862) exited]
[Thread 0x7ffff28f4640 (LWP 667860) exited]
[Thread 0x7ffff3175ac0 (LWP 667855) exited]
[Inferior 1 (process 667855) exited with code 01]
```
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2224Open directory should use the parent if there's none in the current2022-04-12T13:42:50ZDevorlonOpen directory should use the parent if there's none in the current### Use cases
When selecting 'Open Directory' in VLC I navigate to the dir I want, but then have to move up to the parent to select the one I was previously inside.
### Desired behavior
If the currently viewed directory doesn't have any...### Use cases
When selecting 'Open Directory' in VLC I navigate to the dir I want, but then have to move up to the parent to select the one I was previously inside.
### Desired behavior
If the currently viewed directory doesn't have any directory's inside of it then the parent should be used.
### Benefits of the solution
Quicker for those with bookmarks and 'starred' directories.
(IMO) More intuitive as you select the directory you're currently in.
### Possible drawbacks
Inconsistent for users (One might not realise that they can select the pwd if it only contain files).
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2239GtkMountOperation assumes X11, throws exception on Wayland2022-04-26T23:20:23ZCorey BerlaGtkMountOperation assumes X11, throws exception on WaylandI'm having a hard time tracking down the exact behavior, but in Nautilus, if I put something in the Trash and immediate eject / unmount, when g_mount_unmount_with_operation() is called, I get an exception
invalid cast from 'GdkWaylandDi...I'm having a hard time tracking down the exact behavior, but in Nautilus, if I put something in the Trash and immediate eject / unmount, when g_mount_unmount_with_operation() is called, I get an exception
invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
I'm not sure if this is just because it's run within a Flatpakhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/2243Failure to connect to sftp or ssh server with 2FA enabled2022-05-03T14:57:22ZKrupski19Failure to connect to sftp or ssh server with 2FA enabled<!--
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: Nautalis 42 in Pop_OS! 22.04
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Connect to 2FA enabled server in Other Locations in the connect to server option
2. Tries to connect, with no verification window popping up
3. Fails to connect to server
# Current behavior
When trying to connect to a 2FA protected ssh or sftp server in Nautalis, the verification window to enter the 2FA code no longer appears, and the 2FA code cannot be entered to access the server.
# Expected behavior
As in previous versions, a verification code window should appear to allow me to enter in the 2FA code to succesffuly access the sftp server.
# Additional information
Running on Pop_OS 20.04 with Files version 42 with Gnome version 42
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2245nautilus[1281]: Unable to get contents of the bookmarks file: Error opening f...2022-05-31T13:26:23Zsoloturnnautilus[1281]: Unable to get contents of the bookmarks file: Error opening file /home/st/.gtk-bookmarks: No such file or directorywhen logging into gnome the error is printed:
```
nautilus[1281]: Unable to get contents of the bookmarks file: Error opening file /home/st/.gtk-bookmarks: No such file or directory
```
am not sure it needs this file. if not, this should...when logging into gnome the error is printed:
```
nautilus[1281]: Unable to get contents of the bookmarks file: Error opening file /home/st/.gtk-bookmarks: No such file or directory
```
am not sure it needs this file. if not, this should not be an error in the journal viewable be root. in case it does, it would be cool to point to the .config/gtk-4.0 directory.
version: nautilus 42.1.1-1https://gitlab.gnome.org/GNOME/nautilus/-/issues/2263How to get the non-file rightclick menu when files is in list view?2022-05-14T11:34:09ZHernan VagoHow to get the non-file rightclick menu when files is in list view?I'm reporting the same problem stated [here](https://askubuntu.com/questions/1189971/how-to-get-the-non-file-rightclick-menu-when-files-is-in-list-view)
In my view this is an important usability problem.
**PROBLEM DESCRIPTIOM**
When G...I'm reporting the same problem stated [here](https://askubuntu.com/questions/1189971/how-to-get-the-non-file-rightclick-menu-when-files-is-in-list-view)
In my view this is an important usability problem.
**PROBLEM DESCRIPTIOM**
When Gnome Files (nautilus) is in list view I sometimes still want to open the right-click menu that otherwise appears when you right-click into the empty space of a folder. (The one that lets you open the terminal etc.) Is that somehow possible?
Here a screenshot of the current situation: Where the menu of the corresponding file opens.
![screenshot](/uploads/3fcf2f30f374176e21dea17addaf2f42/screenshot.png)
**SO and package versions**
I'm having this problem in my Ubuntu Desktop
Ubuntu: Ubuntu 20.04.4 LTS
Package: nautilus Version: 1:3.36.3-0ubuntu1.20.04.1
Thank you very much.
Hernanhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/2270Unmounting unmounts both partition and device2022-05-26T06:16:17ZNils WernerUnmounting unmounts both partition and device# Affected version
- Other: Arch Linux, GNOME nautilus 42.1.1
# Steps to reproduce
1. Plug in a removable mass media device, wait for it to be mounted
1. Look at it in Disk Utility. You can see the partitions.
1. Unmount it in Nautilus...# Affected version
- Other: Arch Linux, GNOME nautilus 42.1.1
# Steps to reproduce
1. Plug in a removable mass media device, wait for it to be mounted
1. Look at it in Disk Utility. You can see the partitions.
1. Unmount it in Nautilus
1. The partitions in Disk Utility disappear. You cannot work with the device again unless you unplug it and plug it in again.
1. Unplug and plug it in again, wait for it to be mounted.
1. Unmount the partition in Disk Utility.
1. The device and partitions are visible in Disk Utility. You can work with the device.
# Current behavior
Nautilus somehow unmounts the partition and the device. You cannot work with the device again unless you remove and plug it back in.
# Expected behavior
Nautilus should only unmount the partition and leave the device available.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/227542.2: test suite is failing2023-02-28T01:56:40ZTomasz Kłoczko42.2: test suite is failingLooks like just released 42.2 test suite is failing
```
+ cd nautilus-42.2
+ /usr/bin/meson test -C x86_64-redhat-linux-gnu --num-processes 48 --print-errorlogs
ninja: Entering directory `/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_6...Looks like just released 42.2 test suite is failing
```
+ cd nautilus-42.2
+ /usr/bin/meson test -C x86_64-redhat-linux-gnu --num-processes 48 --print-errorlogs
ninja: Entering directory `/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu'
[1/135] Generating config.h with a custom command
fatal: not a git repository (or any parent up to mount point /home/tkloczko)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=1926049 comm="/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64" label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gtk.vfs.Daemon'
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gtk.vfs.Metadata' requested by ':1.1' (uid=1000 pid=1926052 comm="/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64" label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.freedesktop.Tracker3.Miner.Files' requested by ':1.4' (uid=1000 pid=1926056 comm="/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64" label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gtk.vfs.Metadata'
1/14 validate-desktop OK 0.14s
2/14 validate-desktop-autorun-software OK 0.13s
3/14 validate-appdata OK 0.13s
4/14 test-file-utilities-get-common-filename-prefix OK 0.12s
5/14 test-eel-string-get-common-prefix OK 0.12s
6/14 test-file-operations-dir-has-files OK 0.10s
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.3' (uid=1000 pid=1926054 comm="/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64" label="system_u:system_r:unconfined_service_t:s0")
[7-14/14] 🌓 test-nautilus-search-engine-tracker 0/480s
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.799: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.799: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.799: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.799: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.799: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.800: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.800: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.800: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:26.800: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
(process:1926114): GVFS-RemoteVolumeMonitorDaemon-WARNING **: 17:58:26.812: monitor says it's not supported
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
(process:1926114): GVFS-RemoteVolumeMonitorDaemon-WARNING **: 17:58:26.816: monitor says it's not supported
(process:1926114): GVFS-RemoteVolumeMonitorDaemon-WARNING **: 17:58:26.816: monitor says it's not supported
(process:1926114): GVFS-RemoteVolumeMonitorDaemon-WARNING **: 17:58:26.816: monitor says it's not supported
(process:1926114): GVFS-RemoteVolumeMonitorDaemon-WARNING **: 17:58:27.027: monitor says it's not supported
(tracker-miner-fs-3:1926089): GVFS-RemoteVolumeMonitor-WARNING **: 17:58:27.027: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.11' (uid=1000 pid=1926089 comm="/usr/libexec/tracker-miner-fs-3 " label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gtk.vfs.GoaVolumeMonitor' requested by ':1.11' (uid=1000 pid=1926089 comm="/usr/libexec/tracker-miner-fs-3 " label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gnome.OnlineAccounts' requested by ':1.15' (uid=1000 pid=1926160 comm="/usr/libexec/gvfs-goa-volume-monitor" label="system_u:system_r:unconfined_service_t:s0")
7/14 test-file-operations-trash-or-delete FAIL 0.33s killed by signal 5 SIGTRAP
>>> GSETTINGS_SCHEMA_DIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/data G_TEST_SRCDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/test/automated/displayless MALLOC_PERTURB_=168 G_TEST_BUILDDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless RUNNING_TESTS=TRUE /home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-trash-or-delete
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stdout:
# random seed: R02S0867383c1c4ccca0884f70bed00186a7
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
1..14
# Start of test-trash-one-file tests
Bail out! GVFS-RemoteVolumeMonitor-FATAL-WARNING: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
stderr:
(/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-trash-or-delete:1926081): GVFS-RemoteVolumeMonitor-WARNING **: 17:58:26.816: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
8/14 test-file-operations-copy-files FAIL 0.36s killed by signal 5 SIGTRAP
>>> GSETTINGS_SCHEMA_DIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/data G_TEST_SRCDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/test/automated/displayless G_TEST_BUILDDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless MALLOC_PERTURB_=57 RUNNING_TESTS=TRUE /home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-copy-files
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stdout:
# random seed: R02S75fc8f382d7ac4679dbd1d08a42c138e
1..26
# Start of test-copy-one-file tests
Bail out! GVFS-RemoteVolumeMonitor-FATAL-WARNING: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
stderr:
(/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-copy-files:1926071): GVFS-RemoteVolumeMonitor-WARNING **: 17:58:26.816: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
9/14 test-file-operations-move-files FAIL 0.41s killed by signal 5 SIGTRAP
>>> GSETTINGS_SCHEMA_DIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/data G_TEST_SRCDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/test/automated/displayless G_TEST_BUILDDIR=/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless RUNNING_TESTS=TRUE MALLOC_PERTURB_=27 /home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-move-files
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stdout:
# random seed: R02Se2eab02f361d4c5f985b99892fb608bb
1..39
# Start of test-move-one-file tests
Bail out! GVFS-RemoteVolumeMonitor-FATAL-WARNING: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
stderr:
(/home/tkloczko/rpmbuild/BUILD/nautilus-42.2/x86_64-redhat-linux-gnu/test/automated/displayless/test-file-operations-move-files:1926054): GVFS-RemoteVolumeMonitor-WARNING **: 17:58:26.816: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
goa-daemon-Message: 17:58:27.135: goa-daemon version 3.44.0 starting 0/480s
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Activating service name='org.gnome.Identity' requested by ':1.16' (uid=1000 pid=1926164 comm="/usr/libexec/goa-daemon" label="system_u:system_r:unconfined_service_t:s0")
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gnome.OnlineAccounts'
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
(tracker-miner-fs-3:1926089): libupower-glib-WARNING **: 17:58:27.159: Couldn't connect to proxy: Could not connect: Connection refused
(tracker-miner-fs-3:1926089): Tracker-WARNING **: 17:58:27.159: Unable to connect to UPower
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.gnome.Identity'
dbus-daemon[1926025]: [session uid=1000 pid=1926025] Successfully activated service 'org.freedesktop.Tracker3.Miner.Files'
10/14 test-nautilus-search-engine-simple OK 0.75s
11/14 test-nautilus-search-engine OK 0.80s
12/14 test-nautilus-search-engine-model OK 0.78s
13/14 test-file-utilities OK 1.22s
14/14 test-nautilus-search-engine-tracker OK 1.40s
Summary of Failures:
7/14 test-file-operations-trash-or-delete FAIL 0.33s killed by signal 5 SIGTRAP
8/14 test-file-operations-copy-files FAIL 0.36s killed by signal 5 SIGTRAP
9/14 test-file-operations-move-files FAIL 0.41s killed by signal 5 SIGTRAP
Ok: 11
Expected Fail: 0
Fail: 3
Unexpected Pass: 0
Skipped: 0
Timeout: 0
```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/2314Invalid new file suggestion when compressing multiple file that spitted with...2022-07-07T07:13:43ZHamed MasafiInvalid new file suggestion when compressing multiple file that spitted with dots# Affected version
- Nightly flatpak: Can't test it because I don't have nightly version
- Other: Ubuntu 20.04
# Steps to reproduce
1. Create multiple files with names of below list:
- org.sample.file1.txt
- org.sample.file2.tx...# Affected version
- Nightly flatpak: Can't test it because I don't have nightly version
- Other: Ubuntu 20.04
# Steps to reproduce
1. Create multiple files with names of below list:
- org.sample.file1.txt
- org.sample.file2.txt
- org.sample.file3.txt
- org.sample.file4.txt
2. Select all of them and compress them
# Current behavior
The generated zip file is named `org.sample.file4..zip` (with two dots) because the common part of these names ends with a dot
# Expected behavior
I thins is better to name it `org.sample.file4.zip`
# Additional information
--No--
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2321Copying/Extracting large amounts of files into superuser directories from use...2023-09-10T23:53:13ZNereithrCopying/Extracting large amounts of files into superuser directories from user home does not work as expected# Affected version
- Nightly flatpak: Apologies, cannot test due to time constraints right now
- Other: Fedora 36, Files 42.2, btrfs
# Steps to reproduce
1. Have a folder with a very large number of files, folders, and symlinks between...# Affected version
- Nightly flatpak: Apologies, cannot test due to time constraints right now
- Other: Fedora 36, Files 42.2, btrfs
# Steps to reproduce
1. Have a folder with a very large number of files, folders, and symlinks between these files and folders. Tested with 75,000 , 150,000 and 350,000. In my example these were icon themes located in ~/.icons.
2. Either: copy these files to a superuser-only directory (/usr/share/icons in my case) OR make them into a tarball, move the tarball, extract the tarball at the destination.
3. Type in the superuser password when prompted
# Current behavior
With both copying and extraction: about 1000-2000 files are rapidly copied/extracted to the destination, then the copying/extraction stops for about 5 minutes. The copying status popover reports a speed of 900 bytes - 2 KB per second, the disk io actually states nothing is happening. As soon as 5 minutes elapse, the user is prompted for another superuser password, which copies another 1000-2000 files and the issue repeats.
# Expected behavior
2.5 issues here:
1. The files should be properly copied/extracted to their destination, seems to be some sort of access issue here.
2. In case the files are legitimately just being copied slowly (assuming several large files and slow HDDs) to superuser directories, the user should not be prompted for passwords again. In other words, superuser privileges should work for all files placed into the copy/extaction queue, even if they would have timed out normally.
2.5. Perhaps the popover should inform the user if something is going wrong
# Limitations of my tests
1. I copied using Cut and Paste or Drag and Drop, not using the copy menu
2. Copying was always done from a home folder without going superuser in that window, into a different window at the destination with elevated privileges
3. The files are copied/extracted normally when done using the terminal (using cp/mv/tar) with sudo
4. Copying/extracting within user directories works normally
5. I did not test copying between superuser directories, but considering the extraction of a tarball already within a superuser directory runs into this issue, I presume I would see similar results.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2373"Connect to Server" in Other Locations seems out of place2022-08-09T21:33:48ZGhost User"Connect to Server" in Other Locations seems out of place## Problem
![Screenshot_from_2022-07-29_18-58-28](/uploads/7d12bb8d6ce58398e70155092f5881a8/Screenshot_from_2022-07-29_18-58-28.png)
The placement of "Connect to Server" at the bottom part of the Other Locations section looks out of p...## Problem
![Screenshot_from_2022-07-29_18-58-28](/uploads/7d12bb8d6ce58398e70155092f5881a8/Screenshot_from_2022-07-29_18-58-28.png)
The placement of "Connect to Server" at the bottom part of the Other Locations section looks out of place. When connecting to a server, it appears in the Other Locations list, so why isn't there a "+ Connect to a server" item? Like this (feeling lazy to do an elaborated mockup):
![Screenshot_from_2022-07-29_19-03-29](/uploads/2a9b2923965341b8f7cda6cec590434e/Screenshot_from_2022-07-29_19-03-29.png)https://gitlab.gnome.org/GNOME/nautilus/-/issues/2395iso files does not have a good logo it is hard to see you need to read the fi...2022-08-04T17:23:00Zholequantumiso files does not have a good logo it is hard to see you need to read the file name to understand img/iso filesjust like kde files app gnome files need better logo for iso files img files for better identify themjust like kde files app gnome files need better logo for iso files img files for better identify themhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/2429Nautilus doesn't take into account dark style preference2022-09-01T13:55:59ZStan GruppNautilus doesn't take into account dark style preference# Affected version
- Nightly flatpak: Yes - 43.rc-dddf828f9
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Install or update NautilusDevel flatpak with a version from 16 August
2. Se...# Affected version
- Nightly flatpak: Yes - 43.rc-dddf828f9
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Install or update NautilusDevel flatpak with a version from 16 August
2. Set style preference to Dark in Settings
3. Open Nautilus
# Current behavior
Nautilus opens using light theme
# Expected behavior
Nautilus should open with dark theme
# Additional information
The Nautilus version coming from the GNOME OS beta ISO works ok, it opens up using dark theme.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2462Can no longer connect to server using older ssh versions using ssh-rsa keys (...2022-09-03T18:33:05ZManmilan SinghCan no longer connect to server using older ssh versions using ssh-rsa keys (as Nautilus only reads /etc/ssh/ssh_config)<!--
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 / No / Can't test it because <!-- Delete the unwanted answers -->
- Other: <!-- Write the distribution you’re using and the version of the app. -->
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. I am running GNOME nautilus 42.2, i just upgraded my system from Ubuntu 20.04 to Ubuntu 22.04 and with the new nautilus I am seeing the below behaviour
2.
3.
# Current behavior
I have a few servers I access using nautilus, I could connect to them just file when I was using Ubuntu 20.04 but now when I upgraded to 22.04 I am unable to connect to these servers. These servers use older ssh and ssh-rsa algorithms. To connect to these servers with Ubuntu 22.04 I had to add lines to .ssh/config file so that i can use older ssh-rsa algorithms. After adding the lines I can connect to these servers using my ssh-key but only in terminal mode. It does not work if I am using nautilus.
# Expected behavior
I was expecting nautilus to connect to these servers using sftp
# Additional information
<!--
This is something associated with having servers with older open-ssh and using ssh-rsa keys
-->
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2468Nautilus thumbnailing (many potentially large) files is blocking GUI, usuabil...2023-07-09T16:28:34ZPercyNautilus thumbnailing (many potentially large) files is blocking GUI, usuability improvement suggetsionsI am watching this now for years and it seams to stay unaddressed.
Thumbnailing is not only slow (OK when many large files) -- but is getting more a usability issue as it more or less blocks the nautilus GUI when busy updating many icon...I am watching this now for years and it seams to stay unaddressed.
Thumbnailing is not only slow (OK when many large files) -- but is getting more a usability issue as it more or less blocks the nautilus GUI when busy updating many icons. Also drag and drop seam to stall a lot when this happens. In some situations deadly locking nautilus and I have to kill it.
This applies to many simple jpeg images and also to other default file formats. And similar applies to custom thumbnailers. I am talking about 1000+ files here in one folder.
I suggest to better manage the thumbnail processes and give them a low (nice) priority if exceeding a larger number to files to be processed to not bog down the machine usability.
Also the gtk level "thumb nail" update of the actual generated icons seam to have a impact. This rendering process also must be managed better to not impact GUI operations.
Another related issue: When updating thumbnail icons in the file view pane -- those often shuffle around crazy (icon size changes oddly temporary, etc.) for no good reason and selecting/working with files is a bit painful. Also when inserting new appearing files -- it should be tried to not shift currently selected/highlighted files and maintain the location/scroll pos and only move icons before/after the active selection if possible.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2473Version 42.2 strange behavior with NFS shares - automatic going back to local...2023-02-03T13:49:43ZGon0SVersion 42.2 strange behavior with NFS shares - automatic going back to local mount pointHello
Running up to date Solus Linux, Solus 4.3 Fortitude in budgie version.
3.
Using Gnome filer Nautilus version 42.2 with NFS 3 shares.
When browsing local folders, no problems at all, all is fine.
When browsing NFS shares, if you...Hello
Running up to date Solus Linux, Solus 4.3 Fortitude in budgie version.
3.
Using Gnome filer Nautilus version 42.2 with NFS 3 shares.
When browsing local folders, no problems at all, all is fine.
When browsing NFS shares, if you do not have any activity in the nautilus browser on that share, the browser start to climb back the folder tree every 10-11 seconds until it arrive to the mount folder.
Already reset .config and dconf gvfs and nautilus settings recursively, without more luck.
Tried to launch nautilus with debug log with no more usefull data.
Using Caja file browser, this one in GTK too does not show this behaviour.
Same bahaviour seen on an older computer running Nautilus 42.2 too.
Any clues ?
What do you need as debug trace ? Please, give me the command line as I am not a dev nor used to debug linux app.
Best regards.https://gitlab.gnome.org/GNOME/nautilus/-/issues/247643: list of installed plugins is empty2022-09-24T16:52:02ZJeremy Bicha43: list of installed plugins is empty# Affected version
- Ubuntu 22.10
- Nautilus 43~rc-1ubuntu1
# Steps to reproduce
1. Click ☰ > About Files
2. Then Click Troubleshooting > Debugging Information
# Current behavior
My dialog shows
```
Currently installed plugins:
Fo...# Affected version
- Ubuntu 22.10
- Nautilus 43~rc-1ubuntu1
# Steps to reproduce
1. Click ☰ > About Files
2. Then Click Troubleshooting > Debugging Information
# Current behavior
My dialog shows
```
Currently installed plugins:
For bug testing only, the following command can be used:
NAUTILUS_DISABLE_PLUGINS=TRUE nautilus
```
# Expected behavior
- I have nautilus-python 4 alpha installed with 2 working extensions: gsconnect and tilix
- I also installed working installed extensions for file-roller and gnome-terminal.
# Additional information
- Ubuntu (and Debian) use multiarch by default. That makes the default extension directory `/usr/lib/x86_64-linux-gnu/nautilus/extensions-4/`
- So we also ship [a patch](https://salsa.debian.org/gnome-team/nautilus/-/blob/ubuntu/master/debian/patches/multiarch_fallback.patch) to support `/usr/lib/nautilus/extensions-4/` I don't know of anything that would use that non-multiarch directory but it seemed useful to provide that for compatibility.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2480The local 'Public' folder shows up in "Other Locations"2022-09-14T22:49:40ZMatthias ClasenThe local 'Public' folder shows up in "Other Locations"This happens if file sharing is enabled.
It is confusing at best, since it is placed under "Networks", and it most definitively is not a network location.
I would suggest that local shared folders should not be shown in this view.This happens if file sharing is enabled.
It is confusing at best, since it is placed under "Networks", and it most definitively is not a network location.
I would suggest that local shared folders should not be shown in this view.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2496Nautilus Visible columns option missing function2022-12-04T13:30:51ZCorrado VenturiniNautilus Visible columns option missing functionIn Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star'
while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the c...In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star'
while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column.
see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005https://gitlab.gnome.org/GNOME/nautilus/-/issues/2503Menu rendering artifacts under X112022-12-16T13:47:56ZChristoph ReiterMenu rendering artifacts under X11This is with 43.0 as shipped in Ubuntu 22.10 currently.
This happens a lot with context menus in the new gtk4 nautilus for me.
![Untitled](/uploads/192fc53861f7c226063954f438d81ce5/Untitled.mp4)
I suspect it's a GTK issue, but I've on...This is with 43.0 as shipped in Ubuntu 22.10 currently.
This happens a lot with context menus in the new gtk4 nautilus for me.
![Untitled](/uploads/192fc53861f7c226063954f438d81ce5/Untitled.mp4)
I suspect it's a GTK issue, but I've only seen it in Nautilus, so filing here for starters.
Using an AMD RX590 via X11, if that matters re graphics driver/mesa.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2504Search should return file name results before full text completes2023-07-09T16:28:32ZThomas DaedeSearch should return file name results before full text completes<!--
Please test if the shortcoming is overcome in the Nightly version already
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see ht...<!--
Please test if the shortcoming is overcome in the Nightly version already
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
### Use cases
<!-- Describe concrete situations in which this application isn't helpful enough.
Focus is on the end goal, not the means to get there.
Don't forget to mention any applicable requirements or constraints.
Examples from your daily usage are the most useful. -->
With Gnome 43's full text search enabled by default, it takes a very long time for the first search result to be returned. For example, searching for "screenshot" with full text on (the default every time) in my Pictures folder takes about 5 minutes before the first result is displayed. However, it's about a second with File Name only (and in Gnome 42).
### Available features and workarounds
<!-- How do you manage to achieve your goals with the current version of the application? -->
I have to select File Name every time I do a search. Having File Name be default would also be an acceptable workaround.
### Difficulties and insufficiencies
<!-- Why is the current experience unsatisfying? -->
~5 min before the first search result appears is a large regression in how I use search in 43 compared to 42 and the extra clocks to set File Name every time means in practice I avoid the feature.
### Suggested enhancements
<!-- Optionally . -->GNOME 45https://gitlab.gnome.org/GNOME/nautilus/-/issues/2508GNOME 43: shell not showing file search in overview2022-10-05T22:54:29Zsith-on-marsGNOME 43: shell not showing file search in overview<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* Your OS and vers...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* Your OS and version: Opensuse Tumbleweed
* Affected GNOME Shell version: 43.0 (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland: Wayland
### Bug summary
Searching for a file in overview shows no result, where as searching for a file in Nautilus works. It worked before the Gnome 43 update.
### Steps to reproduce
1. Make sure "Files" is enabled in Setting-Search.
2. Press the Windows button.
3. Type the name of a file.
### What happened
The overview window doesn't show the file I was searching for.
### What did you expect to happen
The file I was searching for would show up in overview.
### Relevant logs, screenshots, screencasts etc.
![image](/uploads/3240e30865b02b67cccbb39b4e669053/image.png)
![image](/uploads/172ea0bddb914399ae651d075e497a50/image.png)https://gitlab.gnome.org/GNOME/nautilus/-/issues/2521Nautilus cannot copy files to the network device2022-12-04T13:56:17ZAziz MessihaNautilus cannot copy files to the network device# Welcome to the Files issue tracker!
If you came here to report a bug with Files, please select the 'Bug' template under __Description__ above.
If you want to request a feature, please start a discussion with your idea over at https:/...# Welcome to the Files issue tracker!
If you came here to report a bug with Files, please select the 'Bug' template under __Description__ above.
If you want to request a feature, please start a discussion with your idea over at https://discourse.gnome.org/tag/nautilus.
If you want to report a shortcoming, something that Files currently does not as good as you wish it would, select the 'Shortcoming' template under __Description__ above.
If you need help regarding the usage or configuration of Files, or have a concern not covered by anything described here, please feel free to post about it at https://discourse.gnome.org/tag/nautilus.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2522Make cloudproviders optional2022-10-01T18:21:07ZrezsoMake cloudproviders optionalThe cloudproviders support is required for now. I think, the optional support is better.[optional-cloudproviders.patch](/uploads/a852e58f4ad049028a8b932ef444ede8/optional-cloudproviders.patch)The cloudproviders support is required for now. I think, the optional support is better.[optional-cloudproviders.patch](/uploads/a852e58f4ad049028a8b932ef444ede8/optional-cloudproviders.patch)https://gitlab.gnome.org/GNOME/nautilus/-/issues/2535Black screen for few seconds when switching tabs for the first time2022-12-04T18:44:03ZMOHAMMEDBILALNSBlack screen for few seconds when switching tabs for the first time<!--
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
- Other:Fedora 37 , files version :33
# Steps to reproduce
1.create a new tab
2.switch to the new tab
# Current behavior
black screen for few seconds after switching to previous tab
# Expected behavior
<!-- Describe the expected behavior. -->
# 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. -->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/2558Gnome 43: Inconsistent theming issue.2022-10-23T07:56:19ZCyber ManGnome 43: Inconsistent theming issue.Dark theme in system settings is not consistent with the one from the drop down menu resulting in weird theming.
Turning dark mode on from the menu reverts back after using apps around, turned off all extensions and the problem is still...Dark theme in system settings is not consistent with the one from the drop down menu resulting in weird theming.
Turning dark mode on from the menu reverts back after using apps around, turned off all extensions and the problem is still occurring.
Ubuntu 22.10.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2560Instability of Files after upgrading to Ubuntu 22.102022-10-25T17:09:37ZGuy ChasséInstability of Files after upgrading to Ubuntu 22.10Since upgrading to Ubuntu 22.10 I often got instability of this application. The typical case is the following: I look for a file or directory name in a Files window I get an answer, I go to the file or directory; after I want to come ba...Since upgrading to Ubuntu 22.10 I often got instability of this application. The typical case is the following: I look for a file or directory name in a Files window I get an answer, I go to the file or directory; after I want to come back in the Files window then I don't succeed a small window appears telling Files no longer reply then the Files window (all the Files windows if several are open) close.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2563Nautilus title bar and repaint glitch when moving window on Xorg2022-12-25T13:21:16ZJulynxNautilus title bar and repaint glitch when moving window on Xorg<!--
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. Inconsistently
- Other: Ubuntu 22.10 / GNOME nautilus 43.0
# Steps to reproduce
1. Open Nautilus in the home folder
2. Drag the window to the right edge of the screen and release
3. The window now fits half the screen, but the top bar is missing and the contents are drawn glitched out.
Video: https://imgur.com/Z8b4Xp1
# Current behavior
The icons change position when hovered by the mouse and the window appears "glitched" for around 3 seconds before
it fixes itself.
# Expected behavior
The window is drawn correctly and the icons dont change position when hovered by the mouse.
# Additional information
- I did not have the issue with the version of gnome and nautilus shipped with ubuntu 22.04, but it started to show after upgrading to ubuntu 22.10, which uses gnome 43 and nautilus 43.
- I could replicate the issue with and without using the NVIDIA drivers (prime-select nvidia and prime-select intel) so it is not an issue of the drivers.
- The same glitches also happen in right click menus sometimes, especially in newly created folders.
- I am not using any gnome-shell extensions.
- I am not using a custom gtk theme.
- Im using the Papyrus icon theme although that should not really make a difference.
- I could not replicate the issue with other gnome apps. Just nautilus.
- I tried "sudo apt install --reinstall nautilus" but It didn't change anything.
- [NEW!] Switching to the wayland session fixes the issue, so this must be a problem with gnome and/or Xorg when used together.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2575Changed date for copied pictures from camera not shown2023-02-06T14:24:19ZPaul MenzelChanged date for copied pictures from camera not shownUsing Debian sid/unstable with *nautilus* 43.0-1, a user reported that since around six weeks ago, transferred pictures from the smartphone (taken with the smartphone camera) do not show the change date anymore.
### Before
![with-chang...Using Debian sid/unstable with *nautilus* 43.0-1, a user reported that since around six weeks ago, transferred pictures from the smartphone (taken with the smartphone camera) do not show the change date anymore.
### Before
![with-change-date](/uploads/3f209a538cd21bd2229685891cac8502/with-change-date.png)
### After
![no-change-date](/uploads/4753b7071c7153dbb8fee07cbabbb6e5/no-change-date.png)
The EXIF information correctly show the “change date”.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2578Double clicking immediately on a folder/file does not open it2022-11-03T19:29:34ZJkoutsoumpasDouble clicking immediately on a folder/file does not open itDouble clicking quickly on file or folder, immediately (within 1 second) after opening a folder, the file or folder does not open.
# Affected version
43
# Steps to reproduce
1. open Files
2. open a folder and
3. within 1 second immedia...Double clicking quickly on file or folder, immediately (within 1 second) after opening a folder, the file or folder does not open.
# Affected version
43
# Steps to reproduce
1. open Files
2. open a folder and
3. within 1 second immediately perform a quick Double-click on a folder/file
# Current behavior
nothing happens
# Expected behavior
Folder/file should open
# Additional information
Waiting more than 1 second after opening a folder, then the quick double clicking works.
This happens with the new 43 version. Prior versions where working well.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2590"Open in terminal" option has gone / vanished ?2022-11-06T16:13:27ZColfenor"Open in terminal" option has gone / vanished ?Hi, today I realized that the for me very handy UI-option
to right-click within a gnome-files folder and select "Open in terminal" has suddenly disappeared.
![image](/uploads/bfa0447f3785eb1ea2b9f11f6eaba432/image.png)
I quickly che...Hi, today I realized that the for me very handy UI-option
to right-click within a gnome-files folder and select "Open in terminal" has suddenly disappeared.
![image](/uploads/bfa0447f3785eb1ea2b9f11f6eaba432/image.png)
I quickly checked that the last upgrade i did was
- `the gnome-shell (1:43.0-2 -> 1:43.1-1)`
so I'm not sure if this action has sth to do with the option vanishing.
Or did I miss a major design change here in "Files" ?
Anyway, is there the possibility to re-activate this option again, I'd really appreciate this
greetings!https://gitlab.gnome.org/GNOME/nautilus/-/issues/2607Alt+Home shortcut not working2022-11-14T20:52:33ZDiego MasottiAlt+Home shortcut not working<!--
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: Can't test it because not installed <!-- Delete the unwanted answers -->
- Other: 43.0<!-- Write the distribution you’re using and the version of the app. -->
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
Alt+Home shortcut
# Current behavior
<!-- Describe the current behavior. -->
In my system nothing appens
# Expected behavior
<!-- Describe the expected behavior. -->
should reposition in the home page
# 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
-->
On openSUSE thumbleweed.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2623Replacing files fail in softlinks to GVFS mounts2022-12-20T22:32:52ZToS0Replacing files fail in softlinks to GVFS mounts## DESCRIPTION
When you try to replace a file in a link to a GVFS share, an error appears. Either:
"error while copying" "error opening file" "operation not supported",
or when you deleted the file before in order to allow the copy any...## DESCRIPTION
When you try to replace a file in a link to a GVFS share, an error appears. Either:
"error while copying" "error opening file" "operation not supported",
or when you deleted the file before in order to allow the copy anyway:
"error while copying" "error opening file" "no such file or directory"
Expected behavior would be, that the file is being replaced after confirmation.
## REPRODUCTION
1) mount an SMB network share with ```gio mount smb://server/share/```
2) edit the VARS in the script below to match your environment
3) run the script below in a shell as often as you like and notice it works just fine
4) now replace the existing file in the link with Nautilus via Copy & Paste -- you get an the error
5) also the script throws similar errors now -- somehow Nautilus messed with the file system
## ENVIRONMENT
I am on Ubuntu 20.04 LTS latest.
The Fuse-mount points to an SMB share (in my case from a Synology NAS).
This error exists since some weeks - before it was fine.
---
A fix would be higly appreciated, since GVFS mounts are quite cryptic, and you can use it with links only. Currently I can barely work with Nautilus :disappointed:
Thanks a lot for looking into the issue!
## TEST SCRIPT
```
#!/bin/bash
#set -o xtrace
FILE="file"
LINK="link"
USER="1001" # see /run/user/
SERVER="server"
SHARE="share"
[ ! -d "$LINK" ] && ln -s /run/user/$USER/gvfs/smb-share:server=$SERVER,share=$SHARE/ $LINK
[ ! -f "$FILE" ] && touch $FILE
[ ! -f "$LINK/$FILE" ] && cp $FILE $LINK
echo "1st error: replace fails"
cp $FILE $LINK
echo "2nd error: delete fails"
[ -f "$LINK/$FILE" ] && rm $LINK/$FILE
echo "now replace the file in the link with Nautilus - and run the script again"
```https://gitlab.gnome.org/GNOME/nautilus/-/issues/2629unable to change / set background / wallpaper from files context menu2022-12-01T22:50:17ZGhost Userunable to change / set background / wallpaper from files context menuright clicking on an image & clicking on set as background does not work any more. earlier by clicking on an image in any folder of files i could set that image as the desktop wallpaper from the given location by selecting set as wallpap...right clicking on an image & clicking on set as background does not work any more. earlier by clicking on an image in any folder of files i could set that image as the desktop wallpaper from the given location by selecting set as wallpaper which is now set as background.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2638Explorer crash when files are drag and dropped2022-12-27T21:59:30ZNaga BalajiExplorer crash when files are drag and dropped
I have 3 Nautilus open and a Eye of gnome. When I drag and drop image from Eye of Gnome to one Nautilus, the Nautilus app quits. When app quits I don't get crash report either.
OS : Ubuntu 22
<!--
Please test if the issue has alre...
I have 3 Nautilus open and a Eye of gnome. When I drag and drop image from Eye of Gnome to one Nautilus, the Nautilus app quits. When app quits I don't get crash report either.
OS : Ubuntu 22
<!--
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 / No / Can't test it because <!-- Delete the unwanted answers -->
- Other: <!-- Write the distribution you’re using and the version of the app. -->
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1.
2.
3.
# Current behavior
<!-- Describe the current behavior. -->
# Expected behavior
<!-- Describe the expected behavior. -->
# 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. -->https://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/2652Paste greyed out / Pasting files not possible2023-10-27T00:26:05ZLuFloPaste greyed out / Pasting files not possible<!--
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: 42.0
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Copy a file (either right-click copy, or CTRL-C)
2. Try to paste it, either via menu or CTRL-V
# Current behavior
File won't be copied / paste menu option is greyed out. When I use the "copy-to" option, I can copy files no problem, so there are no permission issues.
# Expected behavior
It should copy the file / paste menu option shouldn't be greyed out
# Additional information
I run Pop!_OS 22.04 LTS, Nautilus is version 42.0. I also tried the flatpak nightly version with the same result.
<!--
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. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2679Sort order is not stored in shared network directories2022-11-30T10:52:46ZÓscarSort order is not stored in shared network directories# Affected version
- Arch Linux
- Nautilus 43.0
- X11
# Steps to reproduce
1. Open Nautilus
2. Go to a shared directory (for example a Samba share, smb://whatever/share/directory).
3. Change the sorting order (for example choose the dat...# Affected version
- Arch Linux
- Nautilus 43.0
- X11
# Steps to reproduce
1. Open Nautilus
2. Go to a shared directory (for example a Samba share, smb://whatever/share/directory).
3. Change the sorting order (for example choose the date column).
4. Exit directory
5. Enter again, the sorting order is lost.
# Current behavior
See video:
![Grabación_de_pantalla_desde_2022-11-30_09-04-41](/uploads/892f67ef828f8e04d528272c00d20322/Grabación_de_pantalla_desde_2022-11-30_09-04-41.webm)
# Expected behavior
The sorting order selected for that directory is maintained.
# Additional information
This problem has arisen with version 43.0, in previous versions of Nautilus it did not happen.https://gitlab.gnome.org/GNOME/nautilus/-/issues/2729Nautilus crashes when pressing CTRL key2022-12-24T19:19:48ZGhost UserNautilus crashes when pressing CTRL key<!--
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: No (it looks great btw!)
- Other: GNOME nautilus 43.0 - Debian bookworm/sid release 10.13 - Debian 5.19.11-1
# Steps to reproduce
1. Open nautilus
2. Press CTRL key while nautilus is on top
3. nautilus closes unexpectedly
# Current behavior
nautilus crashes as soon as CTRL keyboard key is pressed
# Expected behavior
nautilus should remain open when CTRL key is pressed since it can be useful to copy and paste a file, for instance, with key combination CTRL+C / CTRL+V.
# Additional information
- Content of `/var/log/syslog` when openning nautilus (14:39:10) and when pressing CTRL key (14:39:15)
```
Dec 14 14:39:09 ux dbus-daemon[2113]: [session uid=1000 pid=2113] Activating service name='org.gnome.Nautilus' requested by ':1.31' (uid=1000 pid=2262 comm="/usr/bin/gnome-shell")
Dec 14 14:39:10 ux dbus-daemon[2113]: [session uid=1000 pid=2113] Successfully activated service 'org.gnome.Nautilus'
Dec 14 14:39:10 ux dbus-daemon[2113]: [session uid=1000 pid=2113] Activating service name='org.gnome.DiskUtility' requested by ':1.144' (uid=1000 pid=10611 comm="/usr/bin/nautilus --gapplication-service")
Dec 14 14:39:10 ux gnome-shell[2262]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Dec 14 14:39:10 ux dbus-daemon[2113]: [session uid=1000 pid=2113] Successfully activated service 'org.gnome.DiskUtility'
Dec 14 14:39:10 ux gnome-disks[10631]: Using GtkSettings:gtk-application-prefer-dark-theme together with HdyStyleManager is unsupported. Please use HdyStyleManager:color-scheme instead.
Dec 14 14:39:15 ux nautilus[10611]: invalid cast from 'GdkWaylandToplevel' to 'GdkX11Surface'
Dec 14 14:39:15 ux nautilus[10611]: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
Dec 14 14:39:15 ux kernel: [ 6465.145238] nautilus[10611]: segfault at 21 ip 00007f6ee97c0a09 sp 00007ffc1cc257f0 error 4 in libX11.so.6.4.0[7f6ee97b2000+8b000]
Dec 14 14:39:15 ux kernel: [ 6465.145304] Code: e8 2c 21 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 49 89 d4 55 48 89 f5 53 48 8b 87 68 09 00 00 48 89 fb 48 85 c0 74 02 <ff> 10 48 89 ee 4c 89 e2 48 89 df e8 87 39 ff ff 89 c5 48 8b 83 68
```
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2731Files are emergency closed after hiding hidden elements2023-04-20T16:08:37ZMaxim Sokolovskysokolovskymaximorg@duck.comFiles are emergency closed after hiding hidden elements
# Affected version
- Nightly flatpak: No
- Other: OpenSUSE Tumbleweed, Gnome 43.1, nautilus 43.0-3.1
# Steps to reproduce
I could not establish after what action an emergency completion takes place, but I performed the following actio...
# Affected version
- Nightly flatpak: No
- Other: OpenSUSE Tumbleweed, Gnome 43.1, nautilus 43.0-3.1
# Steps to reproduce
I could not establish after what action an emergency completion takes place, but I performed the following actions:
1. I pressed the "show hidden files" button to work with them
2. I used the search, cut out, copied and planted files, including hidden.
3. After some time, I hid hidden files
4. Files are emergency closed
# Current behavior
Files are emergency closed after clicking the "Show Hidden Files" button to hide hidden files
# Expected behavior
Files does not end after such travial actions
# Additional information
In journalctl logs, I found the following
Each of the errors is coasted with the moment of emergency completion of the file manager
<details><summary>Click to expand</summary>
sudo journalctl --since "2022-12-01" | grep -i 'nautil' | grep -i 'error' | grep -i 'trap'
дек 09 17:17:50 workstation kernel: traps: nautilus[760] trap stack segment ip:55874e7758f2 sp:7fff0d762b00 error:0 in nautilus[55874e758000+b0000]
дек 11 21:53:50 workstation kernel: traps: nautilus[10604] trap stack segment ip:558d55f0a8f2 sp:7ffdae001940 error:0 in nautilus[558d55eed000+b0000]
дек 14 12:22:15 workstation kernel: traps: nautilus[15821] trap stack segment ip:55b22e6fc8f2 sp:7ffd4f018890 error:0 in nautilus[55b22e6df000+b0000]
дек 14 21:09:05 workstation kernel: traps: nautilus[2716] trap stack segment ip:56126ec848f2 sp:7ffe373c54a0 error:0 in nautilus[56126ec67000+b0000]
дек 14 21:12:42 workstation kernel: traps: nautilus[11640] trap stack segment ip:558dad6c18f2 sp:7fff86ca8400 error:0 in nautilus[558dad6a4000+b0000]
дек 14 21:17:49 workstation kernel: traps: nautilus[12180] trap stack segment ip:5625cbfaa8f2 sp:7fff96acd700 error:0 in nautilus[5625cbf8d000+b0000]
дек 15 12:06:48 workstation kernel: traps: nautilus[13567] trap stack segment ip:55e8ca2a08f2 sp:7ffdafa75750 error:0 in nautilus[55e8ca283000+b0000]
</details>https://gitlab.gnome.org/GNOME/nautilus/-/issues/2745nautilus will not open2023-06-15T00:57:21Zis itnautilus will not open
# Affected version
- Nightly flatpak: Can't test it because do not have flatpak
- Other:
- Manjaro 22.0.0 Sikaris
- nautilus 43.1-1 (extra) ([repo](https://software.manjaro.org/package/nautilus) (omg who is using animation in thei...
# Affected version
- Nightly flatpak: Can't test it because do not have flatpak
- Other:
- Manjaro 22.0.0 Sikaris
- nautilus 43.1-1 (extra) ([repo](https://software.manjaro.org/package/nautilus) (omg who is using animation in their navigation in their UI in 2022?!))
- xfwm4 version 4.16.1 (revision 5f61a84ad) for Xfce 4.16 Compiled against GTK+-3.24.30, using GTK+-3.24.35.
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Open nautilus (via application finder or terminal)
# Current behavior
Via application finder: Nothing happens.
Via terminal:
```sh
~ nautilus
Namespace Nautilus is already loaded with version 4.0
```
I tried all the options listed in `--help-all` but other than `-h` and `--help-all` they all produced the same result as above.
# Expected behavior
Nautilus should open.
# Additional information
I have 2 machines with environment as described above although not identical in all other ways. This behaviour has been happening on both of them for a few weeks but not sure when it started. It is not intermittent; nautilus will absolutely not open. It is not running and cannot be killed. Details below are only from the machine I am currently using. I tried uninstalling and reinstalling and updating everything.
I searched this tracker and found similar sounding issues but I do not think the same. But I might be wrong I am just an end user. So apologies if duplication.
In another issue I saw someone had run this to produce more info:
```sh
~ G_MESSAGES_DEBUG=all nautilus
(org.gnome.Nautilus:11056): GLib-GIO-DEBUG: 16:58:27.337: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(org.gnome.Nautilus:11056): GLib-GIO-DEBUG: 16:58:27.344: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(org.gnome.Nautilus:11056): Tracker-DEBUG: 16:58:27.352: Loading ontologies from database.
(org.gnome.Nautilus:11056): Tracker-DEBUG: 16:58:27.354: Applying ontologies from /usr/share/nautilus/ontology to existing database
(org.gnome.Nautilus:11056): Tracker-DEBUG: 16:58:27.356: Current and DB locales match: 'C'
(org.gnome.Nautilus:11056): Gtk-DEBUG: 16:58:27.486: Connecting to session manager
(org.gnome.Nautilus:11056): Gtk-DEBUG: 16:58:27.486: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.491: Theme parser error: gtk.css:1777:3-26: No property named "-GtkArrow-arrow-scaling"
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.495: Theme parser error: gtk.css:4505:31-35: Junk at end of value for -gtk-icon-shadow
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.495: Theme parser error: gtk.css:4509:31-35: Junk at end of value for -gtk-icon-shadow
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.496: Theme parser error: gtk.css:4545:18-22: Negative values are not allowed
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.496: Theme parser error: gtk.css:4703:21-28: Expected a valid color.
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.497: Theme parser error: gtk.css:4797:21-28: Expected a valid color.
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.497: Theme parser error: gtk.css:4927:21-28: Expected a valid color.
(org.gnome.Nautilus:11056): Gtk-WARNING **: 16:58:27.497: Theme parser error: gtk.css:5015:20-21: Unit is missing.
(org.gnome.Nautilus:11056): GLib-GIO-DEBUG: 16:58:27.738: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.738: watch_fast: "/org/gnome/nautilus/preferences/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/nautilus/compression/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/nautilus/window-state/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/nautilus/icon-view/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/nautilus/list-view/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gtk/gtk4/settings/file-chooser/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_established: "/org/gnome/nautilus/preferences/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_established: "/org/gnome/nautilus/compression/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.739: watch_established: "/org/gnome/nautilus/window-state/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gnome/nautilus/icon-view/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gnome/nautilus/list-view/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gtk/gtk4/settings/file-chooser/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gnome/desktop/interface/" (establishing: 1)
(org.gnome.Nautilus:11056): dconf-DEBUG: 16:58:27.740: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1)
(org.gnome.Nautilus:11056): GLib-DEBUG: 16:58:27.774: setenv()/putenv() are not thread-safe and should not be used after threads are created
Namespace Nautilus is already loaded with version 4.0
```
My eyes immediately went to the the only thing I know anything (not much) about, which is theming. I wondered if the messy custom themes I am running were causing the problem so I changed to `Default` for xfwm4 theme (in Window Manager setting panel) and `Adapta` for the gtk theme (in Appearance setting panel). I also ran `xfwm4 --replace &` after to restart the WM because occasionally that solves something. The above is from *after* this.
So I was looking at this line:
```sh
Theme parser error: gtk.css:1777:3-26: No property named "-GtkArrow-arrow-scaling"
```
And went into my themes directory to look for this and found:
```sh
~ ag "GtkArrow-arrow-scaling" | ag 1777
Fluent-Dark-compact/gtk-4.0/gtk.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-compact/gtk-4.0/gtk-dark.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent/gtk-4.0/gtk-dark.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-Light-compact/gtk-4.0/gtk.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-Light-compact/gtk-4.0/gtk-dark.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-Light/gtk-4.0/gtk.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-Light/gtk-4.0/gtk-dark.css:1777: -GtkArrow-arrow-scaling: 1;
Fluent-Dark/gtk-4.0/gtk.css:1777: -GtkArrow-arrow-scaling: 1;
```
And I also tried the same for another line,
```sh
gtk.css:4505:31-35: Junk at end of value for -gtk-icon-shadow
```
with similar result:
```sh
~ ag "gtk-icon-shadow" | ag 4505
Fluent-Dark-compact/gtk-4.0/gtk.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-compact/gtk-4.0/gtk-dark.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent/gtk-4.0/gtk-dark.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-Light-compact/gtk-4.0/gtk.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-Light-compact/gtk-4.0/gtk-dark.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-Light/gtk-4.0/gtk.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-Light/gtk-4.0/gtk-dark.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
Fluent-Dark/gtk-4.0/gtk.css:4505: -gtk-icon-shadow: 0 3px 2px -2px rgba(0, 0, 0, 0.2), 0 3px 2.4px 0 rgba(0, 0, 0, 0.14), 0 1px 4.8px 0 rgba(0, 0, 0, 0.12);
```
Fluent is a theme I installed manually from [this repo](https://github.com/vinceliuice/Fluent-gtk-theme) but do not use in particular. I do not know why Nautilus is looking at it.
I uninstalled the Fluent theme and tried again. Unfortunately same result (no nautilus) however the output changed:
```sh
~ G_MESSAGES_DEBUG=all nautilus
(org.gnome.Nautilus:12026): GLib-GIO-DEBUG: 17:24:51.595: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(org.gnome.Nautilus:12026): GLib-GIO-DEBUG: 17:24:51.601: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(org.gnome.Nautilus:12026): Tracker-DEBUG: 17:24:51.609: Loading ontologies from database.
(org.gnome.Nautilus:12026): Tracker-DEBUG: 17:24:51.611: Applying ontologies from /usr/share/nautilus/ontology to existing database
(org.gnome.Nautilus:12026): Tracker-DEBUG: 17:24:51.612: Current and DB locales match: 'C'
(org.gnome.Nautilus:12026): Gtk-DEBUG: 17:24:51.720: Connecting to session manager
(org.gnome.Nautilus:12026): Gtk-DEBUG: 17:24:51.720: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
(org.gnome.Nautilus:12026): GLib-GIO-DEBUG: 17:24:51.955: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.955: watch_fast: "/org/gnome/nautilus/preferences/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.955: watch_fast: "/org/gnome/nautilus/compression/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.955: watch_fast: "/org/gnome/nautilus/window-state/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.955: watch_fast: "/org/gnome/nautilus/icon-view/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_fast: "/org/gnome/nautilus/list-view/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_fast: "/org/gtk/gtk4/settings/file-chooser/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/nautilus/preferences/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/nautilus/compression/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/nautilus/window-state/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/nautilus/icon-view/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/nautilus/list-view/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gtk/gtk4/settings/file-chooser/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/desktop/interface/" (establishing: 1)
(org.gnome.Nautilus:12026): dconf-DEBUG: 17:24:51.956: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1)
(org.gnome.Nautilus:12026): GLib-DEBUG: 17:24:51.990: setenv()/putenv() are not thread-safe and should not be used after threads are created
Namespace Nautilus is already loaded with version 4.0
```
So I managed to eliminate a few lines although I have no idea why and probably it is of no use.
The only other useful (or not) contribution I have is that the above did remind me that when I was looking on reddit I found this thread from a couple weeks ago: [Lxappearance doesn't work on nautilus after recent update](https://old.reddit.com/r/ManjaroLinux/comments/zd3b0b/lxappearance_doesnt_work_on_nautilus_after_recent/). But I do not know if it is related.
I did try running `GTK_THEME=Adapta nautilus` with and without `G_MESSAGES_DEBUG=all`, before and after removing the Fluent theme and it made no difference in any case. In the past I have noticed nautilus doesn't totally jive with gtk themes in xfce, such as if you change the theme sometimes it doesn't keep up, which is not something I have noticed from any other application. But I do not know how to reproduce it reliably and that would be solved by killing nautilus. But maybe there is something funny happening.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2805Thumbnails for local files is not generated2023-04-29T14:13:14ZNikita ShvetsThumbnails for local files is not generated<!--
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: Can't test it because of [this issue](https://github.com/flatpak/flatpak/issues/3069)
- Other: Debian 12, Nautilus 43.2
# Steps to reproduce
1. Clear .cache/thumbnails/fail
2. Open folder with pictures and videos in Nautilus 43.2
# Current behavior
Thumbnails is not generated, folder .cache/thumbnails/fail/gnome-thumbnail-factory get filled with 1-pixel-sized files
# Expected behavior
Thumbnails is generated.
# Additional information
Using aarch64 build of the app.
If thumbnails is pre-generated by Thunar, the it's displayed by Nautilus too. However Nautilus itself can not generate thumbnails.
Somehow running Nautilus via `G_MESSAGES_DEBUG=all NAUTILUS_DEBUG=Thumbnails nautilus` command does not produce meaningful output, as I getting debug log of startup process and then Nautilus fork itself, and debug output is stopped, while Nautilus is still running.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2810trashing a file while the folder is loading scrolls to bottom2023-04-08T13:49:20Ztwotrashing a file while the folder is loading scrolls to bottom# Affected version
- Nightly flatpak: No, because currently window is empty until completely loaded (another bug?)
- Other: Nautilus 43.2 (Debian)
<!-- Ignore the text under this line. --># Affected version
- Nightly flatpak: No, because currently window is empty until completely loaded (another bug?)
- Other: Nautilus 43.2 (Debian)
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2823shuffled images while sellecting sort by modified/created.2023-04-09T18:04:17Zopeni strongshuffled images while sellecting sort by modified/created.# Affected version
- Nightly flatpak: Yes on a fedora rawhide running on a vm issue was present there.
# Steps to reproduce
I find that while scrolling through my images nautilus it shuffled all images which is a big issue as i see 2016...# Affected version
- Nightly flatpak: Yes on a fedora rawhide running on a vm issue was present there.
# Steps to reproduce
I find that while scrolling through my images nautilus it shuffled all images which is a big issue as i see 2016images after 2022 and again 2015stange in both case modified and created but after opening same photos on my phones google photos app (after transferring them from pc to phone) they sorted by time
1.if you have lots of images like a library full of 7-8years of photos just make a folder and add them to that folder
2.now see them it will be sorted randomly like it follows the date but not in ascending / descending order
3.it is random like i find 2016 and 2022 in same area
# Current behavior
some pictures are randomly placed i have attaching a 2 screenshot to show you the issue![Screenshot_from_2023-01-29_14-33-23](/uploads/6a418e7e5b9afbf8452302f84d267c36/Screenshot_from_2023-01-29_14-33-23.png)
![Screenshot_from_2023-01-29_14-50-39](/uploads/640323c0e2618cc5390df707b629dd88/Screenshot_from_2023-01-29_14-50-39.png)
as you can see images are not in order like i have images captured in 2023 but they are bellow 2022 images the images libary starts from the 2022 images but
2023 pictures are at middle of that library you can see the scroll bar placement
![Screenshot_from_2023-01-29_14-41-54](/uploads/bc22870d36504b8293e4ab34ab1137d3/Screenshot_from_2023-01-29_14-41-54.png)
and in both case you can see the photos of 2023 which should be on the last or first on the list but i have 2022 pictures even after adding yesterdays pictures they are also not added after that but are placed middle of the library but i just sent those same pictures to my phone and mac they were rightly placed on those devices.![Screenshot_from_2023-01-29_14-38-59](/uploads/04cabdfe228f0899dc27f695148d28df/Screenshot_from_2023-01-29_14-38-59.png)
![Screenshot_from_2023-01-29_14-39-34](/uploads/f7fd017fd20b32f65f92f4aa4066c09e/Screenshot_from_2023-01-29_14-39-34.png)
# Expected behavior
it should be according to time as it is in my mac and android photos.
I find this issue long back when i was using gnome 42 maybe issue was there before that but i never saw as i was not a gnome user at that time on kde.
i find it was exactly what it was taken time by time. I think nautilus can't fetch the metadata of the images that is why issues like this happens.