Version: (using KDE KDE 3.2.3) Installed from: Slackware Packages OS: Linux when i mount from terminal it mount true with all option(like iocharset,umask,uid,.....) as a root and user. --------------------------- and when i mount from gnome icon it mount true with all options as root and user. --------------------------- when i mount from kde icon it mount true with all options as a user. but when i mount from kde icon it mount but without options as a root.
I'm sorry, I cannot understand you. Are you saying that when you mount a filesystem by clicking on its KDE icon, the options that are used are those that a user would see? If so, how is that a bug?
no --------------- my fstab: /dev/hda5 /mnt/abdo vfat defaults,iocharset=utf8,umask=0000 1 0 when i mount by terminal(as root or user) my mtab is: /dev/hda5 /mnt/abdo vfat rw,iocharset=utf8,umask=0000 0 0 (it is true) when i mount by kde icons (as user) my mtab is: /dev/hda5 /mnt/abdo vfat rw,iocharset=utf8,umask=0000 0 0 (it is true) but when i mount by kde icons (as root) my mtab is: /dev/hda5 /mnt/abdo vfat (it is not complete) the bug in kde icons as root only.
Confirmed. I tested with having the following in fstab: /dev/hda2 /mnt/xxx vfat umask=002,shortname=winnt 1 0 After mounting from a .desktop file on the desktop as root, mount shows: /dev/hda2 on /mnt/xxx type vfat (rw) When I do mount /mnt/xxx it in a shell, I get: /dev/hda2 on /mnt/xxx type vfat (rw,umask=002,shortname=winnt)
I think the correct product is kio
Indeed, this is because kio_file tries "mount <dev> <mountpoint>" first (since both are in the .desktop file) before it falls back to "mount <mountpoint>". But as root both work, so the options are discarded. Could be fixed by comparing the requested device with the one in the fstab....
Is this use-case still widely-used? usually Solid with the Udisks backend handles this nowadays.