After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 598044 - "Open this file" dialogue identifies everything as "Unknown"
"Open this file" dialogue identifies everything as "Unknown"
Status: RESOLVED DUPLICATE of bug 598167
Product: epiphany
Classification: Core
Component: Backend
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-10 22:40 UTC by Sven Arvidsson
Modified: 2009-10-27 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sven Arvidsson 2009-10-10 22:40:41 UTC
Hi,

I never get the option to "Open" a file about to be downloaded from the dialogue window. All files are identified as "Unknown". 

Directly opening downloaded files by setting "Automatically download and open files" still works fine.

For example the torrent in http://www.mininova.org/tor/3001695

 File Type: “Unknown”.

 You have no application able to open “Stayin Alive in JoBurg [documentary] [mininova].torrent”. You can  download it instead.

From reading bug 576788 it's not clear if this is supposed to work, or still a work in progress?
Comment 1 Germán Poo-Caamaño 2009-10-16 04:00:19 UTC
I can reproduce it with several extensions, such as PDF, ODS, XLS.

For instance:
http://foundation.gnome.org/finance/gnome-foundation-fiscal-year-2007.pdf
http://foundation.gnome.org/finance/GNOME-Donations.ods
Comment 2 Jan de Groot 2009-10-26 11:47:04 UTC
This is a limitation in webkit it seems. The code to detect mime types for this dialogs simply doesn't exist at this moment:
http://git.gnome.org/cgit/epiphany/tree/embed/ephy-embed.c?h=gnome-2-28&id=b93c0ee2b3db46db54b6ae45909fb8b5f54d9f4c#n635
Comment 3 Gustavo Noronha (kov) 2009-10-27 12:20:18 UTC
This is fixed already.

*** This bug has been marked as a duplicate of bug 598167 ***