Serviio no working on Mountain Lion (OS X 10.8)

Every time I try to run Serviio or the console I get the message that the file is damaged and should be moved to the trash. I suspect his is something simple but have no idea what to do.

I have downloaded several times, repaired permissions, etc, etc.

[will]

Not a mac user but I think it could be todo with apple removing java by default. Can you check that java is installed/which version it is.

Not a mac user but I think it could be todo with apple removing java by default. Can you check that java is installed/which version it is.

The previous version of serviio (0.6.2) will run. The new version will not.

I suspect something is wrong with the permissions since when I open terminal window and check serviio I see the following:


drwx---r-x@ 3 repeters repeters 102 Jul 28 09:55 Serviio-Console.app
drwx---r-x@ 3 repeters repeters 102 Jul 28 09:55 Serviio.app

What the heck is the '@' sign after the final 'x' and before the '3'.


The previous version of serviio has the following permissions:


drwxr-xr-x 3 repeters admin 102 Mar 14 11:20 Serviio-Console.app
drwxr-xr-x 3 repeters admin 102 Mar 14 11:20 Serviio.app

Mac OS X (10.8) contains a facility called the Gatekeeper. The default setting for this (in the "Sysyem Preferences", "Security&Privacy) is as shown below.

Allow applications downloaded from: • Mac App Store and identified developers

This means that the application must have been downloaded from the Mac App store of from an identified developer. Otherwise, it will not be allowed to execute.

I was forced to choose "• Anywhere" for acceptable application sources.

This is not desirable even though that is how things were before OS X 10.8. I hope the folks at serviio.org can become "identified developers" to keep users from determining why version 1.0 won't run. I found the reason but most will not.

[will]

Can you not control click and then open the Serviio.app and control click and open the Serviio-Console.app (you only have to do it the first time) http://www.tuaw.com/2012/07/26/mountain ... atekeeper/ and http://support.apple.com/kb/HT5290

Can you not control click and then open the service and control click and open the conole (you only have to do it the first time) http://www.tuaw.com/2012/07/26/mountain ... atekeeper/ and http://support.apple.com/kb/HT5290

That's true. However, I would prefer to have Serviio start automatically when I log in.

The real issue is that I have been using computers (including unix) since 1962 and it took me quite a while to see what was happening. A cleaner solution would be for the folks at serviio.org to become "identified developers" (No, I don't know what effort that requires but I suspect not a whole lot.)

[will]

From how I read the docs, you only have to do it the first time you install serviio, after that it will start up automatically just fine.

Did the OS not pop up a message saying cannot run XXX as it is not allowed due to security settings?

I guess it will be the yearly developer fee + a few extra steps to sign the the installer each time it is built.

From how I read the docs, you only have to do it the first time you install serviio, after that it will start up automatically just fine.

Did the OS not pop up a message saying cannot run XXX as it is not allowed due to security settings?

I guess it will be the yearly developer fee + a few extra steps to sign the the installer each time it is built.

The message basically indicated that the application was damaged and should be moved to the trash. You are correct regarding right-clicking on the application on the first launch. A lot of people will miss that. I just changed the Gatekeeper setting back to it's original value and the serviio apps launch just as expected. Remember that altering the Gatekeeper setting requires administrator privileges.

[will]

The message basically indicated that the application was damaged and should be moved to the trash.

Well that is a pretty useless message!

Well at a minimum i'm sure zip can put these instruction in the FAQ on the website.

[will]

@repeters Please can you post step by step instructions for how to get serviio working without dissabling gatekeeper so that zip can update the FAQ as none of us have it in order to test.

Use this as a base, and make it as specific/clear as you can.

Mac OS X 10.8 (Mountain Lion) introduces a new feature called 'Gatekeeper'. When you install Serviio you will have to perform the following steps in order to allow Serviio to run:
1. Control-click on Serviio.app and select open. When a popup shows saying that Serviio is from an unidentified developer, press 'Open'
2. Control-click on Serviio-Console.app and select open. When a popup shows saying that Serviio is from an unidentified developer, press 'Open'

For more information, see http://support.apple.com/kb/HT5290

@repeters Please can you post step by step instructions for how to get serviio working without dissabling gatekeeper so that zip can update the FAQ as none of us have it in order to test.

Use this as a base, and make it as specific/clear as you can.

Mac OS X 10.8 (Mountain Lion) introduces a new feature called 'Gatekeeper'. When you install Serviio you will have to perform the following steps in order to allow Serviio to run:
1. Control-click on Serviio.app and select open. When a popup shows saying that Serviio is from an unidentified developer, press 'Open'
2. Control-click on Serviio-Console.app and select open. When a popup shows saying that Serviio is from an unidentified developer, press 'Open'

For more information, see http://support.apple.com/kb/HT5290

Unfortunately I get none of the options mentioned in http://support.apple.com/kb/HT5290 that allow me to open the application. The dialog that always appears simply says the following:

"Serviio" is damaged and can't be opened. You should move it to the Trash.

The only buttons are labeled 'Cancel' and 'Move to Trash'.

The only way I have found to open version 1.0 of Serviio and Serviio-Console is to change the Gatekeeper option to 'Anywhere', launch both applications and then set the Gatekeeper option back to 'Mac App store and identified developers'. After that time both applications function as expected. Alas, those steps require the user to have Administrator privileges, which I claim is not a good idea for most users.

We are missing something.

Better yet, the folks at serviio.org should become 'identified developers'.

[zip]

I will sign up for the Developer ID, but want to have something on the FAQ page in the meantime - I've put Will's wording there for now.

I will sign up for the Developer ID, but want to have something on the FAQ page in the meantime - I've put Will's wording there for now.

Sorry I couldn't get the 'easy way' to work. It sounded great. but...

Bob Peters

[will]

Looking on that page again, this is could be the problem (and will really be a problem if serviio becomes reconised):

  Code:

"Damaged" app. – The app has been altered by something other than the developer. This message will appear no matter the Gatekeeper option chosen.


If I understand how things are done on OSX, as soon as a user adds plugins to Serviio.app, or changes console properties in Serviio-Console.app, the OS will block the apps from running full stop.

[zip]

Looking on that page again, this is could be the problem (and will really be a problem if serviio becomes reconised):

  Code:

"Damaged" app. – The app has been altered by something other than the developer. This message will appear no matter the Gatekeeper option chosen.


If I understand how things are done on OSX, as soon as a user adds plugins to Serviio.app, or changes console properties in Serviio-Console.app, the OS will block the apps from running full stop.

Probably yes. There is a ticket to install Serviio on OSX differently (ie use their Application folders, etc). Looks like I'll have to prioritize that a bit now ;-/

Looking on that page again, this is could be the problem (and will really be a problem if serviio becomes reconised):

  Code:

"Damaged" app. – The app has been altered by something other than the developer. This message will appear no matter the Gatekeeper option chosen.


If I understand how things are done on OSX, as soon as a user adds plugins to Serviio.app, or changes console properties in Serviio-Console.app, the OS will block the apps from running full stop.

I've changed a number of items in the Serviio-Colsole.app (added servers, added and deleted items in the Library, changed the language, etc) and both applications continue to work. Temporarily setting the Gatekeeper to accept applications from "anywhere", launching both apps and setting the Gatekeeper setting back to the default value apppears to allow both apps to run even after a restart or power cycle.

[will]

Yes but when gatekeeper is enabled, it identifies the app as damaged, and blocks access. You got it to run by dissabling gatekeeper, and then when you re-enable it, all previous apps are given the OK, it only checks new ones. So even if Serviio became identified, you would still have to dissable gatekeeper in order to get it to run as currently you have to modify it which marks it as damaged. So either way, you have to dissable gatekeep to run it.

Yes but when gatekeeper is enabled, it identifies the app as damaged, and blocks access. You got it to run by dissabling gatekeeper, and then when you re-enable it, all previous apps are given the OK, it only checks new ones. So even if Serviio became identified, you would still have to dissable gatekeeper in order to get it to run as currently you have to modify it which marks it as damaged. So either way, you have to dissable gatekeep to run it.

I appears that I don't fully understand what you mean.

Here is what I did.

(1) disable Gatekeeper
(2) launch the 2 serviio applications
(3) enable Gatekeeper
(4) add a renderer
(5) add local directories to the Library
(6) change the console language
(7) Restart...both apps run
(8) power-cycle...both apps still run

What else can I try?

[will]

Serviio will run for you because once an app has either 1) run while gatekeeper was dissabled/not there, or 2) been allowed through gatekeeper using the method I posted, it will always be allowed to run (unless apple blocks a dev id I think). Therefore, once you get Serviio to run once, it will keep on being allowed to run.

Now one question is, what happens when you install a new version, presumably you have to re-allow it. Which explain the fact that users who upgraded to Serviio 1.0, and then updated to 10.8, where OK, but users how upgraded to 10.8, and then upgraded to Serviio 1.0 were not.

[zip]

So I tried it on a clean 10.8 install (vmware)... Opened Serviio, it told me java is not installed and it installed it automatically, then I just ran the apps as always. I didn't have change the setting to run apps downloaded from anywhere. Not sure if it's because I'm an administrator?