|
Bugzilla – Full Text Bug Listing |
| Summary: | No application to open gz files | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Forgotten User SpTvqxsYZX <forgotten_SpTvqxsYZX> |
| Component: | Basesystem | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_L9LYSNS5sV, vcizek |
| Version: | Final | Flags: | forgotten_sM9JzehKpy:
needinfo?
(forgotten_L9LYSNS5sV) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User SpTvqxsYZX
2014-02-26 00:21:54 UTC
I experienced this also. Ark has the capability to decompress .gz and KDE has the File Association set to Ark but the above message shows up. Clicking NO takes me directly to Ark. Clicking Yes runs through to failure then takes me to Ark. I am receiving this error in Dolphin! When attempting to open the same .gz compressed binary in Konqueror it reports that the file is a plain text file. I validated my file associations Configure Desktop --> File Associations *.gz is only assigned to Ark and KCheckHash. I do not see any conflicts. Right clicking on the file and selecting --> open with --> Ark, avoids the error as a whole as *.gz is an assigned file association. The name of the file in question "linux-brprinter-installer-1.0.4-1.gz" should not be creating a file extension conflict or be recognized as a plain text file. It looks like a defect in KDE File Associations. I have the KDE-Services package from Fedora-20 hack installed so this does not validated on another system. This is a KDE bug, reassigning to Raymond. So it seems that KSuseinstall does not recognize somehow that gz is a known extension with an association. Will check in the code of ksuseinstall if I can find anything there. If not, then worst case we would have an option to remove the full functionality of ksuseinstall or to turn this bug to a WONTFIX. Let's hope I find something :) Timothy, could you let me know which mimetype that particular archive has ? It seems that ksuseinstall is looking at the mimetype of the file and if that mimetype is being handled or not. Thanks closing bug |