davidferguson / pibakery

The blocks based, easy to use setup tool for Raspberry Pi
http://www.PiBakery.org
GNU General Public License v3.0
1.49k stars 147 forks source link

Cannot load from sd card #173

Open kstripp opened 5 years ago

kstripp commented 5 years ago

When I try loading from SD card, a dialog appears with a drop down to select. The "Load" button does nothing at all though, but the "Close" button does close the dialog.

System: Debian Sid 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux

npm --version: 5.8.0 node --version: v10.15.0

Full terminal output when launching:

$ sudo npm start
[sudo] password for scott: 
npm WARN npm npm does not support Node.js v10.15.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

> PiBakery@2.0.0 start /home/scott/.local/opt/pibakery
> electron .

There is no terminal output whatsoever after that. How do I enable debug output? If I can do that, hopefully I can provide more useful info.

kstripp commented 5 years ago

Interesting update:

The output I get above is if I try running with the system npm. If however I run it using nodeenv, I get this:

(env)scott@hephaestus ~/.local/opt/pibakery $ npm start

> PiBakery@2.0.0 start /home/scott/.local/opt/pibakery
> electron .

Segmentation fault
npm ERR! code ELIFECYCLE
npm ERR! errno 139
npm ERR! PiBakery@2.0.0 start: `electron .`
npm ERR! Exit status 139
npm ERR! 
npm ERR! Failed at the PiBakery@2.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/scott/.npm/_logs/2019-01-30T04_58_48_637Z-debug.log
Segmentation fault

Now the load button responds and the dialog closes, but nothing loads from the card. (note, it now does this for both system and local npm... unlike last night. But as far as I know, nothing changed).

I've attached the error log. 2019-01-30T04_58_48_637Z-debug.log