Bug 1001988 - "Archive Mounter" entry is missing from nautilus context menu on archives
Summary: "Archive Mounter" entry is missing from nautilus context menu on archives
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-28 09:20 UTC by Fabian Deutsch
Modified: 2015-02-17 16:57 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 16:57:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2013-08-28 09:20:56 UTC
Description of problem:
Some time in the past it was possible to mount archives in nautilus - like we can still mount ISOs.

Version-Release number of selected component (if applicable):
$ rpm -q nautilus
nautilus-3.8.2-1.fc19.x86_64


How reproducible:
always

Steps to Reproduce:
1. Right-click on an .zip file
2. 
3.

Actual results:
Open with Archivemanager is the only option

Expected results:
"Open with Archivemanager" and "Open with Archive mounter" are shown

Additional info:

Comment 1 Fabian Deutsch 2013-08-28 09:39:20 UTC
It seem sthat our patch isn't working anymore. Or at least not working currently.

http://pkgs.fedoraproject.org/cgit/gvfs.git/tree/gvfs-archive-integration.patch

Comment 2 Ondrej Holy 2013-09-10 15:55:23 UTC
NoDisplay=true in the desktop file blocks showing it in the context menu recently, however this isn't probably wanted behavioral according the Desktop Entry Spec http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html:

NoDisplay means "this application exists, but don't display it in the menus". This can be useful to e.g. associate this application with MIME types, so that it gets launched from a file manager (or other apps), without having a menu entry for it (there are tons of good reasons for this, including e.g. the netscape -remote, or kfmclient openURL kind of stuff). 

It is caused by the commit 7770b63d6726bc7ab4b886d6bd3edd009e622e55 (see https://bugzilla.gnome.org/show_bug.cgi?id=696372). However we can't remove NoDisplay=true from the desktop file...

So changing component back to Nautilus.

Comment 3 Fedora End Of Life 2015-01-09 19:37:25 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 16:57:19 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.