CANVAS FAILS NODE GYP REBUILD OSX 2017 INSTALL
If you install the snap with an executable stack, and then you add this to /var/lib/snap/apparmor/profiles/: /dev/nvidiactl m, If you launch the snap from a terminal, what are the differences with the terminal output between devmode and strict? What is the output of snap version? If it isn’t 2.30 or higher, can you try with the snap from beta (sudo snap refresh core -beta)? Contribute to dmiller309/electron-snap-webgl development by creating an account on - is this something you could help with? I looked at the chromium snap which doesn’t have any executable stack binaries and put in chrome://gpu and it lists WebGL as available on my 17.10 Intel system (I don’t have an nVidia system). It supports WebGL when run with npm start but does not support WebGL when run as a snap:Įlectron WebGL in a snap package. I’ve created a simple electron WebGL app for testing. dist/linux-unpacked/polarrĪnd that version also lacked WebGL support. I tried clearing execstack on 1.4.3 with watch -n 0.1 execstack -c. Npm install -save & find node_modules/electron/ | xargs execstack 2>/dev/null | grep XĪll revisions that existed had an execstack for node_modules/electron/dist/electron. I tried a variety of Electron versions electron versions npm install -save & find node_modules/electron/ | xargs execstack 2>/dev/null | grep X Since I’m using npm rebuild, am I responsible for configuring npm and gyp so that they don’t produce binaries with executable stacks? Or is electron responsible for the way that it npm rebuilds to not have an executable stack? When I get home I’ll try using a version of electron other than 1.8.1 to see if it produces an binary without an executable stack. I have dlib and libraw C++ nodejs addons, so I use npm rebuild and node-gyp rebuild: ELECTRON_VERSION="1.8.1" I see on AppArmor denial for /dev/nvidiactl that electron builds occasionally have binaries with executable stacks. Is all I can do at this point just wait for snaps to support NVIDIA? If that’s the case, how long will I have to wait and how will I know that this has been taken care of so that I can move forward with packaging my app for Ubuntu?
CANVAS FAILS NODE GYP REBUILD OSX 2017 DRIVER
Chromium snap doesn't work with the nvidia proprietary driver.I see that there’s some ongoing work with nvidia in snaps: I’m just guessing, but I think what’s really killing the webgl context is the deny on /dev/nvidiactl. I’m not really sure why my electron is messing with bluez, but I see the same logs from in Chromium snap doesn't work with the nvidia proprietary driver. Log: apparmor="ALLOWED" operation="dbus_signal" bus="system" path="/" interface="" member="InterfacesAdded" name=":1.18" mask="receive" pid=4215 label="" peer_pid=1194 peer_label="unconfined" Log: apparmor="ALLOWED" operation="dbus_signal" bus="system" path="/org/bluez/hci0/dev_A8_5C_2C_95_4C_E8" interface="" member="PropertiesChanged" name=":1.18" mask="receive" pid=4215 label="" peer_pid=1194 peer_label="unconfined"
* verify program isn't using an executable stack: Log: apparmor="DENIED" operation="file_mmap" profile="" name="/dev/nvidiactl" pid=26914 comm="polarr" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0
Log: apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="" member="GetManagedObjects" mask="send" name="org.bluez" pid=26725 label="" peer_pid=1194 peer_label="unconfined" INFO: $ sudo journalctl -output=short -follow -all | sudo curity scanlog I checked the security log ( ) and received $ sudo /snap/bin/curity scanlog polarr
0 kommentar(er)
