null error when trying to open a file not correctly named
Bug #292835 reported by
Carlos Horacio Ruiz
This bug report is a duplicate of:
Bug #26662: using the filename to get the mimetype is not always correct.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
File Roller |
New
|
Unknown
|
|||
file-roller (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Hi,
In trying to decompress a few items that you download for beryl, the manager of filing cabinets, a window appears stating that a mistake has happened Null.
I have ubuntu 8.10
Thanks
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: file-roller 2.24.1-0ubuntu2
ProcEnviron:
PATH=/
LANG=es_CO.UTF-8
SHELL=/bin/bash
SourcePackage: file-roller
Uname: Linux 2.6.27-7-generic i686
Changed in fileroller: | |
status: | Unknown → New |
To post a comment you must log in.
assigning to file-roller
i confirm this behaviour. the contained file, named "Blue", is in fact a gzipped tarbal. if renamed to Blue.tgz, it opens fine, so it seems the lack of an extension makes the difference...
i am assigning the Blue file outside the .tar.7z