Bug 478590

+1 for this; It seems like compressing files is now disabled period since KDE 6 whereas before you could do it if the share was mounted via fstab, so technically I'd call it a regression.

(In reply to spamless.9v5xj from comment #1)
> +1 for this; It seems like compressing files is now disabled period since
> KDE 6 whereas before you could do it if the share was mounted via fstab, so
> technically I'd call it a regression.

Before it was a bug.
You might not ever used it, for small files that would be fine for anything else that would be very slow.

I will quote myself:

```
A smb share is a network share, meaning all data reading and writing must go through the network and is slow compared to a local folder.

In order to compress files, we need to read them them all and then write a new file of a potentially similar size.

If we were to allow compressing from a smb share, you would be copying locally the file(s) to compress, compress them and uploading the new compressed file to the server, which would be very noticeably slow and potentially not expected behavior.

If that’s what you want, you can do it manually.
```

I think "noticeably slow" is an overgeneralization - for me it's definitely faster to do it on my local PC despite network overhead because the bottleneck of trying to compress on a Celeron processor far outweighs it.

This is a  blanket change based on a flawed assumption. The decision should be left up to the user with a pop up warning and confirming to continue anyway instead of outright forbidding the action.

I would like to add a similar use case - I would like to be able to compress from a network share to a local destination (as opposed to a destination on the network share).