Thanks, I will try that. Maybe tomorrow, but you might be able to reproduce
this by creating a symlink in user home to a directory in another partition
(ext 4 or ntsf) and secondly going into that dir by clicking the symlink,
and thirdly trying to delete any file there (no subfolder).
On Tue, 1
Public bug reported:
I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.
I've reported this bug (or marked as "it affects me") in a couple of
other places before I've finally discovered that this is the package
that's causing this problem, which unfortunately has been around for a
On Tue, Nov 01, 2016 at 10:48:08AM -, Launchpad Bug Tracker wrote:
> So I was wondering if Ubuntu devs can leave out that particular patch
> when building this package for Ubuntu - if it doesn't cause more harm,
> which I doubt.
The patch is there for a reason - otherwise you can't delete on
