Jun 13 13:24:40 hostname pkg: linux-sublime3 upgraded: 3.1.43 -> 3.1.76
Jun 13 13:24:46 hostname kernel: linux: pid 47880 (io_worker): syscall inotify_init not implemented
Jun 13 13:24:47 hostname kernel: pid 47882 (update_check), uid 1001: exited on signal 6
Jun 13 13:24:47 hostname kernel: pid 47880 (update_check), uid 1001: exited on signal 6
3.1.43 works fine. I went back to the old version.
There may be more problems than the SIGABRT in update_check, not sure
% freebsd-version -ku
Is this still a problem?
Just tried on 11.2-RELEASE-p6 with linux-sublime3-3.1.76 - same behaviour.
linux: pid 43534 (io_worker): syscall inotify_init not implemented
pid 43536 (file_read_threa), uid 1001: exited on signal 6
pid 43534 (file_read_threa), uid 1001: exited on signal 6
Although I moved ~/.config/sublime-text-3 out of the way and it was able to start. Not entirely sure why, and makes me wonder if it will start crashing again during use.
I wonder if file system notifications can be disabled in settings.
Missing inotify is not causing this. It has always printed that message. I think this can be closed now. It must have been an upstream bug where the new version didn't handle the old config file properly or something.
(In reply to Gary from comment #2)
If you can identify which setting(s) are causing the issue that might help elucidate something more concrete to report upstream