Nemo crashes when moving and merging folders in List View #2150
Comments
|
I've had this a lot. The issue is moving or deleting items (folders or files) under a folder that's opened as shown above. Deleting causes this more often in my experience. For me it seems to never happen on the first delete. It does seem to happen on the 3rd to 5th delete. It has happened more than once for me moving files as well. But that it still deleting them. Also as noted above, I have never had data loss. |
|
I've seen this occasionally, and have some idea what causes it, I'll look into again. |
|
In looking through the 24 pages of open issues, there seems to be quite a few more if these, each titled differently. |
|
I have manged to catch a bug that looks awfully like the bug I filed. I'm not certain it's the same bug but I can reproduce this one with 100% certainty on my machine. Prep files/folders: Then, click on the disclosure triangle of
Version: @mtwebster I have a feeling that this might be related to empty folders and "(empty)" label that |
|
This should be fixed now - it was indeed related to the adding of the empty row when a folder no longer had any children. Thanks a lot for all of your help |
|
Thank YOU! |
|
@mtwebster thank you so much Michael!!! #2100 |
|
Most of these pre-date the bug's introduction (Around August 2018, in time for 4.0) - I closed the recent ones, and another I knew I had fixed elsewhere. The rest didn't seem related (or reproducible for the most part). |
|
I see that this post is closed, however, I am receiving exactly the same type of error, following approx. the same steps as above. My issue was moving (not deleting) folders, either by dragging, or cut/paste. I initially received a crash, subsequent tries simply caused Nemo to close immediately. When re-opening the window the action (move) that caused the crash did complete correctly. Nemo 4.0.6 |
|
|
@jlarne upgrade nemo. The version you're using is the old version and contains this bug. |
|
Thank you for the notification. I wasn't aware that there was any other newer version available (especially as I wait for the release through the PPA, and am not self compiling), and seem to have the same concerns as issue #2170 . With the number of issues of apparently both in a state of being 'open' and 'closed' (not integrated, yet in some future version), will there be a release coming soon? |
Issue
Nemo often (but not always) crashes when moving and merging folders with multiple files. This is not a recent bug and has been present for a long time. I have had difficulty figuring out what causes crashes and haven't reported it until now. I believe the other bug that used to crash
nemoon my machine has been fixed by @mtwebster in the past month. However, I think this one is a different issue.Click here to expand `gdb` session log
Steps to reproduce
I have not been able to reliably reproduce this bug. Sometimes this series of steps crashes
nemoand sometimes it does not. I've been trying hard over the past few months to find an example that works 100% but was not able to so. I will be runningnemoingdbwhenever possible so I can capture more examples of this crash.Here's a basic series of steps that sometimes cause a crash:
Switch to List View.
Create this folder and file structure:
Now drag the "folder" from "folder 2" onto "folder 1" like this:
nemowill ask you to merge folders and say yes and select the checkbox to "apply this action to all files" before clicking MergeOften, this will work and you will end up with this:
However,
nemowill often crash too and just disappearAnother thing to do is to use arrow keys to move up and down the file list and then try to close/open folders that were merged with left/right arrow keys. That might trigger a segmentation fault too. It triggers it on my system when I open/close "folder 1" and "folder 2".
Note: there is no data loss! Merge succeeds even though
nemocrashes.Expected behaviour
No crashes please.
Other information
As I was writing this bug report,
nemocrashed again when I merged another set of files.Click to expand for another gdb log
The text was updated successfully, but these errors were encountered: