Hello: I've been tracing the behaviour of the KDE mediamanager to get the removable device mounted. The dbus mounting message is send in svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdebase/kioslave/media/mediamanager/halbackend.cpp line 961, roughly the command send is this
dbus-send --system --type=method_call --dest=org.freedesktop.Hal --print-reply
/org/freedesktop/Hal/devices/volume_uuid_5E438C083A6612CE
org.freedesktop.Hal.Device.Volume.Mount string:'' string:''
array:string:"uid=1000"
where /org/freedesktop/Hal/devices/volume_uuid_5E438C083A6612CE is the
volume uid and the org.freedesktop.Hal.Device.Volume.Mount method input
parameters are:
· mount_point (string): "" in this case
· fstype (string): "" in this case
· extra_options (array string): "uid=1000"
From here what you can see is that KDE mediamanager is not specifying any
filesystem for the mount, and I'm not sure how hal works, but I suspect that
it's hal that has already decided that ntfs is to be used and not ntfs-fuse
or ntfs-3g.
If you could provided some clues as how mediamanager should behave I can
look into the code and see what can be done.
Regards,
--
Raúl Sánchez Siles
----->Proud Debian user<-----
Linux registered user #416098
signature.asc
Description: This is a digitally signed message part.
