BUGG in KDE Partition Manager

[steve7233]

I right click on a partition and select edit mount point. I Click the select button to browse to the folder. I get:

Unable to create io-slave. Can not create socket for launching io-slave for protocol 'file'.

This the bug is repeatable. I just got a replacement drive from WD after my new 4TB My Book drive failed and am trying to make a mount point for my new BTRFS partition exfat cannot be read so I replaced it with BRTFS which is probably better.

[claydoh]

Have you recently had any system updates, and have you logged off or rebooted since then?
This is just one reason an error like this can happen, so logging off or rebooting might be worth trying, if you have not done so already.

[steve7233]

I get that the KDE Partition Manager folks think the program is bug-free but this is a pretty specific error message. My system being borked is unlikely since I had to reinstall it about a week ago. Firefox lets me choose files just fine so why can't KDE partition manager?

[steve7233]

I already rebooted to try to read the partition. When that didn't work I realized it was probably a MAC file system so I ran KDE partition manager. Sure enough, it was an exfat FS requiring exfat-tools which I didn't bother installing rather I deleted extfat and created BTRFS.

[steve7233]

I just tried rebooting again just so you would suggest something else to check. No change I still get the exact same error message in the exact same place.

[Qqmike]

And comparison to using GParted for this same work?

[steve7233]

And comparison to using GParted for this same work?

Hang on. Checking.

Edit: gparted doesn't use a file browser so you can't do the same work. It doesn't even give you the option to edit the mount point as KDE partition manager does.

[claydoh]

unfortunately, it is a known bug, fixed in the next version that does not run the GUI part as root explicitly, using a different method. 'Blame' the need to support Wayland
There are many reports on this already, and the fix is in version 4.0.0, likely available in Kubuntu 19.10, so it *might* get backported to 19.04. Eoan is still at 3.3 currently.
It is already in Kde Neon.

https://www.reddit.com/r/kde/comment...nager_can_not/
(stikonas is the developer of the program)
https://bugzilla.redhat.com/show_bug.cgi?id=1639020
https://bugs.kde.org/show_bug.cgi?id=376189
https://bugs.kde.org/show_bug.cgi?id=401149
and more. Note this is across distros, and was fixed only fixed fairly recently. At least someone was interested in taking the project on.

[steve7233]

unfortunately, it is a known bug, fixed in the next version that does not run the GUI part as root explicitly, using a different method. 'Blame' the need to support Wayland
There are many reports on this already, and the fix is in version 4.0.0, likely available in Kubuntu 19.10, so it *might* get backported to 19.04. Eoan is still at 3.3 currently.
It is already in Kde Neon.

https://www.reddit.com/r/kde/comment...nager_can_not/
(stikonas is the developer of the program)
https://bugzilla.redhat.com/show_bug.cgi?id=1639020
https://bugs.kde.org/show_bug.cgi?id=376189
https://bugs.kde.org/show_bug.cgi?id=401149
and more. Note this is across distros, and was fixed only fixed fairly recently. At least someone was interested in taking the project on.

I was starting to wonder if it might be some sort of permission foul up. Wayland hu? That will annoy the Wayland fanboys. Since there is a fix in KDE neon then I suspect it will work for this flavor of Ubuntu.

[claydoh]

I was starting to wonder if it might be some sort of permission foul up. Wayland hu? That will annoy the Wayland fanboys. Since there is a fix in KDE neon then I suspect it will work for this flavor of Ubuntu.

Ya it works in other distros with the new version

Wayland users could not use it before as the old version needs to be run as root. Wayland does not run run as root, so partitionmanager can't run under it.

Sent from my LG-H931 using Tapatalk

[jlittle]

That will annoy the Wayland fanboys.

No, they'll smugly say it's a feature, by design, not a failing, because

Wayland does not run as root.

[steve7233]

I got working by opening a konsle and running

sudo partitionmanager

. Apparently, that gets around the problem with Wayland.

Edit: getting smart status for 2 of my drives failed. One is a WD MYBOOK module WDBBGB0040HBK-NESN The other one is WDC WD75 00AACS-00ZJB. It would probably be a great idea for Ubuntu to be able to read the smart status of those 2 drives. Both external USB 3.

[claydoh]

I got working by opening a konsle and running

sudo partitionmanager

. Apparently, that gets around the problem with Wayland.

Edit: getting smart status for 2 of my drives failed. One is a WD MYBOOK module WDBBGB0040HBK-NESN The other one is WDC WD75 00AACS-00ZJB. It would probably be a great idea for Ubuntu to be able to read the smart status of those 2 drives. Both external USB 3.

That is also a similar issue to your other one, and should be fixed in the 4.0.0 release.
There are other tools that can be used for this non-Ubuntu problem.

[oshunluvr]

KDEneon 18.04 daily already has partitionmanager 4.0.0

[oshunluvr]

However, it does not read the SMART of any of my disks. I wonder if there's a setting...