.tar.lzma not associated with file-roller

Bug #220320 reported by Jonáš Svatoš
22
Affects Status Importance Assigned to Milestone
shared-mime-info
Fix Released
Medium
shared-mime-info (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Nominated for Hardy by Michael Terry

Bug Description

File roller now has an option to create lzma archives with .tar.lzma extension, however, the resulting file is not associated for opening with file-roller.
It can be opened by manualy selecting file-roller, though.

Bug was observed on Hardy post-RC
file-roller 2.22.2-0ubuntu1

Revision history for this message
In , Frédéric Crozat (fcrozat) wrote :

Created an attachment (id=12569)
add .lzma support

Revision history for this message
In , Bastien Nocera (hadess-deactivatedaccount) wrote :

It's missing the acronym bits.

Revision history for this message
In , Frédéric Crozat (fcrozat) wrote :

Created an attachment (id=12570)
new version, with acronym

Revision history for this message
In , Michael Monreal (mimox) wrote :

This patch would be very helpful to have upstream, as file-roller now supports lzma compressed files, but they are not usable from nautilus because they are detected as application/octet-stream

Revision history for this message
In , Bastien Nocera (hadess-deactivatedaccount) wrote :

2008-01-07 Bastien Nocera <email address hidden>

        * freedesktop.org.xml.in: Patch from Frederic Crozat
        <email address hidden> to add LZMA archives (Closes: #13256)

Revision history for this message
Jonáš Svatoš (lsde) wrote :

File roller now has an option to create lzma archives with .tar.lzma extension, however, the resulting file is not associated for opening with file-roller.
It can be opened by manualy selecting file-roller, though.

Bug was observed on Hardy post-RC
file-roller 2.22.2-0ubuntu1

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

I can confirm this with version 2.22.2-0ubuntu1 on Hardy.

debian/file-roller.mime contains these lines, so it's atleast trying to register the MIME type:

application/x-lzma; /usr/bin/file-roller '%s'; test=test -n "$DISPLAY" -a -e /usr/bin/lzma ; priority=5
application/x-lzma-compressed-tar; /usr/bin/file-roller '%s'; test=test -n "$DISPLAY" -a -e /usr/bin/lzma ; priority=5

Changed in file-roller:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Andrés Rassol (anra) wrote :

I also confirm this bug.

Revision history for this message
Alec Faithfull (alec-faithfull) wrote :

The problem seems to be that the MIME types application/x-lzma and application/x-lzma-compressed-tar aren't actually in the shared MIME database; copying the attached file into /usr/local/share/mime/packages and running "sudo update-mime-database /usr/local/share/mime" adds them, so the archives can at least be opened. (The upstream freedesktop.org package has included these MIME types since version 0.30, but the package in Hardy is only on version 0.23.)

Other integration details don't work properly (the files don't have an archive icon or an "Extract here..." context menu item in Nautilus), but that's probably a separate bug...

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in intrepid now

Changed in file-roller:
assignee: nobody → desktop-bugs
status: Confirmed → Fix Released
Changed in shared-mime-info:
status: Unknown → Fix Released
Revision history for this message
Michael Terry (mterry) wrote :

I'm attaching an SRU minimal debdiff against hardy. This is a safe patch, applied upstream.

This bug is annoying for users because they can right click a file/folder in Nautilus, create an archive of it, and not be able to open the archive because the system doesn't know the mime type of the just-created file!

As noted above, this has been fixed upstream since 0.30 and is fixed in Intrepid by virtue of using newer versions.

Changed in dennis:
importance: Undecided → Low
status: New → Confirmed
Michael Terry (mterry)
Changed in dennis:
assignee: nobody → mterry
Revision history for this message
Martin Pitt (pitti) wrote :

This doesn't fall under the SRU criteria (https://wiki.ubuntu.com/StableReleaseUpdates). Is this a regression from a previous release?

Revision history for this message
Michael Terry (mterry) wrote :

No, not a regression, I believe. And the effect to the user is not critical (no data loss or anything).

The criteria I considered this bug hitting was "Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel)." Which is a pretty wide category of fixes.

But upon reflection, shared-mime-info is likely such a 'critical infrastructure package.'

Changed in shared-mime-info:
importance: Unknown → Medium
Changed in shared-mime-info:
importance: Medium → Unknown
Changed in shared-mime-info:
importance: Unknown → Medium
Michael Terry (mterry)
Changed in dennis:
assignee: Michael Terry (mterry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.