Bug #153

OSX Python Runtime does not install completely

Added by Michael G about 9 years ago. Updated over 1 year ago.

Status:Closed Start date:04/28/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:MacOS
Model affected:(All models)

Description

I am using OSX vsn 10.5.8 (Leopard). It runs the 0.1.12 version of Chirp, but when I try to run 0.2.2, the program doesn't start. Nothing happens. I have Python installed.


Related issues

duplicated by Bug #160: Mac OS X 10.6.8 Chirp won't run, Python running. Closed 05/04/2012
duplicated by Bug #411: Chirp doesn't open Rejected 01/08/2013

History

Updated by Dan Smith about 9 years ago

Please try the latest daily build. This is likely related to a bug when running from directories that have spaces in the names. It was fixed last week, is in the daily, and will be in 0.2.3

Updated by Michael G about 9 years ago

Dan Smith wrote:

Please try the latest daily build. This is likely related to a bug when running from directories that have spaces in the names. It was fixed last week, is in the daily, and will be in 0.2.3

Thanks. I gave it a try. I saw I needed the newer version of Python, so I installed that (version R7). Interestingly, the installer for that said it was R6, even though the filename was R7. Anyway, I installed it and tried running the latest daily version of Chirp. It did start, and it said it would fetch and install it. Then it came up with "Failed to run Chirp." That's all I get. It appears to be a message from X11.

By the way, how does one uninstall Python? If I can't get this to work, I will want to remove it, but I see no instructions on how.

Thanks.

Michael

Updated by Dan Smith about 9 years ago

Ah, then you're running a way old version of the runtime, and that's likely related. The link on the download page is to R10, and it no longer uses/includes X11. R10 is not compatible with 0.1.12 and 0.2.2+ is not compatible with the older runtme.

You may need to nuke it before moving to R10 just to clean up whatever you have. From a terminal:

sudo rm -Rf /opt/kk7ds

Updated by Michael G about 9 years ago

Dan Smith wrote:

Ah, then you're running a way old version of the runtime, and that's likely related. The link on the download page is to R10, and it no longer uses/includes X11. R10 is not compatible with 0.1.12 and 0.2.2+ is not compatible with the older runtme.

You may need to nuke it before moving to R10 just to clean up whatever you have. From a terminal:

sudo rm -Rf /opt/kk7ds

Sorry, but it doesn't work. I did as you said. I nuked the old version of Python and installed R10. When I try to open the daily, it still comes up with X11, and I get a message saying, "The KK7DS Python runtime for OSX is not installed. The Macport Python2.7 runtime for OSX is not installed. I did a reboot and it didn't help.

And if I try to run Chirp 0.2.2, it still doesn't start up.

Updated by Tom Hayward about 9 years ago

When 0.2.2 "doesn't start up", open Console (you should be able to find it with Spotlight) and copy the last error message here.

Updated by Michael G about 9 years ago

Tom Hayward wrote:

When 0.2.2 "doesn't start up", open Console (you should be able to find it with Spotlight) and copy the last error message here.

OK, here it is:
([0x0-0x2d02d].com.danplanet.chirp715) Exited with exit code: 126
I see another one that says it is looking for /opt/kk7ds/bin/python2.7 and "cannot execute: No such file or directory". When I go to that folder, there is an alias by that name there. Checking for what it points to shows it as /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python 2.7. However, if I go to /opt/kk7ds/Library/Frameworks, it is empty. That appears to be the problem. It's looking for Python 2.7 there, but it's not being installed.

This brings up the question: if I'm installing R10, why is it searching for 2.7? Is that what is supposed to be in the contents of R10? In any event, it's not getting installed, even though the R10 installer says it has installed successfully.

Updated by Tom Hayward about 9 years ago

Is Chirp_0.2.2.app in a directory that contains a space? It sounds like this problem (which was just recently fixed): #145

Try this daily build: http://trac.chirp.danplanet.com/chirp_daily/daily-20120428/chirp-daily-20120428.app.zip Once 0.2.3 comes out, you can switch to that.

Updated by Michael G about 9 years ago

Tom Hayward wrote:

Tom Hayward wrote:

Is Chirp_0.2.2.app in a directory that contains a space? It sounds like this problem (which was just recently fixed): #145

Try this daily build: http://trac.chirp.danplanet.com/chirp_daily/daily-20120428/chirp-daily-20120428.app.zip Once 0.2.3 comes out, you can switch to that.

No, I have it in my Applications folder. No space. But I'll give it a try. If it's looking for Python, though, that is not getting properly installed, apparently.

Updated by Tom Hayward about 9 years ago

Michael G wrote:

No, I have it in my Applications folder. No space. But I'll give it a try. If it's looking for Python, though, that is not getting properly installed, apparently.

I don't see where you said the installer failed, just something about an X11 error which would indicate you weren't opening the newest daily :)

