Dolphin: How to move without preserving attributes?

So as the name suggest, I’m struggling to move (“Cut”) folders using Dolphin. It always shows the following error:

Could not rename file /path/to/file

These are the permissions for source & destination:

mpw@fedora:~/Videos/Movies_OUT$ ls -hal ~/Videos/Movies_OUT
total 5.3G
drwxr-xr-x. 2 mpw mpw 4.0K Oct 17 15:36 .
drwxr-xr-x. 7 mpw mpw 4.0K Oct 17 14:02 ..
-rw-r--r--. 1 mpw mpw 2.7G Oct 17 15:02 Cobra.1986.1080p.BluRay.x264.YIFY.mp4
-rw-r--r--. 1 mpw mpw 2.6G Oct 17 15:30 Tango.and.Cash.1989.1080p.BrRip.x264.YIFY.mp4
mpw@fedora:~/Videos/Movies_OUT$ ls -hal /run/media/mpw/5DC9F6A255767E73/
total 5.3G
drwxrwxrwx  1 mpw  mpw  8.0K Oct 17 15:51 .
drwxr-x---+ 3 root root   60 Oct 17 15:36 ..
-rwxrwxrwx  1 mpw  mpw  2.7G Oct 17 15:02 Cobra.1986.1080p.BluRay.x264.YIFY.mp4
-rwxrwxrwx  1 mpw  mpw  2.6G Oct 17 15:30 Tango.and.Cash.1989.1080p.BrRip.x264.YIFY.mp4
drwxrwxrwx  1 mpw  mpw     0 Oct 17 14:31 .Trash-1000

This is what I’m looking for (An option to ignore attributes and just move the folders/data) using Midnight Commander as an example:

Is this possible in Dolphin and follow-up: Where to find it? :slight_smile:

Thank you!

You tried to move to another directory? /run/media is a root directory.

You can try too to move with sudo mv ~/Videos/Movies_OUT/*.mp4 /run/media/mpw/5DC9F6A255767E73/ .

Regards

2 Likes

Yeah, sorry I had more screenshots but because I’m new it didn’t let me post more than 1, so then I tried to copy/paste and left out info :frowning:

I’m on Fedora and it auto-mounts USB sticks to /run/media/myname/ID

I’m trying to move all of the files from ~/Videos/Movies_OUT which is ext4 to the mounted USB (Which is NTFS I think, can’t remember.. “Microsoft Basic Data”).

I think the issue is it can’t preserve the attributes and file permissions from ext4 to ntfs, which is fine (I don’t want to preserve them).

Even when I use Dolphin’s “Open As Administrator” and try to move in Dolphin as admin it doesn’t work.

However, using Midnight Commander (The 1 screenshot I posted) I can move them as my normal user by unchecking the “Preserve attributes” option.

Do you think it’s maybe because of the way my /etc/fstab is setup? I unfortunately can’t make all my USB sticks ext4 ‘cause I still have 1 remaining PC running Windows in the house.

NTFS may have problems (is a problematic FS).

If you don’t need NTFS, my tip is: move all data from the USB to disk, format to ext4 (or what you need) and copy the files again to USB + the Movies_OUT videos. :wink:

Regards

Move will preserve the attributes

but Copy will will not.

so you could copy, then delete.

1 Like

This is technically correct based on my testing. I can copy the files from ~/Videos/Movies_OUT to /run/media/mpw/ID

Then I can delete the files in ~/Videos/Movies_OUT…

However with the same account and with the same file manager, I cannot move the files.

I have installed Thunar and can confirm that my workflow works with Thunars; after my bash script finishes and I have a folder (~/Videos/Movies_OUT) filled with movies, I can simply go into that folder and use Ctrl+A to select everything, use Ctrl+X to Cut them and then I click on the USB drive (NTFS filesystem) in Thunar’s left-hand menu (Just as I do in Dolphin):

How can I make Dolphin behave like Thunar and Midnight Commander (I like Dolphin but it seems to hate me)

This is not possible currently in dolphin, moving copies attributes.

This would be weird to have an option for this, it needs to be passed before-hand.

The Copy & delete should be the way to go in dolphin.

Can you be more specific.

Is /run/media/mpw/5DC9F6A255767E73/ a fuse mount or using kio-fuse ?

You might have hit this bug. It does not limit to affect smb.

What is your versions/distro? (kinfo command, the first four lines)

You can update to the latest version of KDE Frameworks (6.19.1), restart dolphin and the issue should be solved then. That is if your distro already provides 6.19.1.

If that’s not it, can you share the mount command output, the line concerning this path /run/media/mpw/5DC9F6A255767E73/in particular.

Couldn’t your script move the files. One manual step less, just need to pass the path to the usb or detect the usb path, you can make this parameter optional…

1 Like

(I don’t know how to answer your first question yet, I don’t know how these USB drives are being mounted yet hehe)

(Info)

Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.16.12-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

My script is really primitive, I only wrote it to learn bash lol. The challenge for me is that every distribution of linux seems to identify these usb sticks in a way I don’t understand. Sometimes the exact same USB stick that I plug into the same port is /dev/sdd1, sometimes it is /dev/sdc1. I know there’s a rational pattern but I don’t understand it.

Additionally, some linux distributions will mount the same stick (whether it be called /dev/sdc1 or /dev/sdd1) to seemingly random locations (Random to me ‘cause again I’m ignorant lol). Sometimes in a /mnt folder, sometimes under /media and sometimes under /run

So I dont’ even try to think about that in my primitive script lol it just accepts an input folder path as the 1st argument and an output folder path as the 2nd argument. Then it walks the folder structure in the 1st param and collects media files with the find utility; writes those paths to a temp file and then iterates through that list of paths to:
a) check if the path exists in .reencode_done.log (skips if it’s found)
b) probe it with ffprobe to test it for direct-play in a browser
c) re-encode with ffmpeg into a direct-play ready format with fast-play enabled
c.1) if ffmpeg throws an error it appends the file path to .reencode_error.log and continues
c.2) if ffmpeg exits positively it appends the file path to .reencode_done.log

It’s full of bugs I can’t figure out (I’m still learning lmao) and so I am afraid of adding more complexity to it :frowning:

I think Fedora 42 is using systemd & udev and maybe this “udisks2” is reacting to udev events when I plug in the usb sticks?

I’m over my head and have no way to orientate myself to be honest

If I understand correctly the destination is just an exfat partition mounted by udisks.

There is none because there can be none, stable name for that.

I meant to use other ways like using lsusb or udev.

For instance udevadm info --query=property -n /dev/sdb | grep ID_BUSwill tell you if `/dev/sdb`is on usb bus, i.e plug-in through USB.

That’s the more important issue to me. That I would like you to help me figure out.

But since you use KDE Frameworks 6.12, this might have been fixed in the last 6 months, at least if that was a common issue I think I would know.

With Fedora 43 very close now, chances upgrading will solve the issue. But please report a bug if it doesn’t.

Yes, all distros use udev at least that’s implemented by the Linux kernel. systemd and udisks are on top.

1 Like

Absolutely, it’d be my pleasure!

Back from upgrading and I have good news and bad news.

The bad.. Even though I’m on the beta channel I could only get KDE Framework up to 6.18 :frowning:

Operating System: Fedora Linux 43
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.17.1-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1060 6GB

Dolphin: 25.08.1

The good news is the bug seems to be gone! :partying_face:

I did a test with this USB stick:

Sam128 (B) (Dolphin works fine with this)

sudo fdisk /dev/sdc1 -l
Disk /dev/sdc1: 119.51 GiB, 128320719872 bytes, 250626406 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf4f4f4f4

Device      Boot      Start        End    Sectors  Size Id Type
/dev/sdc1p1      4109694196 8219388391 4109694196  1.9T f4 SpeedStor
/dev/sdc1p2      4109694196 8219388391 4109694196  1.9T f4 SpeedStor
/dev/sdc1p3      4109694196 8219388391 4109694196  1.9T f4 SpeedStor
/dev/sdc1p4      4109694196 8219388391 4109694196  1.9T f4 SpeedStor


sudo blkid /dev/sdc1
/dev/sdc1: LABEL="Sam128 (B)" UUID="64A5-F009" BLOCK_SIZE="512" TYPE="exfat"

This one that was giving me the most trouble seems to work as well, too! :slight_smile:

Microsoft basic data (Troublesome)

sudo fdisk /dev/sdc1 -l
Disk /dev/sdc1: 119.51 GiB, 128319488000 bytes, 250624000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

sudo blkid /dev/sdc1
/dev/sdc1: BLOCK_SIZE="512" UUID="5DC9F6A255767E73" TYPE="ntfs" PARTLABEL="Microsoft basic data" PARTUUID="48956fc4-85a5-4f9c-b725-bc1f106793ae"

P.S: Totally random tangent, but do you know why fdisk -l output all that stuff about “/dev/sdc1p1-4” ? Almost looks like another partition table or something.

1 Like

Thank you for the feedback, great to here the issue is resolved.

No that’s the actual original point of access that Linux exposes to your hard-drives. (and generally all that is in /dev for devices, be they virtual (tty) or actual hardware, mouse gpu… ).
One that is funny for instance is /dev/random that provides a generate of random numbers.

Mountpoints are gateways to those block devices as Linux kernel defines them. And then filesystem transform raw bytes to accessible files and folders. That’s a simplification.

Those are questions easy to answer by yourself using any decent search engine: The /dev directory

1 Like