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
During intensive I/O operations in the background, Nemo hangs and the process can't be restarted.
Steps to reproduce
I had my phone connected transferring over 25gb of photos to an internal HDD, and at the same time I was using a Samba Share to transfer files to the same drive. All in the background.
I had five Nemo windows open, two with the Two Pane functionality, and was copying and pasting small files from one place to another at the same time I had these large operations in the background.
At some point, while doing all of these things together, Nemo hung and couldn't be restarted so I had to restart the whole computer. It happened several times already so I decided to post this as a bug. When I try to restart nemo, I get the message:
"Could not register nemo as a remote: Timeout was reached"
Expected behavior
I think it would be expected not to have to restart the computer after a critical failure.
Additional information
No response
The text was updated successfully, but these errors were encountered:
i'm not sure whatever this related to above issue or not, but nemo also sometimes crashing when opening a directory with thousands of files over NFS (it happens sporadically, so it's hard to capture the stacktrace)
Distribution
Mint 22
Package version
6.2.8
Frequency
Quite often
Bug description
During intensive I/O operations in the background, Nemo hangs and the process can't be restarted.
Steps to reproduce
I had my phone connected transferring over 25gb of photos to an internal HDD, and at the same time I was using a Samba Share to transfer files to the same drive. All in the background.
I had five Nemo windows open, two with the Two Pane functionality, and was copying and pasting small files from one place to another at the same time I had these large operations in the background.
At some point, while doing all of these things together, Nemo hung and couldn't be restarted so I had to restart the whole computer. It happened several times already so I decided to post this as a bug. When I try to restart nemo, I get the message:
"Could not register nemo as a remote: Timeout was reached"
Expected behavior
I think it would be expected not to have to restart the computer after a critical failure.
Additional information
No response
The text was updated successfully, but these errors were encountered: