Bug 208618 - editors/linux-sublime3: Sublime executable doesn't work
Summary: editors/linux-sublime3: Sublime executable doesn't work
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-07 20:27 UTC by stephleg
Modified: 2016-04-08 20:30 UTC (History)
1 user (show)

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


Attachments
truss trace (25.66 KB, text/plain)
2016-04-07 20:27 UTC, stephleg
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description stephleg 2016-04-07 20:27:06 UTC
Created attachment 169090 [details]
truss trace

Hello,

After an upgrade from 10.2 to 10.3, i'm no longer able to launch Sublime Text 3. I upgraded the system with freebsd-upgrade, then the packages with pkg. Everything is ok except for Sublime. When i try to run the "sublime" executable, i get nothing. No window, no error message.

I also tried on Virtualbox with the 10.3 virtual image. And it's the same problem. The package installation works well. But the executable doesn't work.

I posted a message on the FreeBSD forum to ask if other users have the same problem: https://forums.freebsd.org/threads/55757/. For now, i didn't received any answer.

Configuration: 10.3-RELEASE amd64 with a GENERIC kernel.


# kldstat
Id Refs Address            Size     Name
 1   63 0xffffffff80200000 17bc680  kernel
 2    2 0xffffffff819bd000 9aed0    linux.ko
 3    3 0xffffffff81a58000 c128     linux_common.ko
 4    1 0xffffffff81a65000 b679b8   nvidia.ko
 5    3 0xffffffff825cd000 6d430    vboxdrv.ko
 6    1 0xffffffff82811000 26b76    vboxguest.ko
 7    1 0xffffffff82838000 358d     ums.ko
 8    2 0xffffffff8283c000 29b2     vboxnetflt.ko
 9    2 0xffffffff8283f000 ba02     netgraph.ko
10    1 0xffffffff8284b000 4123     ng_ether.ko
11    1 0xffffffff82850000 3f64     vboxnetadp.ko
12    1 0xffffffff82854000 8a3      dtraceall.ko
13   10 0xffffffff82855000 3330     opensolaris.ko
14   10 0xffffffff82859000 3ac92    dtrace.ko
15    1 0xffffffff82894000 4644     dtmalloc.ko
16    1 0xffffffff82899000 22b9     dtnfscl.ko
17    1 0xffffffff8289c000 63ce     fbt.ko
18    1 0xffffffff828a3000 580c2    fasttrap.ko
19    1 0xffffffff828fc000 49d2     lockstat.ko
20    1 0xffffffff82901000 15ff     sdt.ko
21    1 0xffffffff82903000 d8d6     systrace.ko
22    1 0xffffffff82911000 d4a4     systrace_freebsd32.ko
23    1 0xffffffff8291f000 4da5     profile.ko
24    1 0xffffffff82924000 6469     nullfs.ko
25    1 0xffffffff8292b000 56c6     fdescfs.ko
26    1 0xffffffff82931000 9faf     linprocfs.ko

# pkg info | grep linux | cut -d ' ' -f 1
linux-c6-alsa-lib-1.0.22_2
linux-c6-alsa-plugins-oss-1.0.21_3
linux-c6-atk-1.30.0
linux-c6-cairo-1.8.8_4
linux-c6-curl-7.19.7_5
linux-c6-cyrus-sasl2-2.1.23_3
linux-c6-dbus-glib-0.86_2
linux-c6-dbus-libs-1.2.24_4
linux-c6-expat-2.0.1_2
linux-c6-flashplugin-11.2r202.569
linux-c6-fontconfig-2.8.0_1
linux-c6-gdk-pixbuf2-2.24.1
linux-c6-gtk2-2.24.23_1
linux-c6-hicolor-icon-theme-0.5_4
linux-c6-jpeg-1.2.1_1
linux-c6-libssh2-1.4.2_4
linux-c6-nspr-4.10.8_2
linux-c6-nss-3.19.1
linux-c6-openldap-2.4.40
linux-c6-openssl-1.0.1e_7
linux-c6-openssl-compat-0.9.8e_2
linux-c6-pango-1.28.1_2
linux-c6-png-1.2.49_2
linux-c6-sqlite-3.6.20_3
linux-c6-tiff-3.9.4_1
linux-c6-xorg-libs-7.4_4
linux-firefox-45.0.1,1
linux-sublime3-3.0.83_1
linux_base-c6-6.7_1
linuxlibertine-g-20120116_1

Thanks for any help.

Regards,
Stéphane.
Comment 1 miguelmclara 2016-04-08 05:13:14 UTC
Hi, try sublime -w as it sometimes shows a bit more info when sublime fails to start, however I would say this is related to the tmpfs changes and you should get a message warning about that when installing linux-c6 ...sublime needs shm but now shm also needs to be a tmpfs filesystem.

In my local machine I link dev/shm to /ram and /ram in a tmpfs filesystem but you can off do that for /tmp.

sadly sublime binary can't tell you that's why it fails, however -w wi at list say it couldn't init shm.


Hopefully that's the issue your seeing, and it's easily solved
Comment 2 miguelmclara 2016-04-08 05:15:41 UTC
P.S. sorry for the smartphone auto correct typos -.-'
Comment 3 stephleg 2016-04-08 20:29:55 UTC
(In reply to miguelmclara from comment #1)

That was exactly that! Thank you very very much for your help. I will forward the solution to the FreeBSD forum thread.

Again, many thanks for your answer.

Stéphane.