Re: XQuartz fails to Launch or Reinstall
Hi Wendy, Run `/bin/ls -Old /private/tmp` I suspect you'll see that "restricted" is set on /private/tmp. If so, you're likely seeing the same issue as impacting users of Xcode, mysqld, and other tools that make use of /tmp. You can see my answer on http://stackoverflow.com/questions/40238266/launchd-sim-crashing-could-not-create-temporary-state-directory for a bit more detail, but the easiest fix right now is to boot into recovery mode and run: chflags norestricted /Volumes/.../private/tmp (with the "..." obviously replaced with the name of your root volume). --Jeremy > On Oct 7, 2016, at 14:10, Wendy M Calvin wrote: > > I am running El Capitain OSX 10.11.6 on a Mac Pro > > I recently performed the update and now XQuartz fails to start with the error > "Could not create lock file in /tmp/.tX0-lock > " > > I have tried to download and reinstall XQuartz-2.7.9 but the install fails > with no information other than the install “encountered an error that caused > the installation to fail. Contact the software manufacturer for assistance”. > > I have reviewed on line suggestions and the symbolic links for /tmp and > /private/tmp seem to be ok and I can not mv the /tmp directory to recreate > the link. There is no existing .tX0-lock file > > The detailed crash report is below my signature. > > Any assistance greatly appreciated. I run several software packages that > rely on the X11 environment. > > __ > Wendy M Calvin > Professor and Chair, Geological Sciences > http://www.unr.edu/geology/ > University of Nevada, Reno 775-784-1785 wcal...@unr.edu > __ > > > Process: X11.bin [2001] > Path: > /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin > Identifier:org.macosforge.xquartz.X11 > Version: 2.7.9 (2.7.94) > Code Type: X86-64 (Native) > Parent Process:??? [1] > Responsible: X11.bin [2001] > User ID: 501 > > Date/Time: 2016-10-07 14:02:16.871 -0700 > OS Version:Mac OS X 10.11.6 (15G1004) > Report Version:11 > Anonymous UUID:1DA5C109-FA76-1D84-F453-2D8905A04B4E > > > Time Awake Since Boot: 1600 seconds > > System Integrity Protection: enabled > > Crashed Thread:2 > > Exception Type:EXC_CRASH (SIGABRT) > Exception Codes: 0x, 0x > Exception Note:EXC_CORPSE_NOTIFY > > Application Specific Information: > X.Org X Server 1.17.4 Build Date: 20160505 > Could not create lock file in /tmp/.tX0-lock > > abort() called > > Thread 0:: Dispatch queue: com.apple.main-thread > 0 libsystem_kernel.dylib > 0x7fff8f905fae semaphore_wait_trap + 10 > 1 libdispatch.dylib > 0x7fff930e1cb2 _dispatch_semaphore_wait_slow + 224 > 2 libxpc.dylib > 0x7fff8b075ba9 xpc_connection_send_message_with_reply_sync + 218 > 3 com.apple.LaunchServices > 0x7fff983512bf _LSSetApplicationInformation + 270 > 4 com.apple.LaunchServices > 0x7fff98362742 _LSSetApplicationInformationItem + 98 > 5 com.apple.AppKit > 0x7fff9c5f23d4 __85-[NSApplication(NSAppssassination) > _setNeedsUpdateToReflectAutomaticTerminationState]_block_invoke + 584 > 6 com.apple.CoreFoundation > 0x7fff8b4134ac __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 > 7 com.apple.CoreFoundation > 0x7fff8b3f2d05 __CFRunLoopDoBlocks + 341 > 8 com.apple.CoreFoundation > 0x7fff8b3f2a6b __CFRunLoopRun + 2347 > 9 com.apple.CoreFoundation > 0x7fff8b3f1ed8 CFRunLoopRunSpecific + 296 > 10 com.apple.HIToolbox > 0x7fff902de935 RunCurrentEventLoopInMode + 235 > 11 com.apple.HIToolbox > 0x7fff902de76f ReceiveNextEventCommon + 432 > 12 com.apple.HIToolbox > 0x7fff902de5af _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 13 com.apple.AppKit > 0x7fff9c49bdf6 _DPSNextEvent + 1067 > 14 com.apple.AppKit > 0x7fff9c49b226 -[NSApplication > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 > 15 com.apple.AppKit > 0x7fff9c48fd80 -[NSApplication run] + 682 > 16 X11.bin > 0x000194f9 X11ApplicationMain + 1576 > 17 X11.bin > 0x000100011b45 server_main + 185 > 18 X11.bin > 0x00012835 do_start_x11_server + 283 > 19 X11.bin > 0x000135b5 _Xstart_x11_server + 122 > 20 X11.bin > 0x00013714 mach_startup_server + 78 > 21 libsystem_kernel.dylib > 0x7fff8f905ce0 mach_msg_server + 504 > 22 X11.bin > 0x00012f9d main + 1849 > 23 X11.bin > 0x000122c4 start + 52 > > Thread 1:: Dispatch queue: com.apple.libdispa
Re: XQuartz fails to Launch or Reinstall
On Mon, Oct 10, 2016 at 11:57:04PM -0700, Jeremy Huddleston Sequoia wrote: Apple didn't do that. The user did. We ship with /tmp as a symlink to /private/tmp with correct permissions. Ok, sorry. Maybe you should consider chattr'ing some things against your users ;-) (I mean, it's odd that ppl. manage to constrain permissions and otoh fail to understand what they do. They'll have required root privs itfp *shrug*) Cheers, Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: XQuartz fails to Launch or Reinstall
On Tue, Oct 11, 2016 at 02:12:18AM +, Wendy M Calvin wrote: Thanks for your response. I get touch: /tmp/.tX0-lock: Operation not permitted I get the same error “Operation not permitted” if I try to mv the /tmp directory to something like tmp_old in order to recreate the link. According to https://discussions.apple.com/thread/482205?start=0&tstart=0 /tmp is now 755, root:wheel what means only root can write there. You could add yourself to wheel and make it 775, but I'm not sure why apple chose those (idiotic) permissions and it's likely not a persistent change (reg. the /tmp permissions, group assignments should be fine) Cheers, Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: XQuartz fails to Launch or Reinstall
Then why can't you create /tmp/.tX0-lock? Does it already exist? > On Oct 11, 2016, at 11:35, Wendy M Calvin wrote: > > The permissions appear to be correctly set and it does link to /private/tmp > > ptychodus:/ wcalvin$ ls -ld /tmp > lrwxr-xr-x@ 1 root wheel 11 Jan 30 2016 /tmp -> private/tmp > ptychodus:/ wcalvin$ ls -ld /private/tmp/ > drwxrwxrwt@ 3 root wheel 102 Oct 7 13:33 /private/tmp/ > __ > Wendy M Calvin > Professor and Chair, Geological Sciences > http://www.unr.edu/geology/ > University of Nevada, Reno 775-784-1785 wcal...@unr.edu > __ > > > From: on behalf of Jeremy Huddleston Sequoia > > Date: Monday, October 10, 2016 at 11:50 PM > To: Wendy Calvin > Cc: "x...@freedesktop.org" > Subject: Re: XQuartz fails to Launch or Reinstall > > >> On Oct 10, 2016, at 19:12, Wendy M Calvin wrote: >> Thanks for your response. >> I get >> touch: /tmp/.tX0-lock: Operation not permitted >> I get the same error “Operation not permitted” if I try to mv the /tmp >> directory to something like tmp_old in order to recreate the link. > > So then it seems like you messed up your permissions. Assuming /tmp is a > symlink to /private/tmp like it should be, you should fix the permissions on > /private/tmp (sudo chmod 1777 /private/tmp). > > --Jeremy > > >> __ >> Wendy M Calvin >> Professor and Chair, Geological Sciences >> http://www.unr.edu/geology/ >> University of Nevada, Reno 775-784-1785 wcal...@unr.edu >> ______________ >> From: on behalf of Jeremy Huddleston Sequoia >> >> Date: Monday, October 10, 2016 at 7:06 PM >> To: Wendy Calvin >> Cc: "x...@freedesktop.org" >> Subject: Re: XQuartz fails to Launch or Reinstall >> You should try to figure out why you can't create /tmp/.tX0-lock. What >> happens if you 'touch /tmp/.tX0-lock'? >>> On Oct 7, 2016, at 14:10, Wendy M Calvin wrote: >>> I am running El Capitain OSX 10.11.6 on a Mac Pro >>> I recently performed the update and now XQuartz fails to start with the >>> error "Could not create lock file in /tmp/.tX0-lock >>> " >>> I have tried to download and reinstall XQuartz-2.7.9 but the install fails >>> with no information other than the install “encountered an error that >>> caused the installation to fail. Contact the software manufacturer for >>> assistance”. >>> I have reviewed on line suggestions and the symbolic links for /tmp and >>> /private/tmp seem to be ok and I can not mv the /tmp directory to recreate >>> the link. There is no existing .tX0-lock file >>> The detailed crash report is below my signature. >>> Any assistance greatly appreciated. I run several software packages that >>> rely on the X11 environment. >>> __ >>> Wendy M Calvin >>> Professor and Chair, Geological Sciences >>> http://www.unr.edu/geology/ >>> University of Nevada, Reno 775-784-1785 wcal...@unr.edu >>> __ >>> Process: X11.bin [2001] >>> Path: >>> /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin >>> Identifier:org.macosforge.xquartz.X11 >>> Version: 2.7.9 (2.7.94) >>> Code Type: X86-64 (Native) >>> Parent Process:??? [1] >>> Responsible: X11.bin [2001] >>> User ID: 501 >>> Date/Time: 2016-10-07 14:02:16.871 -0700 >>> OS Version:Mac OS X 10.11.6 (15G1004) >>> Report Version:11 >>> Anonymous UUID:1DA5C109-FA76-1D84-F453-2D8905A04B4E >>> Time Awake Since Boot: 1600 seconds >>> System Integrity Protection: enabled >>> Crashed Thread:2 >>> Exception Type:EXC_CRASH (SIGABRT) >>> Exception Codes: 0x, 0x >>> Exception Note:EXC_CORPSE_NOTIFY >>> Application Specific Information: >>> X.Org X Server 1.17.4 Build Date: 20160505 >>> Could not create lock file in /tmp/.tX0-lock >>> >>> abort() called >>> Thread 0:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib >>> 0x7fff8f905fae semaphore_wait_trap + 10 >>> 1 libdispatch.dylib >>> 0x7fff930e1
Re: XQuartz fails to Launch or Reinstall
> On Oct 10, 2016, at 23:50, Thomas Lübking wrote: > > On Tue, Oct 11, 2016 at 02:12:18AM +, Wendy M Calvin wrote: >> Thanks for your response. >> >> I get >> >> touch: /tmp/.tX0-lock: Operation not permitted >> >> >> I get the same error “Operation not permitted” if I try to mv the /tmp >> directory to something like tmp_old in order to recreate the link. > > According to > https://discussions.apple.com/thread/482205?start=0&tstart=0 /tmp is now > 755, root:wheel what means only root can write there. > You could add yourself to wheel and make it 775, but I'm not sure why > apple chose those (idiotic) permissions and it's likely not a persistent > change (reg. the /tmp permissions, group assignments should be fine) Apple didn't do that. The user did. We ship with /tmp as a symlink to /private/tmp with correct permissions. smime.p7s Description: S/MIME cryptographic signature ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: XQuartz fails to Launch or Reinstall
> On Oct 10, 2016, at 19:12, Wendy M Calvin wrote: > > Thanks for your response. > > I get > touch: /tmp/.tX0-lock: Operation not permitted > > I get the same error “Operation not permitted” if I try to mv the /tmp > directory to something like tmp_old in order to recreate the link. So then it seems like you messed up your permissions. Assuming /tmp is a symlink to /private/tmp like it should be, you should fix the permissions on /private/tmp (sudo chmod 1777 /private/tmp). --Jeremy > > __ > Wendy M Calvin > Professor and Chair, Geological Sciences > http://www.unr.edu/geology/ > University of Nevada, Reno 775-784-1785 wcal...@unr.edu > __ > > > From: on behalf of Jeremy Huddleston Sequoia > > Date: Monday, October 10, 2016 at 7:06 PM > To: Wendy Calvin > Cc: "x...@freedesktop.org" > Subject: Re: XQuartz fails to Launch or Reinstall > > You should try to figure out why you can't create /tmp/.tX0-lock. What > happens if you 'touch /tmp/.tX0-lock'? > > >> On Oct 7, 2016, at 14:10, Wendy M Calvin wrote: >> I am running El Capitain OSX 10.11.6 on a Mac Pro >> I recently performed the update and now XQuartz fails to start with the >> error "Could not create lock file in /tmp/.tX0-lock >> " >> I have tried to download and reinstall XQuartz-2.7.9 but the install fails >> with no information other than the install “encountered an error that caused >> the installation to fail. Contact the software manufacturer for assistance”. >> I have reviewed on line suggestions and the symbolic links for /tmp and >> /private/tmp seem to be ok and I can not mv the /tmp directory to recreate >> the link. There is no existing .tX0-lock file >> The detailed crash report is below my signature. >> Any assistance greatly appreciated. I run several software packages that >> rely on the X11 environment. >> __ >> Wendy M Calvin >> Professor and Chair, Geological Sciences >> http://www.unr.edu/geology/ >> University of Nevada, Reno 775-784-1785 wcal...@unr.edu >> __ >> Process: X11.bin [2001] >> Path: >> /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin >> Identifier:org.macosforge.xquartz.X11 >> Version: 2.7.9 (2.7.94) >> Code Type: X86-64 (Native) >> Parent Process:??? [1] >> Responsible: X11.bin [2001] >> User ID: 501 >> Date/Time: 2016-10-07 14:02:16.871 -0700 >> OS Version:Mac OS X 10.11.6 (15G1004) >> Report Version:11 >> Anonymous UUID:1DA5C109-FA76-1D84-F453-2D8905A04B4E >> Time Awake Since Boot: 1600 seconds >> System Integrity Protection: enabled >> Crashed Thread:2 >> Exception Type:EXC_CRASH (SIGABRT) >> Exception Codes: 0x, 0x >> Exception Note:EXC_CORPSE_NOTIFY >> Application Specific Information: >> X.Org X Server 1.17.4 Build Date: 20160505 >> Could not create lock file in /tmp/.tX0-lock >> >> abort() called >> Thread 0:: Dispatch queue: com.apple.main-thread >> 0 libsystem_kernel.dylib >> 0x7fff8f905fae semaphore_wait_trap + 10 >> 1 libdispatch.dylib >> 0x7fff930e1cb2 _dispatch_semaphore_wait_slow + 224 >> 2 libxpc.dylib >> 0x7fff8b075ba9 xpc_connection_send_message_with_reply_sync + 218 >> 3 com.apple.LaunchServices >> 0x7fff983512bf _LSSetApplicationInformation + 270 >> 4 com.apple.LaunchServices >> 0x7fff98362742 _LSSetApplicationInformationItem + 98 >> 5 com.apple.AppKit >> 0x7fff9c5f23d4 __85-[NSApplication(NSAppssassination) >> _setNeedsUpdateToReflectAutomaticTerminationState]_block_invoke + 584 >> 6 com.apple.CoreFoundation >> 0x7fff8b4134ac __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 >> 7 com.apple.CoreFoundation >> 0x7fff8b3f2d05 __CFRunLoopDoBlocks + 341 >> 8 com.apple.CoreFoundation >> 0x7fff8b3f2a6b __CFRunLoopRun + 2347 >> 9 com.apple.CoreFoundation >> 0x7fff8b3f1ed8 CFRunLoopRunSpecific + 296 >> 10 com.apple.HIToolbox >> 0x7fff902de935 RunCurrentEventLoopInMode + 235 >> 11 com.apple.HIToolbox >> 0x7fff902de76f ReceiveNextEventCommon + 432 >> 12 com.apple.HIToolbox
Re: XQuartz fails to Launch or Reinstall
You should try to figure out why you can't create /tmp/.tX0-lock. What happens if you 'touch /tmp/.tX0-lock'? > On Oct 7, 2016, at 14:10, Wendy M Calvin wrote: > > I am running El Capitain OSX 10.11.6 on a Mac Pro > > I recently performed the update and now XQuartz fails to start with the error > "Could not create lock file in /tmp/.tX0-lock > " > > I have tried to download and reinstall XQuartz-2.7.9 but the install fails > with no information other than the install “encountered an error that caused > the installation to fail. Contact the software manufacturer for assistance”. > > I have reviewed on line suggestions and the symbolic links for /tmp and > /private/tmp seem to be ok and I can not mv the /tmp directory to recreate > the link. There is no existing .tX0-lock file > > The detailed crash report is below my signature. > > Any assistance greatly appreciated. I run several software packages that > rely on the X11 environment. > > __ > Wendy M Calvin > Professor and Chair, Geological Sciences > http://www.unr.edu/geology/ > University of Nevada, Reno 775-784-1785 wcal...@unr.edu > __ > > > Process: X11.bin [2001] > Path: > /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin > Identifier:org.macosforge.xquartz.X11 > Version: 2.7.9 (2.7.94) > Code Type: X86-64 (Native) > Parent Process:??? [1] > Responsible: X11.bin [2001] > User ID: 501 > > Date/Time: 2016-10-07 14:02:16.871 -0700 > OS Version:Mac OS X 10.11.6 (15G1004) > Report Version:11 > Anonymous UUID:1DA5C109-FA76-1D84-F453-2D8905A04B4E > > > Time Awake Since Boot: 1600 seconds > > System Integrity Protection: enabled > > Crashed Thread:2 > > Exception Type:EXC_CRASH (SIGABRT) > Exception Codes: 0x, 0x > Exception Note:EXC_CORPSE_NOTIFY > > Application Specific Information: > X.Org X Server 1.17.4 Build Date: 20160505 > Could not create lock file in /tmp/.tX0-lock > > abort() called > > Thread 0:: Dispatch queue: com.apple.main-thread > 0 libsystem_kernel.dylib > 0x7fff8f905fae semaphore_wait_trap + 10 > 1 libdispatch.dylib > 0x7fff930e1cb2 _dispatch_semaphore_wait_slow + 224 > 2 libxpc.dylib > 0x7fff8b075ba9 xpc_connection_send_message_with_reply_sync + 218 > 3 com.apple.LaunchServices > 0x7fff983512bf _LSSetApplicationInformation + 270 > 4 com.apple.LaunchServices > 0x7fff98362742 _LSSetApplicationInformationItem + 98 > 5 com.apple.AppKit > 0x7fff9c5f23d4 __85-[NSApplication(NSAppssassination) > _setNeedsUpdateToReflectAutomaticTerminationState]_block_invoke + 584 > 6 com.apple.CoreFoundation > 0x7fff8b4134ac __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 > 7 com.apple.CoreFoundation > 0x7fff8b3f2d05 __CFRunLoopDoBlocks + 341 > 8 com.apple.CoreFoundation > 0x7fff8b3f2a6b __CFRunLoopRun + 2347 > 9 com.apple.CoreFoundation > 0x7fff8b3f1ed8 CFRunLoopRunSpecific + 296 > 10 com.apple.HIToolbox > 0x7fff902de935 RunCurrentEventLoopInMode + 235 > 11 com.apple.HIToolbox > 0x7fff902de76f ReceiveNextEventCommon + 432 > 12 com.apple.HIToolbox > 0x7fff902de5af _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 13 com.apple.AppKit > 0x7fff9c49bdf6 _DPSNextEvent + 1067 > 14 com.apple.AppKit > 0x7fff9c49b226 -[NSApplication > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 > 15 com.apple.AppKit > 0x7fff9c48fd80 -[NSApplication run] + 682 > 16 X11.bin > 0x000194f9 X11ApplicationMain + 1576 > 17 X11.bin > 0x000100011b45 server_main + 185 > 18 X11.bin > 0x00012835 do_start_x11_server + 283 > 19 X11.bin > 0x000135b5 _Xstart_x11_server + 122 > 20 X11.bin > 0x00013714 mach_startup_server + 78 > 21 libsystem_kernel.dylib > 0x7fff8f905ce0 mach_msg_server + 504 > 22 X11.bin > 0x00012f9d main + 1849 > 23 X11.bin > 0x000122c4 start + 52 > > Thread 1:: Dispatch queue: com.apple.libdispatch-manager > 0 libsystem_kernel.dylib > 0x7fff8f90cefa kevent_qos + 10 > 1 libdispatch.dylib > 0x7fff930dc165 _dispatch_mgr_invoke + 216 > 2 libdispatch.dylib > 0x7fff930dbdcd _dispatch_mgr_thread + 52 > > Thread 2 Crashed: > 0 libsystem_kernel.dylib > 0x7fff8f90bf06 __pthread_kill + 10 > 1 libsystem_pthread.dylib > 0x7fff95d124ec pthread_kill + 90 > 2 libsystem_c.dylib > 0x00
