[linux] Cannot use AppImage binary as a helper application
Categories
(Core :: Widget: Gtk, defect, P5)
Tracking
()
People
(Reporter: mozilla.org, Unassigned)
References
Details
Attachments
(1 file)
|
33.09 KB,
image/png
|
Details |
Screenshot from 2020-03-19 12-51-48.png
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I downloaded the PrusaSlicer application as an AppImage file from https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.2.0-rc4
I made the file executable, as instructed. I now want Firefox to automatically open PrusaSlicer whenever I download an STL file. This works fine on my Mac.
When I download he STL file (e.g. any file from thingiverse.com), I'm prompted to specify a helper application. No matter what I do, I cannot specify PrusaSlicer as a helper. Firefox just gets confused.
Actual results:
The first problem is that the "Choose Helper Application" dialog box makes it very difficult to choose any application that isn't a GUI application installed by Ubuntu. There is no way to browse /usr/bin or any other directory.
If I press the search button, or type /, I get an entry field where I can manually type in the full path of the binary. However, when I specify /home/ttabi/PrusaSlicer-2.2.0-rc4+linux-x64-202003151142.AppImage, Firefox gets confused. See attached screenshot.
Expected results:
Firefox should do two things:
-
Allow me to browse any directory to choose any binary
-
Understand what an .AppImage binary is and correctly associate it with the given MIME type.
This is similar to Bug 1153089.
|
||
Comment 2•6 years ago
|
||
I can confirm that this issue is reproducible on ubuntu 18.04 x64 when using the latest Firefox 74, Firefox 75 beta 9, Firefox 68.6.0 esr and the latest Nightly 76.0a1.
|
||
Comment 3•6 years ago
|
||
This is the standard gtk dialog for this purpose, apparently, ie the result of calling gtk_app_chooser_dialog_new_for_content_type.
|
|
||
Comment 4•6 years ago
|
||
You could try working around by picking a different app and then editing your local handlers.json in your profile directory to specify the full path to the executable you want.
|
||
Comment 5•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 6•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 7•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 8•6 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal to S3.
Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.
The work-around in comment 4 worked, but it's absurd that I need to do this. Why can't I just manually add new MIME types and helper applications via the Preferences panel?
|
||
Comment 10•3 years ago
|
||
Based on comment 3, I'm marking this INVALID, and this needs to be fixed in GTK.
|
Reporter | |
Comment 11•3 years ago
|
||
Or, Firefox could just a non-broken method for selecting a helper app.
|
|
||
Comment 12•3 years ago
|
||
(In reply to TT from comment #11)
Or, Firefox could just a non-broken method for selecting a helper app.
There isn't really one, unfortunately. Rolling our own dialog is not really workable - it'd lack tab-complete, theme/window-manager-compatible styling for all the files displayed, etc. etc.
This is the kind of thing that the OS / window manager is meant to provide, and if your OS / window manager provides a useless dialog, I honestly think that's something you should take up with them rather than complaining to Firefox.
If we're actually using the wrong gtk API, I'm sure that's something we could look at - but I'm not aware of a better API to use. See also previous discussion in bug 1299017, which points to this redhat bug where the suggestion is that this is the right API, and that not being able to browse from the dialog is Just How It Is in GTK3-land...
Description
•