[dolphin] [Bug 453747] New: dolphin crash on moving/copying file, when target folder was mounted after starting dolphin with the unmounted folder

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=453747

            Bug ID: 453747
           Summary: dolphin crash on moving/copying file, when target
                    folder was mounted after starting dolphin with the
                    unmounted folder
           Product: dolphin
           Version: 22.04.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: panels: folders
          Assignee: dolphin-bugs-null at kde.org
          Reporter: uwe.brinkhoff at gmx.net
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. open in a tab a folder from a mounted LUKS-partition. 
2. close dolphin and unmount the LUKS-partition.
3. open dolphin --> remark folder doesn't exists, no files shown
4. mount the LUKS-partion
5. refresh tab (F5) --> the files in the new mounted folder displayed
6. move or copy a file from konqueror to tab --> dolphin crash


OBSERVED RESULT
crash

EXPECTED RESULT
moving / copying the file

SOFTWARE/OS VERSIONS
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.5 [KCrashBackend]

ADDITIONAL INFORMATION
The crash can be reproduced every time.

After restarting dolphin  - very quick and easy - dolphin reports an existing
file with 0 Bytes with the same name. Now the moving / copying operates
correct.

By omitting the refresh (step 5) or if the file exists, dolphin doesn't crash.

-- Backtrace:
A useful backtrace could not be generated

-- 
You are receiving this mail because:
You are on the CC list for the bug.