Failure to launch

Asked by Jonny

Hello! I am using version 1.7 (64-bit) for MacOS on 10.8.5 (Mountain Lion). I just downloaded the dmg and installed the app to the default location.

The app icon appears briefly in the dock and disappears, the console doesn't provide much help- no crash log... It merely states it exited with code: 2. I have tried this several times with the same result.

I wish I could provide more information or detail.

What does error 2 signify?

Is there anything I could do to obtain more information? Or anything I might try to mitigate or resolve the issue?

Thank you so much!

Question information

Language:
English Edit question
Status:
Solved
For:
DDRescue-GUI Edit question
Assignee:
No assignee Edit question
Solved by:
Jonny
Solved:
Last query:
Last reply:
Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said :
#1

Hi,

Unfortunately, I haven't been able to find the cause, but I know v1.6.1 works. There seems to be an issue running this version in particular on 10.6, 10.7 and 10.8, perhaps because I now build the packages on Sierra, instead of El Capitan. This is partially why I'm dropping support for those releases of OS X.

Tricky solution:

Open the Terminal from Applications/Utilities and run (without the quotes).

"sudo -H /Applications/DDRescue-GUI.app/Contents/MacOS/DDRescue-GUI" (copy and paste)

and it should work as expected.

Easy solutions:

You could try 1.6.1, a 32-bit version of 1.7, or upgrade to OS X 10.9 or higher, which don't seem to have this problem.

Sorry for the inconvenience.
Hamish

On 7 May 2017, 12:04 +0100, Jonny <email address hidden>, wrote:
New question #631618 on DDRescue-GUI:
https://answers.launchpad.net/ddrescue-gui/+question/631618

Hello! I am using version 1.7 (64-bit) for MacOS on 10.8.5 (Mountain Lion). I just downloaded the dmg and installed the app to the default location.

The app icon appears briefly in the dock and disappears, the console doesn't provide much help- no crash log... It merely states it exited with code: 2. I have tried this several times with the same result.

I wish I could provide more information or detail.

What does error 2 signify?

Is there anything I could do to obtain more information? Or anything I might try to mitigate or resolve the issue?

Thank you so much!

--
You received this question notification because you are an answer
contact for DDRescue-GUI.

Revision history for this message
Jonny (aural.arch) said :
#2

Thank you SO much for such a rapid response!!!

I'm fairly experienced on Mac so I went for the terminal solution which seems to work :) (It has launched, I have yet to perform any operations...)

I thought of trying the 32bit version but suspected that may cause more problems. My next step was to try the previous version.

I understand your reasoning for dropping support on the older OS releases. Although it's disappointing to see support for 10.8 being dropped all over the place...
The main reason I don't update is because of a fingerprint scanner I have which I can use to authenticate and log in- it also stores passwords for websites. The manufacturer was bought by Apple and shut down. It seems they probably used some of the technology eventually for the fingerprint scanner on iPhones, but their main reason was to stop a major deal the company had to supply Samsung with components. Unfortunately 10.8 is the highest version of OS the software will run on. It sounds ridiculous, but I make my passwords long and complicated and it is a major convenience to be able to swipe my finger instead of manually entering them. I honestly am frustrated and surprised that Apple hasn't come out with any fingerprint scanners for their computers/MacOS. They have all the patents for the technology as well as the software- and the company was by far the global leader in all such technology!

Anyway, thank you so much!

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said :
#3

Ah, I see.

Mountain Lion doesn't get any security updates anymore, so may be better to update. I'm sure you've thought it over anyway. The lack of support for those 3 releases was limiting me so I decided the best way forward was just to drop support eventually, but I see what you mean.

You're welcome,
Hamish

On 7 May 2017, 12:45 +0100, Jonny <email address hidden>, wrote:
Question #631618 on DDRescue-GUI changed:
https://answers.launchpad.net/ddrescue-gui/+question/631618

Status: Answered => Solved

Jonny confirmed that the question is solved:
Thank you SO much for such a rapid response!!!

I'm fairly experienced on Mac so I went for the terminal solution which
seems to work :) (It has launched, I have yet to perform any
operations...)

I thought of trying the 32bit version but suspected that may cause more
problems. My next step was to try the previous version.

I understand your reasoning for dropping support on the older OS releases. Although it's disappointing to see support for 10.8 being dropped all over the place...
The main reason I don't update is because of a fingerprint scanner I have which I can use to authenticate and log in- it also stores passwords for websites. The manufacturer was bought by Apple and shut down. It seems they probably used some of the technology eventually for the fingerprint scanner on iPhones, but their main reason was to stop a major deal the company had to supply Samsung with components. Unfortunately 10.8 is the highest version of OS the software will run on. It sounds ridiculous, but I make my passwords long and complicated and it is a major convenience to be able to swipe my finger instead of manually entering them. I honestly am frustrated and surprised that Apple hasn't come out with any fingerprint scanners for their computers/MacOS. They have all the patents for the technology as well as the software- and the company was by far the global leader in all such technology!

Anyway, thank you so much!

--
You received this question notification because you are an answer
contact for DDRescue-GUI.

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said :
#4

I have released a new version, v1.7.1, which fixes this issue.

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said :
#5

^ No it doesn't :P Oh well.