Public bug reported:
Upgrading from 14.04.5 to 16.04.4.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture:
Public bug reported:
If you use shares-admin to share a folder via NFS (Shared Folders:
Shared Folders: Add) and you pick out a path that includes embedded
spaces, the string is included verbatim (that is, without escaping the
spaces) in the configuration (/etc/exports in particular), and thus the
It's really a sad state of affairs that this bug reveals. The Linux
community seems to be disintegrating, each clan blaming the others for
whatever. Ubuntu looked like a viable alternative to the big guys, but
with flat-out failures like this one, it's beginning to look doomed.
Forget clannishne
Public bug reported:
Binary package hint: nautilus
(Possibly a Samba bug rather than a Nautilus one)
When copying a file from a window opened on a remote share (using Samba)
and then pasting into some other (local) location, if the file already
exists the usual Cancel/Skip/Replace dialog pops up
Public bug reported:
Binary package hint: nautilus
Ubuntu 10.10
Using Nautilus, one can select multiple files (or folders) and obtain
their combined Properties. On the Permissions tab of the Properties
window, there is an "Execute" checkbox, which one can check (or
uncheck). So I selected seve
I was sure I had seen someone explaining the problem as arising from
xarchiver, but I seem to have been mistaken. I now understand (I'm new
to this bugs.launchpad) that this bug had been assigned to multiple
applications (file-roller and xarchiver). In that sense, xarchiver is
possibly blameless
Definitely not "invalid", inasmuch as the original (Unicode-named) files
are NOT recreated by xarchiver.
** Changed in: xarchiver (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller
Charlie is mincing words to get around the problem of facing the issue.
The bug is valid, because xarchiver is NOT unzipping the contents of the
archive: it is copying its contents to seemingly randomly-named other
files. The original zipped files are NOT recovered: you get other-named
files with
I can confirm the problem in a French environment : the accented
characters are not dealt with correctly by file-roller (they become
question marks). I'm aware that the problem lies with the zip format
itself; invoking unzip directly from the command line does extract the
"badly named" files, albe
