Mine is still not working. Build Version 2014.2515 (2014.12.2)
Engineering is looking into it. But in the mean time it might be worth doing a few things.
For someone experiencing this problem who’s a little more terminal/command line savvy, run this command:
ls -l /var/log/system.log
and:
ps auxww | grep syslogd
and post the output here. One of the reports above shows the user killing that file and restarting syslogd which could fix a permission problem. It could also fix a locking problem too, should some other app have tried to write there and locked the file (which of course those commands won’t show me).
Rob
Same here 2500, 2511, 2517 no print outs on yosemite 10.10.1 
Please fix this as its a real PITA although the workaround is to use console for now!
I found build 2014.2494 prints out to the terminal which is nice but do we have any info on what the score is with the newer builds doing so??
My /var/log/system.log file contains all the print out data but deleting it and restarting doesn’t fix the issue
I’m using build 2500 and syslog is working but hogs 99% cpu, it’s a pain in the ass as every new window creates another syslog and starts spinning the fans in my macbook like crazy. I restarted my machine and the syslog pops up and then disappears after I close the corona simulator, so I guess I had it going on for too long and this problem persisted until I restarted the machine
Mine randomly started working again yesterday :huh:
Hi Rob,
I am using daily build 2014.2521 , I also have terminal issue and try the tricks to delete system.log file but not works for me.
I tried your commands and get this output
Bhavins-Mac-mini:~ BKPANARA$ ps auxww | grep syslogd
BKPANARA 708 0.3 0.0 2423356 200 s001 R+ 7:13PM 0:00.00 grep syslogd
root 17 0.0 0.0 2474004 1548 ?? Ss 6:40PM 0:00.95 /usr/sbin/syslogd
Please guide me , what should i do for terminal working.
Thank You.
Bhavin
Hi, mine started working again randomly, didn’t do anything different it just started working again. I tried everything suggested an nothing then suddenly it works again.
I did uninstall the Android SDK and re-install it? Don’t know if that did it or what?
Cheers and good luck guys!
Same problem here, older version of Corona that came with the corona terminal in the folder, works.
Should be something that changed after fuse powered.
I keep getting the notifications for this post updating…
When mine wasn’t working for someone who develops full time in Corona this was a BIG inconvenience, fortunately as I mentioned mine started working randomly by itself.
However if it had not started working I find the radio silence from the Corona staff on this issue very disheartening for what seems to be a common problem.
Come on guys sort it out!!
Engineering is looking into it. We can’t reproduce it. It’s working fine on our computers. This isn’t something that a bug report will help with either. In the mean time…
This is a change to make the Mac version of Corona SDK behave like Windows with regards to starting up an output window for you. On OSX prior to this change, you had to launch “Corona Terminal” to get an output window. It would then start Corona Simulator for you. On Windows, you just launch Corona Simulator and we start a command shell for you. This is the desirable behavior instead of having the Corona Terminal method of launching. It seems some people’s syslogd/logfiles are not behaving the same as they are on other Macs.
In the mean time, if you want to go back to having a “Corona Terminal” and launch it old school like, go to this thread:
http://forums.coronalabs.com/topic/52629-new-mac-console-loving-it/page-2
Scroll down my Dec 2. post and implement the script there and see if it helps you until we can sort this out.
Rob
I only get syslog output when building a project from Sublime. Running the simulator by itself and opeing a project I get no syslog output.
I usually immediately close it, (I have a terminal feedback in sublime) because it’s just eating away CPU like mad.
Is it just me or those the syslog take 95% of the cpu when it’s running. I don’t recall this being a big issue or maybe I never noticed it, but it’s downright annoying on a laptop.
This is all the latest build on Yosemite. Anyway to disable terminal on Corona Startup??? I
I found a very simple temporary solution for now.
- open corona simulator
- open var/log/
- open system.log file in TextWrangler
- Run any project
You can see all the log in the open system.log file (as per luisherranz ) and we can consider TextWrangler as corona terminal ;)
I know this is not permanent solution but we can go on for now until CORONA finds the solution.
Please Corona solve this ASAP.
Thank you.
Bhavin 
Update: This still seems to be a system by system issue. Many people are using the new console setup with great success. Here is a list of information that will help us:
What version of OS-X are you running?
What version of Corona SDK are you running?
Can you provide a screen shot showing the Corona Terminal that we started up?
Do you see your corona messages showing up in /var/log/system.log? Are there any errors after Corona starts up?
Do you see your corona messages showing up in the system Console app? (Spotlight search, type in Console) Are there any errors after Corona starts up?
When was the last time you rebooted your Mac?
While we work to solve this, we will be adding a version of “Corona Terminal” back into the .dmg package for those who are worried about doing any command line work. We will be posting a version of it later that you can add for those without access to Daily Builds.
Rob
My terminal started working again :)
Don’t know how… :o
I am using build 2014.2521.
Bhavin
Mine has stopped working today after shutting my mac down last night and rebooting as normal this morning 
To answer your questions Rob:
Yosemite 10.10.1
Corona 2511 (however 2524 behaves the same)
http://imageshack.com/a/img537/7826/onp2c6.png
Yes
No
Yes
No
This morning (8am GMT)
Oh dear, please get the old style one back in a daily build ASAP!!
Daily build 2526 has “Corona Terminal” back that you can use to launch Corona SDK and get output to the terminal window liked it used to be until we can figure out what’s going on with syslogd.
Rob
Thanks Rob.
That’s really much better for those whose terminal is still not working or again stop working.
Thanks you For very quick update.
Bhavin
I have/had this issue with the latest build (Version 2014.2511 (2014.11.18)). I am on OSX 10.10.2. The only incidents in the past week was I had to force restart and I recently ran system updates. Not sure if either had a role in breaking the connection.
I tried to delete the log file but that did not help. However, I found a work around.
Trying to open the application from Launchpad or from the Applications folder, opens the app but does not print the data to terminal.
Solution
- Go to Applications >CoronaSDK > Corona Simulator and right click. You should see a menu. Click Show package contents
- Navigate to and open Contents > MacOS > Corona Simulator
Terminal will open with two windows. The front one will say
Corona Simulator Console ------------------------ Diagnostics and Lua print output will appear here
but nothing will ever print to it. Close that…
The back one will say something like
/Applications/CoronaSDK/Corona\ Simulator.app/Contents/MacOS/Corona\ Simulator ; exit; 2015-02-06 17:31:13.996 Corona Simulator[848:538617] Copyright (C) 2009-2014 C o r o n a L a b s I n c . 2015-02-06 17:31:13.996 Corona Simulator[848:538617] Version: 3.0.0 2015-02-06 17:31:13.996 Corona Simulator[848:538617] Build: 2014.2511
This window will print.
Not sure if this will help anyone else, but it has helped me.
Hi @luisherranz,
Which version of Corona SDK are you using? Since when did the console/Terminal reports stop showing? Did this occur only on upgrade to Yosemite, or when you upgraded Corona to a newer version? Are you using any IDEs like Glider or similar? Are you opening the Simulator through some unusual method like a command line script or something?
Thanks,
Brent