How to enable logging for Google Chrome in Ubuntu 12.04?
I'm trying to capture the logs for a certain bug I'm having with Google Chrome. However, I can't find/enable logs for GC.
According to this Chromium project page, I just need to add the flags --enable-logging --v=1 and a chrome_debug.log file will appear in my user data directory. However, after running GC (and closing through the 'X' title bar button) there is no chrome_debug.log file in the specified directory. I even tried running as root as it may have something to do with write permissions but GC refuses to start as root.
Another thing, GC also prints messages when invoked from command line. I tried capturing this and redirecting them to a file via $ google-chrome > today.log but the messages are still printed in the command line and the file I specify gets created but remains empty.
Note that I can't just copy-paste the messages printed on terminal after my bug occurs as the bug freezes up my whole system that, when it occurs, my only option is to turn off my computer straight via the power button. I've seen a few similar bugs already posted but I find that they don't exactly describe my situation so I'd really like to get some logs for this.
So how do I enable logging or, at least, get those terminal messages in a file?
It seems likely that you're not looking in the right place for the log file.
When you run google-chrome --enable-logging --v=1, the log file will be created inside ~/.config/google-chrome (where ~ represents your home folder). If you're using Nautilus (the graphical file browser), you'll have to press Ctrl+H or click View > Show Hidden Files to see files and folders that start with ., such as the .config folder.
Or, if you're using Chromium rather than Chrome and you run chromium-browser --enable-logging --v=1, the log file will be created inside ~/.config/chromium.
If you want to send all the output of a command to a file, including error output, use the &> redirection operator instead of just >. So you could run google-chrome &> output.txt.
edit
you can also see your crashes reports at
chrome://crashesif logging was enabled before
Another hit is to redirect to stderr
--enable-logging=stderr --v=1