PropellerIDE with Kubuntu 15.04 (error SOLVED)
VonSzarvas
Posts: 3,450
So I've been using PropellerIDE recently with Kubuntu... worked great until today. Now this error appears when building: "Could not start . "
Can't find a log file with more detail.... Anyone know about this "error" ? Preferences look sound, and point to actual files. hmm Maybe permissions...
Trying to recall what might have changed... I installed SimpleIDE last week to work on some C code. That worked OK, and still works today. There may have been some system updates during the week, but nothing else manually installed.
oh, and I just re-download and re-installed PropellerIDE from GitHub, but no improvement. And SimpleIDE still working fine.
Can't find a log file with more detail.... Anyone know about this "error" ? Preferences look sound, and point to actual files. hmm Maybe permissions...
Trying to recall what might have changed... I installed SimpleIDE last week to work on some C code. That worked OK, and still works today. There may have been some system updates during the week, but nothing else manually installed.
oh, and I just re-download and re-installed PropellerIDE from GitHub, but no improvement. And SimpleIDE still working fine.
Comments
Sounds like it cannot find the OpenSpin binary.
I suspect that in Edit->Preferences you should see a path to OpenSpin specified.
(Actually I'm guessing where "Preferences" may be, it's a while since I tried Propeller IDE and I forget)
Edit/Preferences (of F5 shortcut) takes you there.
All the prefs (compiler, loader, library, terminal) appear correct. Clicking the helper "browse" button next to each filename text-box takes me straight to the file too. And just for fun, re-connecting the files seems to re-fill text-boxes with the correct data. And the files are executable and seem to have the correct owner (me!)
Just had a thought though.... maybe SimpleIDE uses different version of the compiler, so that install may have overwritten openspin. And then the re-install of PropellerIDE may not have re-installed the openspin version it prefers....
will go experiment ...
uninstalled simpleide & propelleride
checked openspin was gone from /usr/bin
installed propelleride
same error.
oh well- without finding an error log this is not going to be productive!
I'll move to another system for now, and ask Brett if there's an error log lurking somewhere before thinking any more about the meaning of .
Would be good to solve the mystery for anyone else trying ubuntu with PropellerIDE.
Might just be an innocent looking system update this week that's knocked out the serialport library, or some other dependency.
$ /usr/bin/openspin
and so on.
For my benefit, please paste the output of the following commands:
- cat ~/.config/Parallax/PropellerIDE.conf
- qmake -v
- uname -a
- ldd ${path to openspin}
Some things to try to help you out of your jam:
- Delete ~/.config/Parallax/PropellerIDE.conf.
- See if there are any running instances of openspin and kill them off.
Let me know if that helps.
OH: It should be noted that the command-line interfaces of the SimpleIDE and PropellerIDE versions of OpenSpin are different, and future versions of PropellerIDE will include alternate names for external binaries to prevent possible issues like this.
@Heater... that answers your idea also... that openspin works. Thanks!
I deleted that file etc... but no help unfortunately.
Just to note... that .conf is not recreated when PropellerIDE opens/closes again. Guessing therefore that's only created at install time? Anyway, without that file PropellerIDE seems to work up to the same point as before (same . error), and also the F5 Preferences are intact correctly. Maybe that's useful info.
Thanks for trying to help out.
and propterm works too from the command line, opening up the terminal window as expected.
Also, it is expected that the system paths in Preferences are still valid because sensible defaults are used when no config file is found.
When checking the ownership on the ~/.config/Parallax folder, that showed as root. So I deleted that Parallax folder and re-ran PropellerIDE, which re-created the folder and .conf file, and now seems to work again! Both now with me as the owner, rather than root.
For future readers who don't wish to lose .conf settings.... chown could also be an option!
-
OK, I'm not gonna insist that I didn't cause this..... although I'm feeling confident that I didn't go into that Parallax folder and change the owner!
That said, I can't imagine any random OS updates doing that either, so the issue seems odd. As mentioned before, I did install SimpleIDE before this issue... SimpleIDE seems to create it's own .config folder called "ParallaxInc", but maybe it also touches the "Parallax" folder too?? Wouldn't make much sense, but anything is possible I suppose.
Perhaps PropellerIDE could check the config folder owner at startup, and report a meaningful error message / solution if this happens?
All just ideas and feedback. Now I can get to work!
Happy
But...I thought SimpleIDE was dropping support for Spin anyway.
Just as well I use Vim and the command line
Ooo, I just stumbled across this.
As far as I know, SimpleIDE dropped support for Spin a long time ago. I found that out when I could no longer build any of my projects with it (which is how I got involved in PropellerIDE in the first place).
In any event, the OpenSpin distributed with PropellerIDE is identical to the mainline OpenSpin except that it replaces the command-line interface with a Qt-based one that can be parsed by GNU help2man.
And I also spend most of my time in the terminal. =P
Hi there, I thought that would do the trick! Sorry my reply took so long. =P
I suspect what happened is that propelleride was running as root on its first startup, which is quite likely if the user doesn't have access to the serial port, but who knows. I frequently forget to set up the dialout group when I'm setting up new development machines and run the thing as root instead because I can't remember the one-liner to configure permissions. That's the kind of thing I'm talking about.
At any rate, there's still a lot of changes to be made to how the config system works. Checking to make sure the config file is readable and write-able is definitely a good idea.
Happy Spinning!