Files issueshttps://gitlab.gnome.org/GNOME/nautilus/-/issues2024-03-09T10:02:21Zhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/3355Unable to undo action when deleting latest file of a folder2024-03-09T10:02:21ZAlessandro BonoUnable to undo action when deleting latest file of a folder# Affected Version
- Version: NautilusDevel
- Distribution: Flatpak
- Also happens with development version: Yes
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
1. Create a folder `test`
2. Enter inside ...# Affected Version
- Version: NautilusDevel
- Distribution: Flatpak
- Also happens with development version: Yes
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
1. Create a folder `test`
2. Enter inside folder `test`
3. Create a folder `test1` inside the folder `test`
4. Move to trash folder `test1`
5. Click the `Undo` button in the Toast
# Expected Behavior
The folder `test1` gets moved back from the trash.
# Actual Behavior
Nothing happens and the view keeps being empty.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3343Trash: banner state is incorrect when auto empty trash is enabled (Flatpak)2024-03-05T00:00:25ZAutomeris naranjaTrash: banner state is incorrect when auto empty trash is enabled (Flatpak)## Affected version
46.rc- 2bf304f3d (Flatpak)
## How to reproduce
1. Go to GNOME Settings \> Privacy \> File History & Trash
2. Enable "Automatically Delete Trash Content"
3. Open Nautilus and go to the trash view
## Seen behavior
...## Affected version
46.rc- 2bf304f3d (Flatpak)
## How to reproduce
1. Go to GNOME Settings \> Privacy \> File History & Trash
2. Enable "Automatically Delete Trash Content"
3. Open Nautilus and go to the trash view
## Seen behavior
The banner won't inform that auto empty trash is enabled and the button is still "Empty Trash" instead of "Trash Settings":
![Screenshot_from_2024-03-02_03-00-15](/uploads/8b785bcff7d45488374cb710a4530dda/Screenshot_from_2024-03-02_03-00-15.png)
If an user enabled this setting y accident, they might not know that it's enabled and files can be lost.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3229Opening files doesn't add them to Recent in flatpak builds2023-12-19T10:25:04ZkramoOpening files doesn't add them to Recent in flatpak builds# Affected Version
- Version: master
- Distribution: Fedora 39
- Happens with development Flatpak: Yes
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
1. Open a file
2. Open Recent
3. The file doesn't sh...# Affected Version
- Version: master
- Distribution: Fedora 39
- Happens with development Flatpak: Yes
# Steps to reproduce <!-- Explain in detail how the issue can be reproduced. -->
1. Open a file
2. Open Recent
3. The file doesn't show up
# Expected Behavior
Files opened by Nautilus show up in its own Recent files panel.
# Additional Information
This is because the `GtkRecentManager` obtained by `gtk_recent_manager_get_default ()` uses a file in the applicaton's sanbox to save and retrieve items. GVFS however, uses the host's file.
The best fix for this would probably be for Nautilus to create a `GtkRecentManager` for the host's `recently-used.xbel` when running inside Flatpak, only falling back to get_default if it isn't available.https://gitlab.gnome.org/GNOME/nautilus/-/issues/3086Undo move to trash doesn't work in flatpak2024-02-04T07:03:04ZCorey BerlaUndo move to trash doesn't work in flatpak<!--
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: <!-- 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. Open the flatpak version of nautilus
2. Move a file to trash
3. Attempt to "Undo"
# Current behavior
<!-- Describe the current behavior. -->
Nothing happens
# Expected behavior
<!-- Describe the expected behavior. -->
File is restored from trash
# 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
-->
If you manually attempt to restore the file from trash it successfully restores. Only impacts the flatpak version. Opening an issue as this can lead to data loss.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/nautilus/-/issues/2039Flatpak specific files are installed by default2023-03-22T12:25:55ZOndrej HolyFlatpak specific files are installed by default@jtojnar mentioned on our IRC channel that the `org.gnome.Nautilus.Tracker3.Miner.Files.service` should not be probably installed by default. I would say he is right. It seems that neither `org.gnome.Nautilus.Tracker3.Miner.Extract.servi...@jtojnar mentioned on our IRC channel that the `org.gnome.Nautilus.Tracker3.Miner.Files.service` should not be probably installed by default. I would say he is right. It seems that neither `org.gnome.Nautilus.Tracker3.Miner.Extract.service` and `org.gnome.Nautilus.domain.rule` should be installed. Btw the Fedora package contains those files. So I suppose that an extra meson option needs to be added for those...https://gitlab.gnome.org/GNOME/nautilus/-/issues/1408Flatpak Nautilus can't eject device held by xdg-desktop-portal2020-06-07T23:31:19ZRaffaeleFlatpak Nautilus can't eject device held by xdg-desktop-portalNautilus 3.35 Flatpak nightly
Currently ejecting an USB device shows a warning that the xdg-desktop-portal PID is holding it, which makes "Force Eject" mandatory in a somewhat confusing way. I think the x-d-p lock on devices could be ha...Nautilus 3.35 Flatpak nightly
Currently ejecting an USB device shows a warning that the xdg-desktop-portal PID is holding it, which makes "Force Eject" mandatory in a somewhat confusing way. I think the x-d-p lock on devices could be handled more cleanly, but I do not know enough about how xdg works to suggest an alternative.
![Bildschirmvideo_von_06.03.2020_11_50_24](/uploads/d13d159ce67c292fb36c8eaf56a75982/Bildschirmvideo_von_06.03.2020_11_50_24.webm)https://gitlab.gnome.org/GNOME/nautilus/-/issues/946Nautilus on Flathub2023-08-28T17:56:14ZyodatakNautilus on Flathub### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
Install form flatpak native distribution ,get the latest stable nautilus
### Benefits of the solution
<!-- List the poss...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
Install form flatpak native distribution ,get the latest stable nautilus
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
Able to acces to the latest nautilus and correction form the latest stable
### 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. -->Khalid Abu ShawaribKhalid Abu Shawaribhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/476Investigate Flatpak extensions as a way to support Nautilus plugins2021-06-14T08:52:13ZCarlos SorianoInvestigate Flatpak extensions as a way to support Nautilus pluginsWhile moving development to Flatpak and while we move step by step towards supporting more a delivered Nautius flatpak, one remaining issue is to support Nautilus plugins, like Dropbox.
@ernestask pointed out that a possibility could be...While moving development to Flatpak and while we move step by step towards supporting more a delivered Nautius flatpak, one remaining issue is to support Nautilus plugins, like Dropbox.
@ernestask pointed out that a possibility could be to make them [Flatpak extensions](https://github.com/flatpak/flatpak/wiki/Extensions).
Would be good to have this in the near term 💪https://gitlab.gnome.org/GNOME/nautilus/-/issues/399Add thumbnailers to the Flatpak2024-01-18T10:01:44ZBastien NoceraAdd thumbnailers to the FlatpakIt would be great if you could add a number of thumbnailers (and their dependencies) to the nautilus Flatpak.
I'd recommend adding:
- evince (PDFs, DjVu, CBR, CBZ)
- gnome-epub-thumbnailer (eBooks)
- gnome-mobi-thumbnailer (eBooks)
- gs...It would be great if you could add a number of thumbnailers (and their dependencies) to the nautilus Flatpak.
I'd recommend adding:
- evince (PDFs, DjVu, CBR, CBZ)
- gnome-epub-thumbnailer (eBooks)
- gnome-mobi-thumbnailer (eBooks)
- gsf-office-thumbnailer (Office documents)
- totem (videos)
This might drag quite a few dependencies, but would make it easier to use.https://gitlab.gnome.org/GNOME/nautilus/-/issues/318Flatpak integration2023-09-03T18:08:12ZCarlos SorianoFlatpak integration# Current problems
<!--
What are the problems that the current project has?
For example:
* User cannot use the keyboard to perform most common actions
or
* User cannot see documents from cloud services
-->
- Users, designers, etc. canno...# Current problems
<!--
What are the problems that the current project has?
For example:
* User cannot use the keyboard to perform most common actions
or
* User cannot see documents from cloud services
-->
- Users, designers, etc. cannot try work in progress easily to provide early feedback.
- Developers doesn't use a single environment to develop.
- Reporters doesn't have a canonical environment to test their issues before reporting.
# Goals & use cases
<!--
What are the use cases that this proposal will cover? What are the end goals?
For example:
* User needs to share a file with their friends.
or
* It should be easy to edit a picture within the app.
-->
- Everyone involved upstream should use same enviroment, like a "safe place", including non developers when they report issues.
- Developers should find easy to test all the functionality of GNOME
- ...
# Relevant art
<!--
Is there any product that has implemented something similar? Put links to other
projects, pictures, links to other code, etc.
-->
Endless OS comes to mind.
# Proposal & plan
<!-- What's the solution and how should be achieved? It can be split in smaller
tasks of minimum change, so they can be delivered across several releases. -->
* [x] Nautilus runs inside Flatpak
* [x] All files except [blacklisted directories](http://docs.flatpak.org/en/latest/sandbox-permissions.html#filesystem-access) in Flatpak can be accessed
* [ ] Plugins work
* [x] Trash works
* [ ] Admin backend works
* [x] Network locations workhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/228Current org.freedesktop.FileManager1 implementation isn't Flatpak friendly an...2023-09-01T14:29:16ZDebarshi Rayrishi.is@lostca.seCurrent org.freedesktop.FileManager1 implementation isn't Flatpak friendly and ignores the default file managerThis has been mentioned a few times before, but I couldn't find a relevant bug for it.
First, here in the original discussion around the <a href="https://www.freedesktop.org/wiki/Specifications/file-manager-interface/">org.freedesktop.F...This has been mentioned a few times before, but I couldn't find a relevant bug for it.
First, here in the original discussion around the <a href="https://www.freedesktop.org/wiki/Specifications/file-manager-interface/">org.freedesktop.FileManager1</a> interface:
http://lists.freedesktop.org/archives/xdg/2011-May/011971.html
Then, during the Nautilus patch review:
https://gitlab.gnome.org/GNOME/nautilus/commit/f01e2e9b5fa6dcd0514bdf5efe5f76b4312f1fd3
Finally, in the context of Firefox using the interface:
https://bugzilla.mozilla.org/show_bug.cgi?id=417952#c17
Now it has come up in GNOME/gnome-photos#7
The problem is that Nautilus ships org.freedesktop.FileManager1.service.
In the traditional non-Flatpak case, this means that no other file manager can ship that file and be installed together with Nautilus because their paths will conflict. Hopefully, nobody tried that because, it also means that if Nautilus is installed then it ignores the user's default file manager setting (inode/directory handler) and hard codes Nautilus, and avoiding that was the whole reason to create the org.freedesktop.FileManager1 standard. In short, it's pointless. :)
With Flatpaks, an application can only export services with bus names prefixed with its application ID. So, org.gnome.Nautilus cannot export org.freedesktop.FileManager1. Therefore, one can't use Nautilus through this interface if Nautilus is Flatpaked.
A better way to implement this (as mentioned in the above URLs) would be to have gnome-settings-daemon front the D-Bus interface, and then forward the calls to whichever application is set as the default file manager (inode/directory handler).