Bug 229036 - Add .txz archive support
Summary: Add .txz archive support
Status: RESOLVED DUPLICATE of bug 218929
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
: 229667 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-01 16:19 UTC by Thorsten Mühlfelder
Modified: 2010-03-06 19:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Mühlfelder 2010-03-01 16:19:26 UTC 
Version:           2.14 (using KDE 4.4.0)
OS:                Linux
Installed from:    Slackware Packages

Slackware has introduced the .txz package format long ago. This basically is a xz compressed tar archive. Infos about xz: http://tukaani.org/xz/

As KDE is the default desktop in Slackware, xz support in ark would be nice. I'm waiting for this really long now :-D
Comment 1 Raphael Kubo da Costa 2010-03-01 21:54:45 UTC 
Are you sure you're using KDE SC 4.4.0? As I see the official Slackware packages are still for 4.3.4.

Support for tar.xz files was implemented a few months ago.

*** This bug has been marked as a duplicate of bug 218929 ***
Comment 2 Thorsten Mühlfelder 2010-03-01 23:52:06 UTC 
I've used 4.3.4 for some time and I've switched to AlienBob's KDE 4.4.0 packages recently.

I'm getting this error message:
Reading the archive '/home/slkbuilds/x86_64/a/lilo/lilo-22.8-x86_64-9tm.txz' failed with the error 'The archive reading failed with message: Unrecognized archive format: Invalid or incomplete multibyte or wide character'
Comment 3 Raphael Kubo da Costa 2010-03-02 02:52:57 UTC 
Hmm, this is weird. If Ark is already being called to open the txz file, at least the mimetype has been registered correctly.

Does this problem happen only to this specific file? If so, can you attach it or provide a link to some package that presents this behaviour to you? Last but not least, can you try upgrading your libarchive package to a newer version and see if it works?
Comment 4 Thorsten Mühlfelder 2010-03-02 03:41:58 UTC 
Sometimes solution is so simple. Updating libarchive from 2.6.2 to 2.8.0 did the trick. Thanks for the tip ;)
Comment 5 Raphael Kubo da Costa 2010-03-06 19:05:49 UTC 
*** Bug 229667 has been marked as a duplicate of this bug. ***