Summary: | Dolphin crashing while dragging a file to a folder in order to copy it | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Andreas Stangl <andreas-stangl> |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Andreas Stangl
2009-09-05 16:33:55 UTC
- "Two columns" <- is that a split view or the Column view showing the same folder herarchy ? - Which were the folders you were showing ? how they are related? (example: "folder on the right side is a subfolder of the one being shown in the left side") - Do you have desktop compositing/effects ? - Can you reproduce the crash at will ? The backtrace looks like bug 203384 indeed Thanks (In reply to comment #1) > - "Two columns" <- is that a split view or the Column view showing the same > folder herarchy ? This is not a split view. I selected a folder in the left column and the right column showed me the content of the selected folder > - Which were the folders you were showing ? how they are related? (example: > "folder on the right side is a subfolder of the one being shown in the left > side") * <folder 1> * <folder 2> <-- this is the selected folder * <file 1> * <file 2> <-- the files are shown in the right column I tried to move <file 1> to <folder 1> > - Do you have desktop compositing/effects ? Yes, compositing is enabled > - Can you reproduce the crash at will ? Unfortunately not, I was moving a couple of files from <folder 2> to <folder 1> without any problems, but suddenly dolphin crashed. After the crash I continued moving files from <folder 2> to <folder 1> without any problems. Maybe I should also notice this: Dolphin crashed before the popup dialog ("Move File", "Copy File", "Create Link", "Cancel") was shown. *** This bug has been marked as a duplicate of bug 203887 *** |