PixInsight > Bug Reports

Mac OS X 64 bit updater no-install loop

(1/10) > >>

JMc:
Mac OS X.6.6
Pixinsight V1.07.00.0697 Starbuck (x86_64)

On startup, Pixinsight tells me I have ten updates available. I enable the updates, close the application, and then I see a dialog that asks if I want to install updates (the restart application box is checked). I click yes, and nothing happens.

When I restart the program, this loop repeats. Why won't the updates install on exit? I am the sole user on this machine and have admin privileges.

Juan Conejero:
Hi,

I haven't seen anything similar to this before. As far as I can tell, the update system works perfectly on Mac OS X.

Anybody can confirm this problem? Anybody can figure out the cause of this?

JMc:
Rebooted the system and the same loop repeats:

On starting Pixinsight I have a dialog that announces updates, click the box and they download:

Packages downloaded:
  10 successful
   0 failed
Downloaded packages are now scheduled for installation.
The updates will be installed when you exit this instance of the PixInsight Core application.
Should you need to cancel the scheduled update, you can do so by selecting Resources > Update > Unschedule Update Installation.

I click APPLY and exit PixInsight (Dialog box):

Update packages have been scheduled for installation. Do you want to install the updates now?  (restart Pixinsight box is checked)

I click yes ... nothing happens. PI does not restart automatically, the updates are not applied. Should I reinstall PI? Is there a library or pref file that needs deletion?

Can I get a link to re-download the latest version of PI and skip this FUBAR update process?

pfile:
is PI crashing before the installer starts? i have seen that often times the x86-64 version crashes on exit. if there was an update pending at that time it does not happen. when PI starts up again it wants to download the updates again, but i suspect they are still hanging around in whatever temp directory they were put in.

can the installer be invoked by the user somehow? is it inside the PI application bundle somewhere? if so "open -a /path/to/updater.app" might work after a PI crash on exit.

AstroGabe:
I'm having the same situation.  Any progress on this?

Navigation

[0] Message Index

[#] Next page