https://bugs.kde.org/show_bug.cgi?id=468132
--- Comment #7 from Andrius Štikonas <[email protected]> --- (In reply to nickl from comment #5) Thanks for attaching full table. It does seem like only exfat is affected (this excludes some of the possible failure scenarios but still leaves me a bit puzzled). You don't need setting SESSION variables, you can set them for a single app launch from the command line, e.g. like I was suggesting KPMCORE_DEBUG=y partitionmanager As for setting PATH, there is a fine point. For security reasons partition manager restricts PATH further. All privileged operations are performed by a small helper running as root and as some basic sanity checking we make sure that executables are located in some trusted prefix (see https://invent.kde.org/system/kpmcore/-/blob/master/src/util/externalcommandhelper.cpp#L384) which is specified at compile time and defaults to / and /usr. I.e. partition manager would refuse to run /home/username/bin/sfdisk even if you have PATH=/home/username/bin/ (or even something like /usr/../home/username/bin/sfdisk wouldn't work). Anyway, it looks like your exfatprogs are in /usr/sbin, so you should be fine. I think at this point it would be useful to see if there are any error messages in the terminal when you run KPMCORE_DEBUG=y partitionmanager -- You are receiving this mail because: You are watching all bug changes.
