Bug 838896 - mime record for .ar archive is incorrect
mime record for .ar archive is incorrect
Status: NEW
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: shared-mime-info (Show other bugs)
x86_64 Linux
medium Severity low
: rc
: ---
Assigned To: Bastien Nocera
Desktop QE
Depends On: 838849
  Show dependency treegraph
Reported: 2012-07-10 07:49 EDT by Martin Simon
Modified: 2017-09-14 07:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 838849
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Simon 2012-07-10 07:49:59 EDT
+++ This bug was initially created as a clone of Bug #838849 +++

Description of problem:
E.g. file-roller is able to create the .ar archive, but is unable to open it by default - file-roller is not set as the default app for *.ar file. If I want to open an archive using file roller, I can choose which types of files are shown, but if I choose "All archives", there is none of the *.ar files visible. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create an .ar archive (e.g. using file-roller)
2. double click on it
Actual results:
"There is no application installed for AR archive files." error appeared

Expected results:
Opened archive by file-roller

Additional info:
Comment 1 RHEL Product and Program Management 2012-09-07 01:22:39 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

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