Switch branches/tags
Nothing to show
Find file
Fetching contributors…
Cannot retrieve contributors at this time
173 lines (87 sloc) 5.79 KB
original_url created_at updated_at status type reporter owner priority milestone component version keywords cc
2010-08-27 17:41:08 -0700
2015-10-23 10:27:18 -0700
2.5.3 (xserver-1.8.2)

Won't start when a user is managed (Parental Controls)

When a user account is managed, XQuartz won't start up!


  1. XQuartz is enabled (checked) in the "parental controls" pane of a student user's Accounts Preferences window.
  1. A dialog is displayed when XQuartz is started where an admin user should be able to override the "parental controls" but the override fails!

I need to use X11 in a student iMac lab and must enable "parental controls" to manage student user accounts.

The iMacs are running Snow Leopard 10.6.4 and are "new" (installed summer 2010).

Adam Hausknecht Department of Mathematics, UMass Dartmouth

jeremyhu@… commented on Aug 27, 2010

What happens? See anything in /var/log/system.log?

jeremyhu@… commented on May 19, 2011

  • Status changed from new to closed
  • Resolution changed from to invalid

No information provided. Closing.

adamaig@… commented on May 20, 2011

  • Status changed from closed to reopened
  • Resolution invalid deleted

Funny that you just closed this, because I just ran into the issue yesterday at a school I'm working with.

Here is the console output you need.

5/20/11 1:46:28 PM [0x0-0x7ed7ed].org.macosforge.xquartz.X11[86146]    -: /Applications/Utilities/ Permission denied
5/20/11 1:46:28 PM  [0x0-0x7ed7ed].org.macosforge.xquartz.X11[86146]    -: /Applications/Utilities/ Unknown error: 0
5/20/11 1:46:28 PM[86068]    ([0x0-0x7ed7ed].org.macosforge.xquartz.X11[86146]) Exited with exit code: 1

To test I just created a new account, "student", applied parental controls, but allow XQuartz and X11 as applications. When I start XQuartz I'm asked to authenticate if I want to [Always Allow] [Allow Once] [Cancel]. I try authenticating with my admin password, but that fails.

jeremyhu@… commented on May 20, 2011

  • Cc adamaig@… added

jeremyhu@… commented on May 20, 2011

  • Milestone set to 2.7.0

jeremyhu@… commented on May 20, 2011

  • Status changed from reopened to new
  • Priority changed from Not Set to Important
  • Component changed from X11.pkg to xserver
  • Milestone changed from 2.7.0 to OSX

I suspect this is an issue in OSX, but hopefully I'll be able to find a workaround.


siva.dirisala@… commented on Aug 19, 2012

  • Cc siva.dirisala@… added

siva.dirisala@… commented on Aug 19, 2012

I have the same problem with OSX 10.8 and XQuartz 2.7.2 (xorg-server 1.12.2).

mike@… commented on Aug 22, 2012

Same problem here. I am running 10.8 with XQuartz 2.7.2. Of interest, if I select the "allow once" option, it seems to work fine. If I select the "allow always" option, the authorization fails and it sends you back to the original authorization prompt.

If anyone finds a work-around, I would be very interested in it.


mike@… commented on Aug 22, 2012

  • Cc mike@… added

siva.dirisala@… commented on Aug 23, 2012

Thanks Mike. Using "allow once" worked for me as well, though it asks for permissions for other apps. Only the X11 app needs "allow once" and all others can be "allow always".

jeremyhu@… commented on Oct 23, 2015

Mass Edit

As you may have noticed, we have had issues with spam in trac for the past couple years. We've decided to migrate to using's bugzilla for our bug tracker (more details will be coming on the mailing lists in the next couple weeks).

I don't want us to loose valuable bug reports in the transition, so I want to make sure that any relevant open issues in this MacOSForge trac are migrated over to the new system. If you are interested in this issue, please take a few minutes to file a new bug for this issue in bugzilla. Please make sure to do the following:

  • Copy over all relevant information into that report, just in case we loose this one.
  • Set the URL field of the bugzilla report to this trac ticket's URL.
  • Paste the URL of the new bugzilla report as a comment in this ticket, and I'll close it out.