Bug 444549

Summary: F9 - KDE arK cannot read 7z archives
Product: [Fedora] Fedora Reporter: Gerald Cox <gbcox>
Component: kdeutilsAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: kevin, ltinkl, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-29 10:37:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gerald Cox 2008-04-29 01:30:28 UTC
Description of problem:
Cannot open 7z archives.  arK is the KDE supplied graphical front end to read
archive files, File Roller is used for GNOME. 
 
Installed kio_p7zip-0.3.1-7.fc9.x86_64 
p7zip-plugins-4.51-4.fc0.x86_64
p7zip-4.51-4.fc0.x86_64

After application, was able to open 7z archives with FileRoller, but unable to
open with arK.

Version-Release number of selected component (if applicable):
kdeutils-4.0.3-4.fc9.x86_64
kio_p7zip-0.3.1-7.fc9.x86_64 
p7zip-plugins-4.51-4.fc0.x86_64
p7zip-4.51-4.fc0.x86_64

How reproducible:
Try to open 7z archive with arK

Steps to Reproduce:
1.  Launch arK application
2.  Select open, 7z does not appear as supported filetype
3.
  
Actual results:
7z does not appear as supported filetype
archive does not open


Expected results:
7z appears as supported filetype
archive can be opened


Additional info:
After installation of the 7z rpms listed above, archives are now supported using
fileroller, but should be able to open using arK

Comment 1 Kevin Kofler 2008-04-29 01:38:41 UTC
7z support was simply never ported to the new plugin-based version of Ark in 
KDE 4. :-(

Comment 2 Lukáš Tinkl 2008-04-29 10:37:58 UTC
As Kevin noted, you should probably file a wishlist upstream, there's nothing 
we can do about this as the feature is simply not implemented