Bug 365210 - Unable to browse simple gzip/bzip files as an archive
Summary: Unable to browse simple gzip/bzip files as an archive
Status: CONFIRMED
Alias: None
Product: krusader
Classification: Applications
Component: krarc (show other bugs)
Version: 2.7.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords: reproducible, triaged
: 403545 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-07-07 18:56 UTC by Till Schäfer
Modified: 2019-05-24 06:30 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Till Schäfer 2016-07-07 18:56:20 UTC
Whenever i double click a gzip file  (no gziped tar), i get the error: 

Error: Protocoll not supported by Krusader
gzip:/path/to/file.ext.gz

seems that the option to browse archives as folders introduced by this [1] commit tries to handle gziped files as archives.

From a user perspective, theses gziped files should be handled such as single file archive files.

[1] https://quickgit.kde.org/?p=krusader.git&a=commit&h=d1459aebf7447709feae136848d33e070041118a 

Reproducible: Always




Software used: 

Krusader git: commit d1459aebf7447709feae136848d33e070041118a
kde-frameworks: 5.23
plasma: 5.7.0
qt: 5.6.1
Comment 1 Davide Gianforte 2016-07-08 09:45:07 UTC
The problem is older, also the 2.4.0 version is affected.

On the other hand, krarc:/path/to/file.ext.gz can successfully browse the file.

Katepart can edit and save the gzipped file without the need to decompress it.
Comment 2 Till Schäfer 2016-07-08 14:13:40 UTC
hmm you are right, krarc:/path/to/file.ext.gz works as expected. 

I see two ways to handle this situation:

Solution 1: Even if katepart can transparently view/edit gziped files: handle them as single file archives, because there exist other applications which cannot handle gziped files transparently. Furthermore, the shortcuts to view or edit a gzip file still work directly on the gzip file. It is therefore easy to edit the files directly with katepart (and only katepart / other applications which can handle gzip transparently are cut of).

Solution 2: Alternatively, we must differentiate between the associated applications of the second order extension and mime type, e.g. <filename>.txt.gzip (text/plain; charset=us-ascii compressed-encoding=application/x-gzip; charset=binary) would open directly with kate and <filename>.mp3.gzip (audio/mpeg; charset=binary compressed-encoding=application/x-gzip; charset=binary) would trigger the krarc browsing as my associated player does not handle gzip files transparently. I do not know if there is an easy way to know if an application can handle gzip transparently. It might therefore be troublesome to implement this feature (but still: it would be pretty cool :-) ).
Comment 3 Davide Gianforte 2016-07-10 20:24:09 UTC
A trick could be adding application/gzip to the mimetypes supported by krarc. Though, it doesn't work if the filename contains spaces.
Comment 4 Nikita Melnichenko 2018-07-08 07:04:33 UTC
Confirmed on v2.7.0.

For gzip files the workaround with changing protocol to krarc helps.
For bzip files it doesn't - "Error: The process for the krarc protocol died unexpectedly."
Comment 5 Nikita Melnichenko 2019-05-24 06:30:51 UTC
*** Bug 403545 has been marked as a duplicate of this bug. ***