https://bugs.kde.org/show_bug.cgi?id=479262
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
Those paths don't exactly look healthy, there's a need for quite a bit more
context here:
- What's the full path of the file you attempted to trash?
- What's the mount point that file resides on?
- Is your $HOME on a different mount point?
If I interpret the problem well, then those extra zero bytes will lead to the
path being just "/" which of course really shouldn't be used for trash
purposes, but where are the garbage bytes coming from? Is
KMountPoint::currentMountPoints getting an unexpected null byte somewhere and
is Qt turning that into 2 bytes of zero due to using the horrible UTF-16 mess?
Alternatively it could come from Solid::Device::listFromQuery, but that's in
case of scanning for trash directories, and without more info I'll assume that
the error was encountered when attempting to use the trash.
--
You are receiving this mail because:
You are watching all bug changes.
