www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - [OT] Faulty Java update for OS X (10.8)?

reply "Chris" <wendlec tcd.ie> writes:
I installed the latest Java update for Mac last Tuesday (7u45). 
When I shut down the Mac, I noticed that it took ages (several 
minutes), then today (didn't use it on Wednesday) it wouldn't 
boot. All it showed me was a white screen. I tried all the 
recommended remedies, but nothing would help. I finally restored 
it from a Time Machine backup that was pre Java 7u45. Now the Mac 
works again.

I wonder if it was the Java update or something else. I 
downloaded it from 
http://java.com/en/download/mac_download.jsp?locale=en.

My system is 10.8.4
Oct 24 2013
next sibling parent Jacob Carlborg <doob me.com> writes:
On 2013-10-24 23:39, Chris wrote:
 I installed the latest Java update for Mac last Tuesday (7u45). When I
 shut down the Mac, I noticed that it took ages (several minutes), then
 today (didn't use it on Wednesday) it wouldn't boot. All it showed me
 was a white screen. I tried all the recommended remedies, but nothing
 would help. I finally restored it from a Time Machine backup that was
 pre Java 7u45. Now the Mac works again.

 I wonder if it was the Java update or something else. I downloaded it
 from http://java.com/en/download/mac_download.jsp?locale=en.

 My system is 10.8.4
If you boot your computer and hold down Command-V it will boot in verbose mode. This let you see what's going on and possibly what's actually causing the problem. You can also boot in single-user mode. This will get you a minimal shell environment allowing you to fix the problem, like remove files causing the problems. http://support.apple.com/kb/ht1492 -- /Jacob Carlborg
Oct 24 2013
prev sibling parent reply "Kagamin" <spam here.lot> writes:
Install it again and see.
Oct 24 2013
parent reply "Chris" <wendlec tcd.ie> writes:
On Friday, 25 October 2013 at 06:54:32 UTC, Kagamin wrote:
 Install it again and see.
Thanks. I had already tried all of the above. Disk utility, single user mode (with fcsk -fy etc), safe mode or whatever, you name it. I had to restore it from my Time Machine backup and it works fine (only lost a few files I had backed up elsewhere anyway). All I know is that it happened after the Java update 7u45.
Oct 25 2013
parent reply Jacob Carlborg <doob me.com> writes:
On 2013-10-25 10:36, Chris wrote:
 On Friday, 25 October 2013 at 06:54:32 UTC, Kagamin wrote:
 Install it again and see.
Thanks. I had already tried all of the above. Disk utility, single user mode (with fcsk -fy etc), safe mode or whatever, you name it. I had to restore it from my Time Machine backup and it works fine (only lost a few files I had backed up elsewhere anyway). All I know is that it happened after the Java update 7u45.
What did the verbose mode say? -- /Jacob Carlborg
Oct 25 2013
parent reply "Chris" <wendlec tcd.ie> writes:
On Friday, 25 October 2013 at 12:40:10 UTC, Jacob Carlborg wrote:
 On 2013-10-25 10:36, Chris wrote:
 On Friday, 25 October 2013 at 06:54:32 UTC, Kagamin wrote:
 Install it again and see.
Thanks. I had already tried all of the above. Disk utility, single user mode (with fcsk -fy etc), safe mode or whatever, you name it. I had to restore it from my Time Machine backup and it works fine (only lost a few files I had backed up elsewhere anyway). All I know is that it happened after the Java update 7u45.
What did the verbose mode say?
Once it said in single user mode. HD seems to be ok. HD has been changed. I ran fcsk -fy again (as recommended) and it was fine. Disk Utility also said it was fine. I cannot think of anything else that could've wrecked my Mac, except for the Java update.
Oct 25 2013
parent Jacob Carlborg <doob me.com> writes:
On 2013-10-25 15:38, Chris wrote:

 Once it said in single user mode.

 HD seems to be ok.
 HD has been changed.

 I ran fcsk -fy again (as recommended) and it was fine. Disk Utility also
 said it was fine.

 I cannot think of anything else that could've wrecked my Mac, except for
 the Java update.
If you want to be able to solve this you need to read the output of the verbose mode. The last output might be available in some log file, somewhere. -- /Jacob Carlborg
Oct 26 2013