It's easy to test if the runtime exists. Run this command from Terminal:

/opt/kk7ds/bin/python2.7 -V

You should get this response:

Python 2.7.2

Updated by Michael G about 9 years ago

Tom Hayward wrote:

Michael G wrote:

No, I have it in my Applications folder. No space. But I'll give it a try. If it's looking for Python, though, that is not getting properly installed, apparently.

I don't see where you said the installer failed, just something about an X11 error which would indicate you weren't opening the newest daily :)

It's easy to test if the runtime exists. Run this command from Terminal:

/opt/kk7ds/bin/python2.7 -V

You should get this response:

Python 2.7.2

I wrote this above, but maybe it never came through:

I see another one that says it is looking for /opt/kk7ds/bin/python2.7 and "cannot execute: No such file or directory". When I go to that folder, there is an alias by that name there. Checking for what it points to shows it as /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python 2.7. However, if I go to /opt/kk7ds/Library/Frameworks, it is empty. That appears to be the problem. It's looking for Python 2.7 there, but it's not being installed.

Updated by Tom Hayward about 9 years ago

Michael G wrote:

I see another one that says it is looking for /opt/kk7ds/bin/python2.7 and "cannot execute: No such file or directory". When I go to that folder, there is an alias by that name there. Checking for what it points to shows it as /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python 2.7. However, if I go to /opt/kk7ds/Library/Frameworks, it is empty. That appears to be the problem. It's looking for Python 2.7 there, but it's not being installed.

Thanks, I missed that detail the first time. Did R10 report any errors during installation? I've never seen it fail quietly. If it is indeed failing, we need to determine what differs in your system. Both Dan and I have only tested on OS X 10.6, but I suspect you're not the only OS X 10.5 user.

Updated by Michael G about 9 years ago

Tom Hayward wrote:

Michael G wrote:

I see another one that says it is looking for /opt/kk7ds/bin/python2.7 and "cannot execute: No such file or directory". When I go to that folder, there is an alias by that name there. Checking for what it points to shows it as /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python 2.7. However, if I go to /opt/kk7ds/Library/Frameworks, it is empty. That appears to be the problem. It's looking for Python 2.7 there, but it's not being installed.

Thanks, I missed that detail the first time. Did R10 report any errors during installation? I've never seen it fail quietly. If it is indeed failing, we need to determine what differs in your system. Both Dan and I have only tested on OS X 10.6, but I suspect you're not the only OS X 10.5 user.

No errors were reported. It said the software had installed successfully. The problem seems to be with the Python installer. For one thing, it says it will require 135 (I think) mb, and it's only around 80mb itself. Where's the rest of the data supposed to come from? Or is it just compressed?

Updated by Michael G about 9 years ago

Ok, I ran the terminal command to check for Python 2.7, as you suggested. It comes back with "No such file or directory." Clearly, Python is not getting installed properly, even though its installer says it is. Hmmm, do I need internet access while installing it? Or is the installer self-contained?

Updated by Tom Hayward about 9 years ago

  • Subject changed from Chirp OSX vs 0.2.2 will not run to OSX Python Runtime does not install completely

Updated by Dan Smith about 9 years ago

Tom, isn't this just a matter of nuking the old runtime package so the new one will install properly?

Updated by Tom Hayward about 9 years ago

Dan Smith wrote:

Tom, isn't this just a matter of nuking the old runtime package so the new one will install properly?

He says he did that. See #153#note-4

Updated by Rob Walker about 9 years ago

I think that in http://chirp.danplanet.com/issues/153#note-10 , the error makes it clear that the /opt/kk7ds/Library/Frameworks/ directory didn't get installed properly with the install of R10 of the framework. I installed R10 today, and my python is running properly, as evidenced below:

[684]rwalker@a:~$ ls -alhrt /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
-rwxr-xr-x 1 itadmin wheel 13K Feb 13 20:23 /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
[684]rwalker@a:~$ ls -alrht /opt/kk7ds/bin/python2.7
lrwxr-xr-x 1 itadmin wheel 73 Jun 8 08:26 /opt/kk7ds/bin/python2.7 -> /opt/kk7ds/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
[685]rwalker@a:~$ /opt/kk7ds/bin/python2.7 -V
Python 2.7.2
[686]rwalker@a:~$

I believe what the end user needs to do is another 'rm -rf' and then reinstall R10. Until '/opt/kk7ds/bin/python2.7 -V' returns "Python 2.7.2" as it should, I don't see how this can be a chirp error.

Thanks,
Rob

Updated by Jens Jensen almost 7 years ago

  • Status changed from New to Resolved
  • Chirp Version changed from 0.2.2 to 0.4.0

Updated by Bernhard Hailer over 1 year ago

  • Status changed from Resolved to Closed
  • Chirp Version changed from 0.4.0 to daily

Also available in: Atom PDF