After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759684 - GIMP.app doesn't start for other users due to permission problems
GIMP.app doesn't start for other users due to permission problems
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
2.8.16
Other Mac OS
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
: 761401 761440 762951 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-12-20 03:16 UTC by dfpoon
Modified: 2016-04-01 20:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dfpoon 2015-12-20 03:16:51 UTC
I've GIMP by using homebrew cask on Mac OS 10.11.
$> brew cask install GIMP

It works for the admin account. However, General users (i.e. non-admin users) encountered the following permission problem with GIMP.app.

"LSOpenURLsWithRole() failed with error -10658 for the file /Applications/GIMP.app"
-> GIMP.app cannot be opened.

In the contrast, Administrator has no problem.

Fix: I followed the instruction in this thread:
https://apple.stackexchange.com/questions/81330/downloaded-apps-does-not-start-error-10658

$> sudo chmod a+x /opt/homebrew-cask/Caskroom/gimp/2.8.16-x86_64/GIMP.app/Contents/MacOS/GIMP

Please help to fix the GIMP.app package. Thanks a lot!
Comment 1 Michael Natterer 2015-12-20 12:23:58 UTC
I have no clue how homebrew makes its packages, but a generic "make install"
in gimp installs all executables properly. I suspect this must be a
bug in the homebrew package description for gimp. Did you file a bug against
homebrew too?
Comment 2 Michael Natterer 2015-12-20 12:56:19 UTC
I just realize that you set the prmissions of the launcher script in
order to fix it. This is definitely homebrew's problem.
Comment 3 dfpoon 2015-12-22 03:44:16 UTC
Thanks Michael. I have indeed reported that to homebrew cask project previously. But they consider it is the problem of GIMP package. I will pass your view to there again.
Comment 4 Michael Natterer 2015-12-22 16:25:02 UTC
Can you please ask them if they make the app bundle using their
own scripts, or using the scripts in gimp's build/ source directory?

If they use the latter, it's indeed our bug.
Comment 5 dfpoon 2015-12-23 08:19:40 UTC
I went back to homebrew cask bug report page and the maintainer offered the following response:
https://github.com/caskroom/homebrew-cask/issues/15968#event-496593015

"The mistake there was you referenced doing the installation via a tool, which isn’t at all related to the problem. Please report back in that issue where the developer is wrong:

We’re not homebrew, we’re homebrew-cask. We don’t use make like they’re assuming, we just download their prebuilt package and move the application, nothing else.

Before doing so, though, please uninstall GIMP woth homebrew-cask, download the prebuilt package manually, move it to you /Applications directory youself, and see if your issue persists."

Please see if you could handle it as a GIMP bug for Mac package. I haven't tried installing the GIMP.app manually yet. I may do so if it is absolutely necessary.

------------

For your info, I did previously install gimp-2.8.10 by downloading from the official GIMP download page and had no problem on the permission issue. (but there are other bugs with that version)
Comment 6 Michael Schumacher 2015-12-30 08:55:09 UTC
So, do you experience the same issue if you get the 2.8.16 package from gimp.org?
Comment 7 Max Mustermann 2016-01-17 10:19:39 UTC
The problem is also reported at the GIMP user mailing list (https://mail.gnome.org/archives/gimp-user-list/2016-January/msg00034.html). I could reproduce it with GIMP 2.8.16 and got the error 'LSOpenURLsWithRole() failed with error -10810'.
I could fix it by opening a Terminal session, then executing
sudo chmod 755 /Applications/GIMP.app/Contents/MacOS/*

We should set these file permissions properly on packaging.
Comment 8 Max Mustermann 2016-01-17 10:21:26 UTC
Addition: please note that we build GIMP with JHBuild and some of us use Macports. You might have more luck if used one of them for building instead of Homebrew.
Comment 9 Michael Natterer 2016-02-01 16:28:40 UTC
*** Bug 761401 has been marked as a duplicate of this bug. ***
Comment 10 Michael Schumacher 2016-02-02 09:58:51 UTC
*** Bug 761440 has been marked as a duplicate of this bug. ***
Comment 11 Kristian Rietveld 2016-02-10 12:30:42 UTC
Note to self: I need to check the permissions are right in the DMG we package. If I remember correctly I do set the permissions such that the bundle can be read by everyone, but will double check.
Comment 12 Michael Schumacher 2016-03-01 22:25:31 UTC
*** Bug 762951 has been marked as a duplicate of this bug. ***
Comment 13 Kristian Rietveld 2016-04-01 20:09:30 UTC
Ok, the problem with our gimp.org DMG was most likely:

-rwxr--r--  1 kris  staff     2920 Dec 13 21:21 GIMP


I've have fixed the permissions of this file now and uploaded a new DMG image to the FTP server:  gimp-2.8.16-x86_64-1.dmg