Major Problem with MacOSX.Com IRC Chat Client

S

Sogni

*gone*
Hey I just noticed a pretty BAD problem that was caused by the chat client!!!

I launch terminal and this is what I see:

Code: 
Last login: Sun Jan  5 22:07:06 on ttyp1
/Volumes/MacOSX.com\ Chat\ 1/installer.command; exWelcome to Darwin!
it
[DualG4:~] sogni% /Volumes/MacOSX.com\ Chat\ 1/installer.command; exit
/Volumes/MacOSX.com Chat 1/installer.command: Command not found.
logout
[Process completed]
And terminal session ends...

I can't use Terminal at all now!

HELP!
 
Ok I'm able to temporarily stop it by pressing Control C key combo and have access to the terminal if I enter the key combo in time before the script finishes...

Where is this code written that causes it to auto-start when a new terminal session is started? It has to be a startup file for terminal - I've just never used them so I don't know where to look. So far I've turned up nothing.

This is not good! I have removed all traces of the macosx.com irc chat client from my systems completly (and never using it again!!!) and still have this problem!

Thank god it wasn't a more damaging command it executed - or else I would have been a LOT more mad than I am now!
 
BTW, The problem is only isolated to my user account - I loged in with another user account, launched terminal, and the problem is NOT there... Thank god!

But I still can't figure out how to fix it on my useraccount...
 
well, and no one else has been able to replicate this yet. what else were you playing around with at the time?

also, please keep in mind that we did declare this beta and that finding any bugs and fixing them is one of our goals. if you look in the programming forum, you will see Captain Code's thread looking for others to participate in this project. it would be great if our site members were to help make this the best little dedicated client on the 'net.

oh, and our goal in getting it out now is so that people who don't have much irc experience can easily connect - especially during MWSF, from the keynote on. i would expect our terminal jockeys to be able to manage this with any client. :)
 
That's what I was thinking - that maybe it was just me... but, why?

Maybe because I didn't completly uninstall the previous version? Maybe the installer barfed on my machine?

I realize it was Beta, but I never expected it to cripple any part of my computer - which is the part that pissed me off. :p

Can't people just drag the app and requiered folder themselves? It seems so silly to user that terminal script.

Anyway, I'm sure the script put itself into a startup file so it runs when a terminal session is opened - but where the heck is that file?

BTW, here's the error in action on my machine:
http://www.dtechnoart.com/~sogni/temp/TerminalProblem.mov
(628 KBs)
 
FIXED!!!

This is what I did...

Edited this file in Pico:
~/Library/Preferences/com.apple.Terminal.plist

and removed these two lines:
<key>ExecutionString</key>
<string>/Volumes/MacOSX.com\ Chat\ 1/installer.command; exit</string>

Saved it, and opened a new Terminal Window
Code: 
Last login: Mon Jan  6 05:37:41 on ttyp3
Welcome to Darwin!
[DualG4:~] sogni%

Yay! :)
 
coool, and yes, you can manually move the macidentification.framework file with no problem. that's what i've been doing all along just because the first version didn't have an installer.
 
You must log in or register to reply here.
Back
Top