Bug 229004 - editors/linux-sublime3: Crashes on startup after 3.1.76 update
Summary: editors/linux-sublime3: Crashes on startup after 3.1.76 update
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords: crash, needs-qa, regression
Depends on:
Blocks:
 
Reported: 2018-06-13 23:02 UTC by Gary
Modified: 2019-06-11 22:08 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (miguelmclara)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary 2018-06-13 23:02:30 UTC
/var/log/messages shows

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
11.1-RELEASE-p10
11.1-RELEASE-p10
Comment 1 Tijl Coosemans freebsd_committer 2018-12-16 13:20:20 UTC
Is this still a problem?
Comment 2 Gary 2018-12-16 13:39:31 UTC
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.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-17 04:47:14 UTC
I wonder if file system notifications can be disabled in settings.
Comment 4 Tijl Coosemans freebsd_committer 2018-12-17 10:58:19 UTC
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.
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-17 11:00:37 UTC
(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