Configuration bug
** Changed in: nautilus (Ubuntu)
Status: Invalid => New
--
Tar lzma nautilus default opening
https://bugs.launchpad.net/bugs/223965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I have the same problem with a fresh install of Ubuntu Hardy AMD64.
The command gvfs-info returned:
display name: file.lzma
edit name: file.lzma
name: file.lzma
type: regular
size: 18
attributes:
standard::name: file.lzma
standard::type: 1
standard::size: 18
standard::display-name: file.lz
could you add an example to the bug?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Incomplete
--
Tar lzma nautilus default opening
https://bugs.launchpad.net/bugs/223965
You received this b
1. Open Nautilus
2. select a file (for example a .pdf)
3. right click and select "Create archive..." (guessed, for I have localized
labels)
4. select tar.lzma or .lzma as archive type and click on Create button
Bug: the result file is smaller, has .lzma as extension, but the icon is not a
box and
trying the steps you describe give an archive icon on jaunty and the
property dialog lists application/x-lzma correctly, the bug has probably
been fixed in a new version
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Fix Released
--
Tar lzma nautilus default opening
https://bugs.l
the bug is a small annoyance and not really worth a stable update since
lzma is not used a lot and only few users complained about the issue
until now
--
Tar lzma nautilus default opening
https://bugs.launchpad.net/bugs/223965
You received this bug notification because you are a member of Ubuntu
** Changed in: nautilus (Ubuntu)
Sourcepackagename: None => nautilus
--
Tar lzma nautilus default opening
https://bugs.launchpad.net/bugs/223965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Please install gvfs-bin (if you don't already have it installed) and run
gvfs-info /path/to/file.tar.lzma
and add what it returns to this bug. The likely case is that you have
incorrect mime information set for LZMA's content type (in e.g.
~/.local/share/mime/globs).
** Changed in: nautilus (Ubu
display name: file.tar.lzma
edit name: file.tar.lzma
name: file.tar.lzma
type: regular
size: 147
attributes:
standard::name: file.tar.lzma
standard::type: 1
standard::size: 147
standard::display-name: file.tar.lzma
standard::edit-name: file.tar.lzma
standard::copy-name: file.tar.lzma
That's pretty much what I figured. This is not a bug, but a
configuration error. Application/x-extension-lzma is not the valid
Content-type for a file with an LZMA extension (should be
application/x-lzma). Check that you don't have an entry in
~/.local/share/mime/globs for LZMA (and either remove i
10 matches
Mail list logo