summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordnicoara <dnicoara@chromium.org>2014-08-28 16:51:25 -0700
committerCommit bot <commit-bot@chromium.org>2014-08-28 23:52:18 +0000
commitc1389309e847eb45ccafb18e0ae7373c675b60c1 (patch)
tree2dcfc591fdc579c648f03bcade4624cab21fee5b
parent159c27b073e61cf021c4431dd095db7b4b661d3b (diff)
downloadchromium_src-c1389309e847eb45ccafb18e0ae7373c675b60c1.zip
chromium_src-c1389309e847eb45ccafb18e0ae7373c675b60c1.tar.gz
chromium_src-c1389309e847eb45ccafb18e0ae7373c675b60c1.tar.bz2
Print information on connected displays to VLOG(1)
Finding the root cause of display configuration bugs is harder without knowing which displays were reported as connected. BUG=none Review URL: https://codereview.chromium.org/518553002 Cr-Commit-Position: refs/heads/master@{#292507}
-rw-r--r--ui/display/chromeos/x11/native_display_delegate_x11.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/ui/display/chromeos/x11/native_display_delegate_x11.cc b/ui/display/chromeos/x11/native_display_delegate_x11.cc
index 1cb6483..5f19ae6 100644
--- a/ui/display/chromeos/x11/native_display_delegate_x11.cc
+++ b/ui/display/chromeos/x11/native_display_delegate_x11.cc
@@ -435,7 +435,7 @@ DisplaySnapshotX11* NativeDisplayDelegateX11::InitDisplaySnapshot(
crtc,
index);
- VLOG(2) << "Found display " << cached_outputs_.size() << ":"
+ VLOG(1) << "Found display " << cached_outputs_.size() << ":"
<< " output=" << output << " crtc=" << crtc
<< " current_mode=" << current_mode_id;