Your best friend for file transfer.

Fetch application logoFetch

Fetch 5.7.3 won't launch, crashes with broken pipe (16 posts)

  • Started 1 year ago by entee
  • Latest reply 5 months ago from MikeiLL
  • entee Member

    I couldn't launch fetch, so I downloaded the most recent version, still no dice, only message in console:

    1/16/13 7:14:44.969 PM com.apple.launchd.peruser.501[151]: ([0x0-0x55055].com.fetchsoftworks.Fetch[629]) Exited abnormally: Broken pipe: 13

    Deleted prefs, caches, etc. but doesn't even seem to get that far before crashing. Help?

    Thanks!

    Entee

    Update: Tested 5.6 and 5.3.1 and they launch with no problems. Also, this machine is running 10.8.2

    Edited 1 year ago #

  • Jim Matthews Administrator

    Hi,

    Is there anything in the Fetch.log file? To find it, go to the Finder, choose Go to Folder… from the Go menu, and enter:

    ~/Library/com.fetchsoftworks.Fetch/Logs

    and click Go

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • entee Member

    That folder doesn't appear to exist on my computer. I can try and look through sys log, but the only report I see on system.log in console is basically the same message as above. One line, broken pipe.

    Posted 1 year ago #

  • Jim Matthews Administrator

    Thanks for trying that; it looks like Fetch isn't getting far enough to even open the log file.

    My next suggestions would be to restart, and to delete Fetch and install a fresh copy. Let me know if neither of those do any good.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • entee Member

    No dice, 5.6 and 5.3.1 launch fine, and I used 5.6 this morning to download a rather large file over sftp without issue. It really seems limited to 5.7.3. I checked about the video codecs, don't seem to have it. Also removed all quicktime plugins, tried launching, still no dice.

    Posted 1 year ago #

  • Jim Matthews Administrator

    Has 5.7.3 ever launched successfully for you on 10.8?

    Posted 1 year ago #

  • entee Member

    Not sure. I haven't used it in a while, I'm going to go with no. I have an old computer that was running 5.7.1. on 10.7, that works well. I only mention it because the current computer is a time machine restore of the old one that's been upgraded.

    I used time machine to restore a 5.7.2 version, that also fails to launch in the same way. Same deal with a restored 5.7.1 version.

    Posted 1 year ago #

  • Jim Matthews Administrator

    Try deleting any Fetch cache or preferences files. To find them, choose Go to Folder… from the Go menu in the Finder and enter either

    ~/Library/Preferences

    or

    ~/Library/Caches

    Then delete anything that starts with "Fetch" or "com.fetchsoftworks.Fetch" (note: that will include your shortcuts, so you might want to copy the files to your desktop rather than deleting them).

    Let me know if that doesn't fix the problem.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • entee Member

    Nope, no change.

    Posted 1 year ago #

  • Jim Matthews Administrator

    My next suggestion would be to reinstall OS X 10.8. A problem with your OS X installation could cause the behavior you are seeing.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • entee Member

    Seriously? I mean, that's a pretty major step. If that's the solution, I'm just not going to use Fetch anymore. I love the program, but I can't reinstall my whole system for one program that won't launch. Everything else works fine. There is nothing else that could be causing this issue?

    Posted 1 year ago #

  • Jim Matthews Administrator

    It's hard to think of anything else. You've removed every Fetch file, and reinstalled Fetch, so you have the same application code and settings that work fine on other 10.8 machines. You could try creating a new account and seeing if Fetch runs when you are logged into that test account; that would tell you if there's something in your regular account that is causing the problem.

    Another thing you could try is launching Fetch from Terminal; I can offer directions if you like.

    The most suspicious thing is that Fetch is failing so early in the launch process, before it even opens a log file. The logging component of Fetch is written in a language called Python, and we have seen cases where a corrupt Python component in OS X caused this sort of problem. The fix is to replace the corrupt component by reinstalling OS X.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • entee Member

    OK that's actually pretty valuable information, I've recently been coding a lot in python and have had to fool around with where the python executable/libraries are located. I've always put symlinks in the place of old interpreters, but might have missed one. Is there any chance you could tell me where the python interpreter Fetch calls is located? I can check to see that it's kosher.

    Posted 1 year ago #

  • entee Member

    I resolved the issue. The default installation of python on OSX 10.8 appears to be /usr/bin/python. On my system that was a symlink to the interpreter I need to use. I replaced that link with the old executable, works fine now, found a workaround for the rest. It still remains strange that 5.6 would launch with no problems, but whatever.

    Thank you for your help, hopefully if someone has this specific problem again this exchange will be useful.

    Posted 1 year ago #

  • Jim Matthews Administrator

    Ah, I wish I'd mentioned the Python issue earlier! I'm glad that fixed the problem.

    Jim Matthews
    Fetch Softworks

    Posted 1 year ago #

  • MikeiLL Member

    this definitely helped me. turned me onto the Console first of all. Error was ImportError no module named Carbon. Also related to Python. Had upgraded to 3.4, but reinstalling 2.7.6 solved the problem. thank you very much.

    Posted 5 months ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.