How to see ChromiumBrowser log ?

1,517 views
Skip to first unread message

Daniel Yoo

unread,
Aug 1, 2014, 1:12:25 AM8/1/14
to chromiu...@chromium.org
Hi.

I send dbus signal to Browser, but I wonder if Browser gets the signal correctly.

There are some logs in /var/log/chrome/chrome but not everyone. 

Please help me 

Thank you.

Mike Frysinger

unread,
Aug 1, 2014, 1:13:36 AM8/1/14
to Daniel Yoo, chromium-os-dev
do you mean file:///var/log/messages ?
-mike



--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en


Daniel Yoo

unread,
Aug 1, 2014, 5:08:12 AM8/1/14
to chromiu...@chromium.org, near...@gmail.com
Hi Mike.
Thank you for reply my question. You are very kind person. 

I think /var/log/messages has logs related to system like kernel.  
There is no log what I what. 

I send SuspendImminent DBus signal so Browser should receive it. The callback function is SuspendImminentReceived.
There is VLOG(1) << "Got " << power_manager::kSuspendImminentSignal << " signal "
            << "announcing suspend attempt " << proto.suspend_id();  code in power_manager_client.cc
I want to see that log to confirm if I send signal correctly or not.
Thank you.-Daniel



2014년 8월 1일 금요일 오후 2시 13분 36초 UTC+9, Mike Frysinger 님의 말:

Mike Frysinger

unread,
Aug 1, 2014, 6:35:03 AM8/1/14
to Daniel Yoo, chromium-os-dev
/var/log/messages contains system messages, many of which are the kernel, but not all.  some daemons get routed to other files.

maybe /var/log/powerd.out is what you want ?
-mike

Daniel Erat

unread,
Aug 1, 2014, 11:27:44 AM8/1/14
to Daniel Yoo, Chromium OS dev
You're probably looking in the right place. Chrome logs to /var/log/chrome/chrome at the login screen and to /home/chronos/user/log/chrome when a user is logged in (note that this is within the user's encrypted home directory, so you'll only be able to read the files while logged in).

The "v" in VLOG(1) stands for "verbose"; these messages aren't logged by default. To turn them on in your local build, you can update the --vmodule flag passed to Chrome by adding a line like "vmodule=power_manager_client=1" to /etc/chrome_dev.conf.

Daniel Yoo

unread,
Aug 4, 2014, 4:08:05 AM8/4/14
to chromiu...@chromium.org, near...@gmail.com
Thank you Dan. I could see logs by your reply. 


2014년 8월 1일 금요일 오전 8시 27분 44초 UTC-7, Dan Erat 님의 말:

Sreenidhi Koti

unread,
Aug 11, 2014, 6:52:15 AM8/11/14
to chromiu...@chromium.org, near...@gmail.com
Hi Dan/Daniel,

I'm stuck with the same problem where i'm not getting logs from the V4L2 capture device. I'm trying to get the logs from from the following three files:

src/media/video/capture/linux/video_capture_device_factory_linux.cc
src/media/video/capture/linux/video_capture_device_linux.cc
src/third_party/webrtc/modules/video_capture/linux/video_capture_linux.cc

I've inserted the following lines in /etc/chrome_dev.conf

--vmodule vmodule=video_capture_device_linux=1

--vmodule vmodule=video_capture_linux=1

--vmodule  vmodule=video_capture_device_factory_linux=1

I'm not very sure if this is the right way to insert the commands to get logs from multiple files. 

PS: I've also added --enable-logging --v=1 command in the chrome_dev.conf. But still i'm not seeing any Verbose logs.

Thanks
Sreenidhi Koti

Daniel Erat

unread,
Aug 11, 2014, 10:32:34 AM8/11/14
to Sreenidhi Koti, Chromium OS dev
On Mon, Aug 11, 2014 at 3:52 AM, Sreenidhi Koti <sreeni...@gmail.com> wrote:
Hi Dan/Daniel,

I'm stuck with the same problem where i'm not getting logs from the V4L2 capture device. I'm trying to get the logs from from the following three files:

src/media/video/capture/linux/video_capture_device_factory_linux.cc
src/media/video/capture/linux/video_capture_device_linux.cc
src/third_party/webrtc/modules/video_capture/linux/video_capture_linux.cc

I've inserted the following lines in /etc/chrome_dev.conf

--vmodule vmodule=video_capture_device_linux=1

--vmodule vmodule=video_capture_linux=1

--vmodule  vmodule=video_capture_device_factory_linux=1

I'm not very sure if this is the right way to insert the commands to get logs from multiple files. 

It isn't. Per the comment in the file, you should add the following lines:

vmodule=video_capture_device_linux=1
vmodule=video_capture_linux=1
vmodule=video_capture_device_factory_linux=1

Sreenidhi Koti

unread,
Aug 11, 2014, 11:18:06 PM8/11/14
to Daniel Erat, Chromium OS dev
Thanks Daniel! I could see the logs now..

Mike Frysinger

unread,
Aug 11, 2014, 11:23:06 PM8/11/14
to Daniel Erat, Sreenidhi Koti, Chromium OS dev
On Mon, Aug 11, 2014 at 11:32 PM, Daniel Erat <de...@chromium.org> wrote:
On Mon, Aug 11, 2014 at 3:52 AM, Sreenidhi Koti <sreeni...@gmail.com> wrote:
Hi Dan/Daniel,

I'm stuck with the same problem where i'm not getting logs from the V4L2 capture device. I'm trying to get the logs from from the following three files:

src/media/video/capture/linux/video_capture_device_factory_linux.cc
src/media/video/capture/linux/video_capture_device_linux.cc
src/third_party/webrtc/modules/video_capture/linux/video_capture_linux.cc

I've inserted the following lines in /etc/chrome_dev.conf

--vmodule vmodule=video_capture_device_linux=1

--vmodule vmodule=video_capture_linux=1

--vmodule  vmodule=video_capture_device_factory_linux=1

I'm not very sure if this is the right way to insert the commands to get logs from multiple files. 

It isn't. Per the comment in the file, you should add the following lines:

vmodule=video_capture_device_linux=1
vmodule=video_capture_linux=1
vmodule=video_capture_device_factory_linux=1

seems like an easy mistake to make.  should we catch & warn when a line starts with a - ?
-mike

Daniel Erat

unread,
Aug 12, 2014, 10:38:01 AM8/12/14
to Mike Frysinger, Sreenidhi Koti, Chromium OS dev
Lines are allowed to start with "-" [1]; that's the usual way to add a command-line flag (e.g. "--foo"). "vmodule=" is a separate command so that people can append additional modules to the existing list instead of replacing the current value of the --vmodule flag.

All of this is documented in the comment at the top of chrome_dev.conf, but patches are welcome if anyone has suggestions for making it clearer.

1. or anything else except "!" or "ALL_CAPS_IDENTIFIER=", which delete existing arguments or define environment variables

Mike Frysinger

unread,
Aug 12, 2014, 10:40:46 AM8/12/14
to Daniel Erat, Sreenidhi Koti, Chromium OS dev
ok, i looked closer and see what you mean.  i think existing docs are sufficient :).
-mike
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages