Bug 376634 - Moving a folder from ext4-formated partition to a FAT32 partition does not remove all files at source and dolphin sometimes even segfaults
Summary: Moving a folder from ext4-formated partition to a FAT32 partition does not re...
Status: RESOLVED DUPLICATE of bug 364039
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.08.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-18 20:31 UTC by Sebastian Ernst
Modified: 2017-02-19 10:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
dolphin segfault backtrace (9.01 KB, text/plain)
2017-02-18 20:31 UTC, Sebastian Ernst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Ernst 2017-02-18 20:31:51 UTC
Created attachment 104104 [details]
dolphin segfault backtrace

Dolphin 16.02.2 on openSUSE Leap 42.2 Linux.

I am trying to move a bunch of folders from an ext4-formatted (home-) partition to another FAT32-formated partition. (The folders and files therein originated mostly from a digital camera, which has a FAT32-formatted SD-card itself.) When doing so, Dolphin throws some "access denied" errors for some seemingly random files at the target of the move operation although every file is actually copied into its desired destination. Additionally, the files for which there is an error message are not removed at the source location. Moving the same set of files with the bash command "mv" only throws the usual messages about being unable to maintain access rights but moves all folders / files in question without leaving any copies at the source location. Its rather strange. Any suggestions on how to debug this any further are highly appreciated. 

During one try, I got a segfault - see attachment.
Comment 1 Elvis Angelaccio 2017-02-19 10:29:59 UTC
Hi, there is already a report for this. Please continue there.

*** This bug has been marked as a duplicate of bug 364039 ***