Files crashes immediately after opening #1753
Comments
|
Small update. Opening files as an administrator is still possible, probably because that's from another directory. I managed to work around the issue by opening files from a terminal window in a different directory than it was crashing on. Nevertheless, it would be nice not to have it crash because it locks out the user. |
|
Are you able to install the |
|
I am able to install them, but unable to reproduce the issue now. I've tried creating a directory in Files, closing Files, renaming the directory in the Terminal, re-opening Files, but that's not it. I'll keep an eye on it and report back in case it happens again. |
|
Ok, I've got this going on again. I've installed From Particularly this line is interesting: That's the folder I created and renamed. At first, I called it Bla Bla, then renamed it to BlaBla, but that didn't reproduce the error. Then I deleted it and now Files seems to be crashing on it. |
|
Thanks for trying! After running |
|
You are right it does look like Files is crashing when restoring that file but the gdb backtrace should give clearer information. Files should be designed to tolerate problems restoring particular files. You can stop Files restoring previously opened tabs by temporarily turning off "History" under "System Settings/Privacy & Security". |
Right, that makes sense, I've never used gdb before. :) And here's the backtrace:
Good to know, thanks! |
|
I am not getting a crash when restoring a folder that has been deleted by another application. I get the |
|
In case it matters, could you indicate which view mode you are using and whether there is a bookmark to the problem folder? |
I'm almost always using the Columns view mode.
Inside the parent folder, I re-created a folder with the same name from the terminal, and Files is no longer crashing. Then I closed Files, deleted the folder again, opened Files and still no crash. But Files is also no longer opening that particular directory, while it did before. It's hard to reproduce, but still, it happened twice to me. So something is not right. I'll have to keep watching it. |
|
OK, thanks. So, if you are using ColumnView, there are two folders that are specified for restoring each tab - the leftmost (root) folder and the rightmost (tip) folder. Is the problematic folder the root, the tip or one of the intermediate folders? |
|
Deleting either the root or the the tip folder resulted in an additional warning ` |
Good point. I could only see the files window for a fraction of a second, because it opened and immediately closed again. But during the fade-in and fade-out I could see the deleted folder was selected. So somehow Files thought the folder was still present while in fact, it wasn't. It's frustrating that I can't reproduce this. |
|
This is still going on. Here's the trace: This is a brand new elementary OS 7 installation: Turning off the Restore tabs option in Tweaks fixes the issue:
|
|
@thanks for the update. Could you confirm that you are restoring a Column View? Could you check which folders are being restored and whether they exist and whether they are connected/mounted? You can see which tabs are stored by inspecting the key Do the relevant directories restore OK in Icon or List View? Does Column View restore a single folder OK? |
|
If you could install |
|
I'm almost exclusively using Column View, so that's definitely the case. Here's the content of the files settings: There are a bunch of duplicates at the end What I'm getting with UPDATE |
wout
changed the title
|
Tested another view by disabling Restore Tabs, opening Files to enable Icon View, then close Files, re-enable Restore Tabs and it also crashes. This is what it looks like:
It seems to be stuck in a transition. Did the same with List view and something similar is happening there with the Column View icon pressed but the List View icon highlighted:
|
|
Thanks that is helpful. It seems a couple of folders When running under The pathbar glitch is not relevant I think - I get that occasionally on startup but have never got round to investigating it as it causes no problems. |
Both folders no longer exist, so I can't navigate to them. The former is removed, the latter renamed.
Recreating |
|
Thanks. I tried restoring deleted folders and while I got a lot of terminal errors Files did not crash - however there could be timing differences between different systems. There is clearly some mishandling of this situation which I will look into. |
What Happened
After opening files, it immediately closes again.
Expected Behavior
Should stay open.
Logs
From syslog:
Platform Information
The text was updated successfully, but these errors were encountered: