Results 1 to 9 of 9

Thread: Dolphin Drag and Drop

  1. #1

    Default Dolphin Drag and Drop

    In Dolphin Drag and Drop from btrfs/ext4 to fat32 throws an error which references the file with an additional dot at the end. Copy (or Move) however is made, but often followed by a crash of dolphin.
    The fat32 is mounted in fstab with this entry

    Code:
    /dev/disk/by-id/ata-Samsung_SSD_850_EVO_500GB_S2RBNX0H751314Z-part8 /windows/e           vfat       users,gid=users,umask=0002,utf8=true 0  0

    Any ideas welcome.
    LEAP 42.2
    KDE 5.8.6
    Desktop: Nvidia GTX960
    Laptop: Bumblebee

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 9
    Posts
    14,405

    Default Re: Dolphin Drag and Drop

    How big is the file?? Bigger then 4 gig?? Exactly what does the error say??

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    21,927

    Default Re: Dolphin Drag and Drop

    Quote Originally Posted by tobiasw2 View Post
    .... throws an error .......
    People here are not clairvoyant. They need exact and precise information. Specially as you have it before your eyes.
    Henk van Velden

  4. #4

    Default Re: Dolphin Drag and Drop

    Quote Originally Posted by hcvv View Post
    People here are not clairvoyant.
    Sorry, here it is



    a message box pops up and states 'access denied' and refers to the destination where the file should be copied/moved to. When closing the message box the file is indeed copied/moved despite the message and dolphin likely crashes (not always). Independent of file size. Happens also for small files.
    LEAP 42.2
    KDE 5.8.6
    Desktop: Nvidia GTX960
    Laptop: Bumblebee

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    21,927

    Default Re: Dolphin Drag and Drop

    Ok, that is the error message. And that . at the end is of course simply the end of the message, not part of the file name

    Typically something about ownership and permissions. Which is of course on non-Linux file systems extra tricky, because they do not exist there and are mimicked.

    Your fstab entry does state that the group mimicked should be gid=users, but it does not say anything about the user (uid=). Thus the owner is probably root, but that may depend on which user did the mount as allowed by the users option.

    Well, as in every case where some application says it has a permission problem, check what it is:
    Code:
    ls -l /windows/e/_benutzer/test.mp3
    and the path leading to it:
    Code:
    ls -ld /windows /windows/e /windows/e/_benutzer
    And we also want to know what the user is that has this permission problem.
    Henk van Velden

  6. #6

    Default Re: Dolphin Drag and Drop

    The dot is a period. I'm getting old.

    Code:
    tobias@linux-2biv:~> ls -ld /windows /windows/e /windows/e/_benutzer
    drwxrwxr-x  1 root users     4 27. Nov 23:04 /windows
    drwxrwxr-x  4 root users 32768  1. Jan 1970  /windows/e
    drwxrwxr-x 10 root users 32768 25. Dez 01:13 /windows/e/_benutzer
    
    tobias@linux-2biv:~> ls -l /windows/e/_benutzer/test.mp3
    -rwxrwxr-x 1 root users 459754 21. Jun 2016  /windows/e/_benutzer/test.mp3
    
    tobias@linux-2biv:~> mv test.mp3 /windows/e/_benutzer/test.mp3
    mv: Erhalten der Zugriffsrechte für „/windows/e/_benutzer/test.mp3“: Die Operation ist nicht erlaubt
    The user is a normal user from group 'users', so it should work. What am I overlooking?
    LEAP 42.2
    KDE 5.8.6
    Desktop: Nvidia GTX960
    Laptop: Bumblebee

  7. #7

    Default Re: Dolphin Drag and Drop

    your issue is with root priveliges
    I've found that the best way to access windows partitions is with polkit not with fstab
    if it was me I'd remove that line from fstab and create the file /etc/polkit-1/rules.d/10-udisks2.rules
    Code:
    kdesu kate /etc/polkit-1/rules.d/10-udisks2.rules
    and paste this
    Code:
    // See the polkit(8) man page for more information
    // about configuring polkit.
    
    // Allow udisks2 to mount devices without authentication
    // for users in the "users" group.
    polkit.addRule(function(action, subject) {
        if ((action.id == "org.freedesktop.udisks2.filesystem-mount-system" ||
             action.id == "org.freedesktop.udisks2.filesystem-mount") &&
        subject.isInGroup("users")) {
            return polkit.Result.YES;
        }
    });
    the above would grant full priveliges to external file systems to all members of the group users
    if you want to limit filesystem access you can create a new group ie storage and add only a select user to that group

    edit
    this is the way I access windows partitions, partitions are not mounted on boot but on demand and I don't need to mess with root privileges
    on the downside you can't copy a file to windows until you mount it but if you use a gui file manager that is trival as all file managers will auto mount

  8. #8
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    2,720

    Default Re: Dolphin Drag and Drop

    Quote Originally Posted by tobiasw2 View Post
    The dot is a period. I'm getting old.

    Code:
    tobias@linux-2biv:~> ls -ld /windows /windows/e /windows/e/_benutzer
    drwxrwxr-x  1 root users     4 27. Nov 23:04 /windows
    drwxrwxr-x  4 root users 32768  1. Jan 1970  /windows/e
    drwxrwxr-x 10 root users 32768 25. Dez 01:13 /windows/e/_benutzer
    
    tobias@linux-2biv:~> ls -l /windows/e/_benutzer/test.mp3
    -rwxrwxr-x 1 root users 459754 21. Jun 2016  /windows/e/_benutzer/test.mp3
    
    tobias@linux-2biv:~> mv test.mp3 /windows/e/_benutzer/test.mp3
    mv: Erhalten der Zugriffsrechte für „/windows/e/_benutzer/test.mp3“: Die Operation ist nicht erlaubt
    The user is a normal user from group 'users', so it should work. What am I overlooking?

    Your ls output shows the owner as root, so only root is allowed to write those files. You need to improve your mount settings in fstab so the device is mounted (and therefore, owned, which means the files will be pseudo-owned, by the user and not by root). Either that, or your mount must specify the permissions 777 (or rwxrwxrwx) in order for all users to write the files. Note that your permissions for all users is r-x, no write privilege.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~~~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  9. #9

    Default Re: Dolphin Drag and Drop

    Quote Originally Posted by Fraser_Bell View Post
    Your ls output shows the owner as root, so only root is allowed to write those files. You need to improve your mount settings in fstab so the device is mounted (and therefore, owned, which means the files will be pseudo-owned, by the user and not by root). Either that, or your mount must specify the permissions 777 (or rwxrwxrwx) in order for all users to write the files. Note that your permissions for all users is r-x, no write privilege.
    polkit is not a solution since the drive is needed after startup. So umask=0000 yields 777 but the strange behaviour persists. Finally I had to set uid=username in fstab and that works. Only the other users still get this errormessage (while -strange enough- the file gets moved despite the message).

    Thanks to all.
    LEAP 42.2
    KDE 5.8.6
    Desktop: Nvidia GTX960
    Laptop: Bumblebee

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •