You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue
Nemo crashes every time I try to copy a few files over ssh. Kernel says
[533300.681161] nemo[13108]: segfault at 0 ip 0000000000000000 sp 00007ffff8805f28 error 14 in nemo[559d787da000+1a8000]
Steps to reproduce
Open an ssh folder in a Nemo tab, open a local folder in a new tab, copy a few files in the remote folder, paste into local folder. Nemo usually copies the first few files, then becomes unresponsive and then crashes. Generally, it does not copy all files.
Expected behaviour
It should copy the files. If I perform the same action in Nautilus it works.
Other information
This happens in 2 different computers which were upgraded from Ubuntu 17.10 to 18.04.
The text was updated successfully, but these errors were encountered:
Sure, please let me know how to do that and I will provide you with the data. I have virtually the same installation on 3 computers, and this happens pretty consistently on 2 of them.
Same setup, noticed that issue as well. The first time. I have not been able to get anything to show up when I connect. No files, no folders, just an empty "folder." No errors, nothing. Just sits there.
Can connect via ssh in the CLI, but a hint, filezilla wont connect either? Just keeps timing out.
Issue
Nemo crashes every time I try to copy a few files over ssh. Kernel says
[533300.681161] nemo[13108]: segfault at 0 ip 0000000000000000 sp 00007ffff8805f28 error 14 in nemo[559d787da000+1a8000]
Steps to reproduce
Open an ssh folder in a Nemo tab, open a local folder in a new tab, copy a few files in the remote folder, paste into local folder. Nemo usually copies the first few files, then becomes unresponsive and then crashes. Generally, it does not copy all files.
Expected behaviour
It should copy the files. If I perform the same action in Nautilus it works.
Other information
This happens in 2 different computers which were upgraded from Ubuntu 17.10 to 18.04.
The text was updated successfully, but these errors were encountered: