Terminal problem in leopard

Hey, i copied his over from the general forum
i did a fresh install on my macbook, and i reinstalled all my dev environment. I had some trouble with this and i may have messed something up in the process, but basically i have no prompt and it says login in the titlebar. thisafter i installed mysql, set up apache the way i need with virtual hosts, added stuff to my hosts file, and installed the fixed leopard mysql prefpane (plus someother stuff like setting up root password).
The only .bash file i have in my home directory is .bash_history

I'm ran into the same problem. When I ran 'sudo mysqld_safe5 &', it would kill my Terminal in exactly the way you describe. Turns out the 'sudo' was still hanging around, I was able to kill the 'sudo' processes via Activity Monitor (maybe sure you show 'All Processes'), after that I had my terminal back. Launching Mysql at boot via launchd worked for me: http://hivelogic.com/articles/installing-mysql-on-mac-os-x/, skip to "Auto-Starting Mysql" if you already have Mysql installed.
Good luck!

Similar Messages

Weird Terminal problem with AIX

Hi,
I have kind of an odd problem with the Terminal.app that I hope someone can assist me in figuring out.
I'm connecting to an AIX 5.3 server and the top portion of the window is always "cut off". It's there, it's just one screen up in the buffer and I can't figure out why. I can connect with iTerm and things display appropriately.
Below is a link to a side by side picture of Terminal.app (left) and iTerm (right). If I scroll up in the Terminal.app buffer, I can see the missing lines from the top of the screen.
http://picasaweb.google.com/andy.black10/Misc#5407855064094337554
Thanks,
Andy

Minor point: would you please fill in your Forum profile information, at least the Mac OS X operating system version.
I'm currently using Leopard and I can reproduce this problem in Terminal vs iTerm. I used your script output (thank you) in order to generate the escape sequences.
BY THE WAY, if the script output contains any sensitive login info, you might want to change your password on the Pharamcy OSU system
It looks like there is a Terminal problem handling Scrolling Regions as set by <esc>[1;24r. It looks like <esc>[0J is not erasing from the current cursor position to the end of the display, but rather it starts the erase above the current cursor position. The erase behavior without a scrolling region appears better, but not perfect.
I would encourage you to file a bug with Apple at either:
<http://www.apple.com/feedback/macosx.html>
or
<http://bugreporter.apple.com>
Free ADC (Apple Developer Connection) account needed for BugReporter
The BugReporter would be better.
If you want, I have a little script that can be used to demonstrate the problem
#!/usr/bin/env bash
echo -e "e[1;24re[He[0Je[He[0Je[?6he[1;24re[He[0Jc"
for j in {1..3}
do
echo BEFORE should remain on screen $j $j $j $j $j
done
for j in {4..23}
do
echo FILLER should be erased $j $j $j $j $j
done
echo -e "e[4;24re[He[0Jc"
for j in {4..23} # our next command prompt will be 24th line
do
echo AFTER should remain on screen $j $j $j $j $j
done
Here is example output from Terminal:
BEFORE should remain on screen 1 1 1 1 1
AFTER should remain on screen 4 4 4 4 4
AFTER should remain on screen 5 5 5 5 5
AFTER should remain on screen 6 6 6 6 6
AFTER should remain on screen 7 7 7 7 7
AFTER should remain on screen 8 8 8 8 8
AFTER should remain on screen 9 9 9 9 9
AFTER should remain on screen 10 10 10 10 10
AFTER should remain on screen 11 11 11 11 11
AFTER should remain on screen 12 12 12 12 12
AFTER should remain on screen 13 13 13 13 13
AFTER should remain on screen 14 14 14 14 14
AFTER should remain on screen 15 15 15 15 15
AFTER should remain on screen 16 16 16 16 16
AFTER should remain on screen 17 17 17 17 17
AFTER should remain on screen 18 18 18 18 18
AFTER should remain on screen 19 19 19 19 19
AFTER should remain on screen 20 20 20 20 20
AFTER should remain on screen 21 21 21 21 21
AFTER should remain on screen 22 22 22 22 22
AFTER should remain on screen 23 23 23 23 23
and here is example output from iTerm:
BEFORE should remain on screen 1 1 1 1 1
BEFORE should remain on screen 2 2 2 2 2
BEFORE should remain on screen 3 3 3 3 3
AFTER should remain on screen 4 4 4 4 4
AFTER should remain on screen 5 5 5 5 5
AFTER should remain on screen 6 6 6 6 6
AFTER should remain on screen 7 7 7 7 7
AFTER should remain on screen 8 8 8 8 8
AFTER should remain on screen 9 9 9 9 9
AFTER should remain on screen 10 10 10 10 10
AFTER should remain on screen 11 11 11 11 11
AFTER should remain on screen 12 12 12 12 12
AFTER should remain on screen 13 13 13 13 13
AFTER should remain on screen 14 14 14 14 14
AFTER should remain on screen 15 15 15 15 15
AFTER should remain on screen 16 16 16 16 16
AFTER should remain on screen 17 17 17 17 17
AFTER should remain on screen 18 18 18 18 18
AFTER should remain on screen 19 19 19 19 19
AFTER should remain on screen 20 20 20 20 20
AFTER should remain on screen 21 21 21 21 21
AFTER should remain on screen 22 22 22 22 22
AFTER should remain on screen 23 23 23 23 23

Anyone else having a Problem with Leopard and Photoshop CS3?

I'm using CS3 with Leopard 10.5.4 at work and there are some very aggravating anomalies, that I'd like to nail down to a cause. Most frequently, when switching from apps to P'Shop, the menu bar stays for the previous app, i.e. when going from Finder to P'shop, the menu bar still says Finder and has Finder options. Changing from Lightwave to P'Shop, the menu bar remains Lightwave.
Occasionally, an Adobe app - P'Shop or InDesign - will simply disappear and not come back. The icon in the dock shows it as active, but no amount of clicking, Command-Tabbing will reveal the app and I have to Force Quit, losing unsaved changes.
I have a feeling it's Leopard, since, I've used CS3 on Tiger and CS4 on Tiger and never had a problem.
I'm wondering if upgrading to the latest Leopard would make much of a difference.
Has anyone come across this and found any kind of answers?
Thanks for any suggestions.
-Vincent

> Just because it doesn't happen to Phil (who may not use all of the same features of the Suite that others do anyway) does NOT mean that these problems are not real and are not mere PEBCAK.
Right. If someone is having a problem associated with Tiger, it's PEBAK. If Leopard is involved, it's automatically because of Leopard. Apparently, with Apple's latest OS, trouble shooting problems are no longer necessary - just blame it on Leopard and call it a day.
b FUD
I find the dynamics here really interesting. This thread would have been very different if Vincent had posted with problems involving Tiger. Would have gone something like this:
After admonishing him for not providing more information about his setup by posting the obnoxious big blue link on how to ask questions (ahem - we know NOTHING about his machine or configuration, such as which machine, how much RAM, scratch disk or attached peripherals), there'd be all kinds of trouble shooting advice given - "try a new user", "repair permissions", "run DiskWarrior, and on and on ...
But no, since he mentions Leopard, none of that is apparently necessary and the completely, utterly
b irresponsible
advice is given ... "that's just the way Leopard is".
Those are some serious problems he's reporting that have nothing to do with Leopard. Something is obviously hosed!
As for discounting my experience because I don't use every app in the suite as extensively as I do Photoshop, I'm FAR more qualified to discuss Leopard and CS issues than Ann or Neil who do not use Leopard at all (and have never used it as far as I know.)
"Others have problems with it", is their battle cry but it's extremely weak. Do I really need to remind you all that these forum are ALWAYS filled with people who have problems, regardless of version or OS? You act as if this forum was a ghost town when Tiger and CS3 were current!
Gee, Ann ... people are STILL reporting problems with 10.5 and CS3? How shocking! Guess what - people are STILL reporting problems with 10.4 and CS3 too! Let me make a prediction - people will have problems with 10.8 and CS9!
Vincent-
> I don't really deal with fonts anyway ...
Yes. You do. Even if you never type a single line of text, every application uses fonts to create menus and other GUI items. If one of those fonts are bad, it can create all kinds of problems, including the very problems you mention.
The fact that you don't seem aware of this and you're still using 10.5.4 leads me to believe you're not familiar with the basic practices of maintaining a healthy system. Again, how did you install Leopard on that machine?
Look, if you're simply trying to justify using CS4, go right ahead. It's a worthwhile upgrade in it's own right. However, if you install it on that machine in it's current state, CS4 will NOT fix your problems because you do NOT have a healthy system.
You asked for experiences with Leopard - I can launch every application in both CS3 and CS4 suites
i simultaneously,
and STILL not have your issues. I haven't experienced anything like your CS3 problems in Leopard - on both a 2006 Mac Pro and a 2008 Macbook.
If you'd like help to try and figure out the real problem, I'm more than happy to help. If not, Adobe will gladly take your money ...
-phil

Database termination Problem

Hi every body ..plz help me on this..
We are facing database termination problem in ECC6 production syste.
Database: Oracle 10.2, O/S: Windows 2003. Spam :27, SP level 13.
Error is:
Errors in file f:\oracle\p02\saptrace\background\p02_ckpt_6520.trc:
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: 'D:\ORACLE\P02\ORIGLOGB\CNTRL\CNTRLP02.DBF'
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
When we are performing backup then data base termination occuring freequently.
Give right solution as early as possible.
Thanks,
Nani.

Hi,
Have a look at below snote which actually speaks about the oracle error codes
Snote : 546006
within the Snote it says :-
" If you cannot access a database file (for instance a data file, control file or RedoLog) for whatever reason, an ORA-270xx appears. The actual cause comes from additional error messages (usually in the operating system) that occur on ORA-270xx. "
And as per your last update
" ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: 'D:\ORACLE\P02\ORIGLOGB\CNTRL\CNTRLP02.DBF' "
i think there is problem accessing the database control file. Hence you are facing the above problem.
I think if you recreate your control file i think, it should resolve the problem.
Hope it will be helpful to resolve your problem.
Rgds
Radhakrishna D S

Problem with leopard DVD loading in PowerPC G4

Hi having problems installing Leopard DVD on Mac G4 desk top - 1GHz PowerPC G4 (3,6), 1MB L3 Cache, 768 MB Ram.
A few of the details:
1) I have installed Leopard on my Laptop and it is running fine and it is a family pack edition DVD.
2) I wiped the G4 I am trying to install clean and re-loaded the original system software, then loaded to Tiger to see if that was the issue...When I put in the Leopard DVD it doesn't even show as being in the computer. It doesn't come up on the desk top...it doesn't show in the HD...it doesn't make a sound at all when put in the DVD slot...basically, the computer is not recognizing the DVD. I have tried other cd's and DVD's in the drive....everything is working except the Leopard DVD.
Any ideas?

Allan Eckert wrote:
Hi TK333;
Where did you get the Leopard DVD? Did you buy it or did it come with another Mac?
Allan
Hi Allan. He said it was a Family Pack DVD.

Possible Fix for Printing Problems in Leopard

I got this information from Mac OS X Leopard Edition book by David Pogue. Here's his possible fix for printing problems in Leopard...Open web browser and enter this address http://127.0.0.1:631. You'll find youself at a secret "front end" for CUPS (Common UNIX Printer System), the underlying printing technology for Mac OS X 10.5. This trick lets your Mac communicate with a huge array of older printers that dopn't yet have Mac OS X drivers. Using this administration screen, you can print a test page, stop your printer in its tracks, manage your networked printers and print jobs, and more–a very slick trick. Haven't tried it yet...anyone who does let me know how it worked!

If you literally "checked" them, meaning the checkboxes, that only affects their visibility. To remove them, select one and then click on the "minus" part of the "plus minus" at lower left.
Doug

Digital Camera Connection Problems With Leopard

Hi Everyone,
I'm having a big problem with connecting various digital cameras to my macs. I have 3 different machines (a G5 iMac, 2 MacBook Pros) all running 10.5.1 or 10.5.2 and none of them will recognize my canon Powershot SD800 or my SD1000. I haven't had a chance to test it out with my Digital Rebel yet but I'm suspecting I may run into the same issue.
I've read through all the tech notes in the iLife section and various articles on the web and from what I can tell Apple has a problem with usb device connections in Leopard. I've tried all of the fixes (deleting caches folder, resetting PRAM, updating all applications, etc) and nothing works. The cameras were working fine under 10.4.11. I was really hoping Apple would have fixed this in 10.5.2 but it is still not working. Does anyone have any ideas if Apple is working on this? For photographers like myself this is a major deal. I can get around the issue right now using an external memory card reader, but that's extremely inconvenient at times and I'm just not impressed that something like this has gone months without a fix from Apple.

And I'm not having any problems with Leopard mounting my Canon PowerShot Pro or Rebel though I typically don't connect them, choosing to use a card reader instead. (Saves camera battery.) This is true on the 4 computers I use at home and work as well as my wife's MacBook. Two came with Leopard pre-installed the other 3 I installed Leopard using Archive & install.
We can talk about how you upgraded to Leopard or what you have installed that might be getting in the way, or you can buy an inexpensive card reader and be done with the hassle.

Mouse interaction problem in Leopard

Hi Folks,
All of a sudden, my mouse has some interaction problem in Leopard. Tried different mice, they all behave the same, so I guess this is an issue with Leopard.
Very weird symptoms:
1- In Sarafi, when I place pointer on a hyperlink, it doesn't change from arrow to hand, but click action still works.
2- In menu bar, the selection doesn't get highlighted when I move the pointer over the menu.
3- For Dock (in auto-hide mode), the Dock doesn't pop up automatically if I move the pointer to the bottom of the screen. I have to click somewhere in the bottom to bring up the Dock, but the icons don't get magnified when I place pointer over them.
Any idea what the problem is and how to fix that?
Thanks for the help, guys.
Raimondo
Message was edited by: Raimondo.jiang

my iMac just got this problem yesterday, no luck since then.
tried all stuff i could think of
repair permissions, restart, new user(SAME!), install 10.5.4 combo again, PRAM zap
mac retailer here in Taiwan doesnt know either!
any ideas?

Fewer problems with Leopard if bought on new iMac rather than upgrade?

I bought a new iMac (my 1st Mac ever) just before Leopard came out, so I have Tiger 10.4.11 now and love it. I've had no problems whatsoever and really don't plan on upgrading to Leopard because of all the problems I keep reading about. My brother is thinking about buying an iMac but hesitates because he's heard so many problems about Leopard. Question for you guys - do the Leopard problems seem more common if you've done an upgrade from Tiger, or are the problems just as common if you buy a new iMac with Leopard installed? Any help will be greatly appreciated. Thanks.

I bought a new iMac (my 1st Mac ever) just before Leopard came out, so I have Tiger 10.4.11 now and love it. I've had no problems whatsoever and really don't plan on upgrading to Leopard because of all the problems I keep reading about.
Your choice - BUT remember that Millions of people have upgraded with NO problems - you only read about the very few who do have problems. Leopard is a great OS and IF you upgrade carefully (repair your disk, fix permissions, backup and have a bootable clone in case of problems) you are very unlikely to have problems and it is EASY to go back to your clone in the unlikely case that you do have any problem.
My brother is thinking about buying an iMac but hesitates because he's heard so many problems about Leopard. Question for you guys - do the Leopard problems seem more common if you've done an upgrade from Tiger, or are the problems just as common if you buy a new iMac with Leopard installed
This is a "how long ago did yo stop beating your wife question" - Problems are VERY uncommon in either case. With new systems they are highly unlikely since there is no previous damage to the system and NO incompatible third party software on the system - but problems are extremely uncommon in either case
He should move ahead with his purchase IMHO.
LN
Message was edited by: LarryHN

Problems reinstalling Leopard on Macbook

Just recently, I've had some serious problems installing Leopard back onto my Macbook. About 4 days ago, I decided to use boot camp to try Windows XP on my Macbook. It all went smooth as I was trying out Windows XP, but I soon found out that I had some serious problems. Boot camp had written over my version of Leopard. When I held down the option key, all I saw was Windows. Of course I thought this could be easily remedied by using my Install disks 1 and 2 but for some reason, neither disks were recognized when I put them in. At one point disk 1 was recognized but it took about twenty minutes to actually get to the install screen. Once there I tried to erase or wipe the Harddrive as it says to do in the apple instructions. So I went ahead and erased it. This was probably a bad choice seeing as halfway through the first install disk, the installation failed. I had just erased my harddrive and now I cannot even get into Windows! Now I cannot get my Macbook to recognize either disk and both disks are spit out after about 5 times of the disk starting itself back up and trying to recognize it multiple times. Anyone have any suggestions?
Message was edited by: Bowenboy
Message was edited by: Bowenboy

Hi, and welcome to the forums.
You've either got a bad disc or a bad drive. Both happen on occasion.
Do you have access to another Mac? If so, try the disc in it (of course, don't actually do anything, just see if it's readable).
If the disc is bad, and you're near an Apple store, you might be able to get a Genius to install from a disc of theirs, but either way, you need to get a replacement. Depending on how old your Mac is, there may or may not be a small charge.
If the drive is bad, it's covered for a year. If you've got AppleCare, it's even longer.

Install snow leopard from external hard drive-terminal problems!

hi everybody ,
i have a big problem :s
wanted to restore and getting "Restore Failure Could not find any scan information... then i've followed some terminal commands..finished restoring and couldn't boot cause i only find Macintosh HD when i use "alt option" when i restart my macbook pro and even if i go to "startup Disk" i can find my partition of the external hard drive but when i click on it nd do retart it's can't boot ...another thing is tht m having a slow start and it's ask for my Password (i've no problem with password it just doesn't ask me to enter it before and i have internet and server failure)
Due to terminal commands?? :((
Plz help :s

"How to install Snow Leopard from an External Hard Drive"
* Launch Disk Utility
* Select the External Firewire/USB device that you want to use as the boot drive for the upgrade
* Click “Partition” from the menu options
* Select 1 Partition, then click “Options” below the partition scheme
* Select the top option for “GUID Partition Table” – it MUST be GUID to be bootable!
* Click OK to create the GUID partition (this will reformat the drive, ie: all data is lost)
* Next, click the “Restore” tab within Disk Utility
* Select your newly made Snow Leopard 10.6 Install DVD image and restore this image to the GUID partition you just created OR…
* Alternatively, you can select the Snow Leopard Install DVD and restore directly from the DVD to the GUID partition
* After the restoration is complete, your GUID partition will now be bootable by Mac OS X!
* Reboot the Mac holding down the “Option” key to pull up the boot loader, select the Snow Leopard install drive you just created rather than your default Mac OS hard drive
* Install Snow Leopard as usual!
Hope this helps!

Terminal problems

Hi everyone,
Every time I open terminal I get the message below. This only happens in one account in the computer, it does not happen in other accounts. I will appreciate any help to fix the problem. I have a mac book pro, keyboard in spanish, and I am using leopard 10.5.1, but the problem is coming since tiger, I emigrate users from an old mac book pro with tiger.
The message is as follows:
Last login: Sun Jan 20 08:37:00 on ttys000
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LANG = "UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Macintosh:~ javier$

If I go to Terminal-> Preferences _> settings and UNFLAG the last sentence "Set LANG environment variable on startup" then it works … now the sentence that appear in terminal changed a little bit
Well, in the Advanced Settings, I have the "Set LANG environment variable on startup" checkbox ticked, and the "International character encoding is set to "Unicode (UTF-8)". In the "Shell" tab, under "Startup" the "Run command" is unchecked and the text box is empty. My environment has the required locale settings:
macbook:~ michaelc$ echo $LC_ALL
macbook:~ michaelc$ echo $LANG
en_GB.UTF-8
I don't see any change in your Terminal output between your first post and your latest one?
Also, you don't mention what you have set in Terminal > Preferences > Startup, which is what I referred to in my previous post.

Sftp problem with Leopard Server

Hey guys,
The problem I'm having is that I can't get an application to connect to my Leopard Server via sftp. I can bring up a terminal and sftp that way, so I'm not sure why I can't get the app to get in over sftp. I can actually connect successfully with the app over ftp, just not sftp. Anyone know of a reason for this? Thanks for the help.
Mickey

I suggest you ask in the Server forum.
http://discussions.apple.com/category.jspa?categoryID=236

Permission Problems with Leopard & Time Machine are ridiculous!

I just had a hard drive die in a MacBook. I installed a new drive and restored from TM.
Only to find out I have absolutely no ownership to anything in my home directory.
System & Admin -r/w, everyone r --- no where is my id mentioned as having ANY r/w access.
Leopard has been a disaster on 2 out of 3 Macs I've installed it on.
If I wanted this kind of crap I'd use Windows full time.

You'll need to reset permissions on your home directory. Follow these steps:
1) Boot from your Leopard install CD/DVD (insert it, shut down, start while holding "C")
2) Choose your language.
3) When the menubar appears, select Utilities>Reset Password.
4) In the window that appears, select your boot volume (by default, "Macintosh HD") from the list at the top.
5) In the popup menu below the volume list, select an affected user. (One that you used "Apply to enclosed items" on).
6) Click the "Reset" button at the bottom of the window. This will reset the permissions (and ACLs) back to their default settings.
7) Repeat Steps 5 & 6 for every user on your machine who has this problem (except "System Administrator (Root)").
There is one bug in this process, so you need to take some additional steps to get permissions back to how they should be.
8) Log in to an account you reset the permissions for.
9) Open Terminal (/Applications/Utilities/Terminal)
10) Copy the blue text in, and press "return". chgrp -R `id -gn` ~
11) You won't see anything happen, but you can check that it worked by selecting your home folder, and clicking File>Get Info. You will see either "unknown" or "staff" under "Sharing and Permissions", depending on how you installed Leopard. Either one is fine.
12) Repeat the steps 8-11 for every account that you reset permissions for on your machine. (Remember, NOT "System Administrator (Root)").
Good luck!
Message was edited by: joshz

Problem with Leopard on a Macbook pro

I'm posting this for my fiance as it's his computer that's acting up and he can't get here himself. The problem goes as this: He went to boot up his macbook pro, which is running leopard and also has windows installed. When he tried to boot up into the Leopard side, it started normally, got to the grey screen, the swirly goes away, it starts to go to the login, but login never loads, it just goes black. Also, the keyboard lights are not on, but if he hits capslock, the key lights up. He's able to boot up into the windows side with no problem aside from the as-yet-unworking internet connection. Any idea what may have happened or how to fix it?

Make sure all these updaters are installed: find at http://www.apple.com/support/downloads/ although he should have installed these updaters before installing any other major software.
MBP EFI updater 1.4 fixes issues with bootcamp
MBP software update 1.0
MBP software update 1.1 fixes responsiveness and keyboard
MBP software update 1.2

Terminal problem in leopard

Similar Messages

Maybe you are looking for