i've been struggling with an error message that pops-up whenever i double click my usb external drive auto-mount icon in kde (konqueror). At first everything was working normally, but after i made a group change (i just added my user to disk group, to be able to manipulate physical disks in vmware-server), this started to happen. I'm not logging in as root, but a normal user, and I also have a static internal partition (not removable) with ntfs filesystem which can not be accessed as well, with the same error message.
The error message reads:
Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
I don't know where this Unknown protocol error messages come from, or if there is some kind of log in kde so that i can see which specific process went wrong to start tracing the problem.
I don't know if this helps understand the problem, but a while ago, when i was first trying to use ntfs-3g instead of the standard ntfs kernel module, i came across this:
so, i followed the instructions there to use ntfs-3g by adding an entry to the hal policy, but then i read the part where it says:
As of hal => 0.5.10 the above policy may not work, so i checked slack 12 hal version and it was 0.5.10, so i removed the entry and tried the second approach, which was creating the symlink:
# ln -s /sbin/mount.ntfs-3g /sbin/mount.ntfs
where mount.ntfs-3g is a bash script that actually calls the command ntfs-3g with the right locale, and it worked!!
About two days after this, while dealing with vmware, i started having an error message every time i tried to mount my ntfs devices which read something like
ntfs-3g must have exactly one device and one mount point.
After i started having this problem, i found the Slack 12 HAL sticky post and read that the entry in the policy should be used, so i did that, and removed the symlink previously created.
and this is when i started having the could not start process message.
Does anyone have an idea of what is going on?
I can normally mount from a console my partitions in root mode, with the ntfs-3g command.
Thanks in advance.
Problem solved, removed ntfs devices from fstab, removed /sbin/mount.ntfs-3g bash script and restored /sbin/mount.ntfs-3g symlink pointing to /bin/ntfs-3g, only added the hal policy entry mentioned in slack12 hal sticky post, and voila! my fault.