Hello, this is my first day on this forum and I’d like to ask something about a recent behavior that i got.
This strange behavior happened whenever I tried to open a new file (from the left pane where I list all of my project folders) on partition in exFAT (a local drive), but what I got is a yellow notification with “Socket is not connected” error message. So then I tried to look for the file with file manager but it couldn’t get the job done either as it shows another error with “transport endpoint is not connected” message. Opening a file from the menu doesn’t work either.
I am using Solus (Linux, 64 bit) and this happens since v.1.23.2. I’ve tried safe-mode and it still persists. When I dig into the settings and change the file system watcher to the emulated ones, it solves the problem.
But then since I don’t know much about how atom-watcher works, I turned it back to the native ones and when I scrolled down a bit, I saw the “project home” part and I remember that I used to setup a specific directory (the ones where I stored all of my project files, I mean my local git repo) which is on the same partition as where the problem start all the day. So I left that box empty (default) and it also solves the problem.
But I was still feeling curious about the problem, so I tried to reproduce the problem by setup a folder in a NTFS partition (where my Windows 10 sits) as the “project home” value to see if it would broken the partition. But no, the problem kicks in again only when I tried to open a file from the previous partition. The partition that I’m talking about was in exFAT.
Is this one of the reason for atom-watcher to be there as a second option ? or is this more likely to be a hardware / OS specific problem ?
Thanks, Good night from Indonesia!
Sorry for being less technical.