1934858 - Regression: Firefox does not show file dialogs any more (open, save as, upload...)

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect)

Description

[mywwa-sufo]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

Open Firefox in a container with a mount namespace (to hide/protect sensitive files) and a process namespace (to avoid getting around the mount namespace very easily).

Example programs to active and configure Linux kernel namespaces are firejail or bwrap but many others exist as these are kernel features.

For example, start "firejail --blacklist=/mnt/photos firefox"

Press Ctrl+O, Open File...
OR
Download file, download is started by website/click
OR
Click an upload button to any website, select/choose file

Actual results:

Nothing.
A couple of error messages that might be related:

invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gtk.vfs.UDisks2VolumeMonitor was not provided by any .service files (g-dbus-error-quark, 2)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.MTPVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gtk.vfs.MTPVolumeMonitor was not provided by any .service files (g-dbus-error-quark, 2)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.AfcVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gtk.vfs.AfcVolumeMonitor was not provided by any .service files (g-dbus-error-quark, 2)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gtk.vfs.GPhoto2VolumeMonitor was not provided by any .service files (g-dbus-error-quark, 2)

These error messages are expected to happen, though, as the Firefox runs in a container without access to the non-restricted dbus. None of the mentioned services are needed here. This is about saving/loading a local file.

Expected results:

A file open/save dialogue appears.

===

Extra information: This is a regression, the exact same setup/start method worked for many years (before approx. 132.0.1). Recently the Firefox build on my distro started to require xdg-desktop-portal which may hold the necessary services to open a file dialog in a newly desired fashion and the built-in dialog I used for many years was perhaps removed.

I had a similar problem a few years ago and setting a variable not to use the external file picker was a good workaround. Perhaps that was removed?

I tried that again, though, and found a WORKAROUND:

about:config, set widget.use-xdg-desktop-portal.file-picker to 0

Perhaps the availability of extended services for this dialogue could be automatically detected (on dbus?!), avoiding this issue completely? There are error messages on the console so something could perhaps be detected fairly easily.

For some file uploads/downloads, drag&dropping files will be a workaround but not for all use cases are it only works for some websites.

PS: Disabling the extra container security by allowing the containered Firefox to handle file access by the non-restricted desktop open would not work for me as a solution.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Martin Stránský [:stransky] (ni? me)]

Can you use mozregression to find the broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?

For more information, please visit BugBot documentation.