All of a Sudden, I can't launch any programs

Fahrvergnuugen

Fahrvergnuugen

I am the law!
I'm using OSX 10.1.2 on a Dual 500MHz G4 w/ 1.2 GB of RAM.

I never shut my computer down unless I'm forced to....and lately I've had to shut down a lot [sometimes using the power button].

Everything will be running fine for days on end, then all of a sudden, I'll try and launch an ap [any ap] and it won't launch. The icon will just bounce in the finder for a while, then eventually stop but the ap will never launch.

If I quit an ap that I'm currently running and try and relaunch it, the same thing happens. This INCLUDES the finder. Once or twice I've had to "relaunch" the finder and it won't come back. It'll just bounce until it gives up. As you might have guessed, when that happens, the system goes down hard. A lot of the time, when this sort of thing happens, I can't even telnet in to shut the system down.

I've also noticed that when I do shut down, it takes FOREVER [over a minute].

Anybody know what might be wrong?
 
well i have had this happen twice now. both fairly recently. at least the last time it happened i can identify that i was running spring cleaning and it was performing a task that must take hours or else just funks things up. hitting restart button cured it. it takes so long to reboot after this because disk repair has to be done before you can load.:(
 
I had the same problem but its gone now. I ran the console to see if there was an error I could at least report here and it seemed to be and application I was running (Fire .29) was returning a null or something. I forget exactly how it was worded but I downloaded a different chat client (Adium) and I have had no problems since. This all occured sunday and monday of this week so 2 days ago.
 
Ok, obviously you can't launch the app in /Applications/Utilities called console.app.

however, if you see this happening, try this:
Log out. Log in as ">console" (without the quotes). the computer will not ask for a password, and you will be droped into aqua-less (dry? heh) Darwin. There you will see a login prompt. Log in using the short name assigned to you in the Login plane of System Preferences (its also the name of your home directory). Use your password as usuall.

Next, you get a shell prompt. type:
cat /var/log/system.log | more
(the | is a 'pipe' and its made by pressing shift and that key right above the return key on mac keyboards). You'll see all the errors your computer has reported lately. Press space to see the next page (return to see it line-by line). Press q to quit.

And type exit to be returned to normal aqua land :p

Please post anything from these logs - I'm almost posative you will find your answer within them.
 
I don't know if it is related to your problem but I have been experiencing the same thing after - or while, running the Installer.app..

A simple reboot solves it for me though..
 
Hi,

Had the same thing happen to me after upgrading to 10.1.2. It happened every time that I changed my NW settings. I had to basically delete all of the NW settings and re-create them. Since then its all been fine. The only time I had probs after that is when I tried to assign the en0 interface (built in ethernet on my iBook) the same IP as the loopback.

This problem was repeatable, as was the cure.

Don't know if any of you have been switching your NW locations in Settings?? Perhaps the same "bug" also extends to other properties?

Anyway, hope the above can be of help to some ;-)

C
 
Dude.... you set an interface to 127.0.0.1? I think thats your prob!

There are some services which work only internally (like WindowServer, I think). When apps try and latch on to the window server, they might make an internal UNIX connection (see netstat). I think this is called rpc (see netinfo).

Anyway, try just setting a manual address to the interface, like 192.168.1.1

Or, just disable it
sudo ifconfig en0 down
 
You must log in or register to reply here.
Back
Top