When I run the browser from the command line using `/opt/google/chrome-beta/chrome` instead of the KDE start menu icon, I can't reproduce.

I don't know what is different when run from console :-/

Tested the issue in chrome #56.0.2924.67 and latest build #58.0.2992.0 on Ubuntu 14.04 and not able to reproduce the issue.Please find the screen shot for reference.
@gzoechi: Could you please let me know if i have missed anything and if possible,Please create a new profile without extension and recheck once.Let us know the observations which would help us to triage the issue further.

Thank you in advance!

Deleted: 684403.png 114 KB

	684403.png 114 KB View Download

I disabled all extensions and plugins in my default profile, still the same issue.

Currently on version V8 5.6.326.42 (just updated)

When I use a different profile I, I also can't reproduce.

Any idea how to debug. I'm not used to debugging issues in Chrome.

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I found the cause. JavaScript was disabled in the console.
I intended to only temporarily disable it but forgot to re-enable.

It would be real great if it could be shown more prominently when JS is disabled.  

1) We could show a warning icon next to Sources panel similarly to how we show one for throttling
2) We could make this setting temporary (non-persistent).

Let's start with (1)

We already do the icon next to sources.  The warning icon can be hard to notice, so perhaps we need a better indicator (console message?) or pfeldman@'s 2nd suggestion.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe

commit d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe
Author: luoe <luoe@chromium.org>
Date: Mon Mar 06 18:04:07 2017

DevTools: make disable javascript setting temporary

This makes the "disable javascript" setting temporary, similar to
networkBlockedURLs. Before, disabling JS then opening a new tab with DevTools
resulted in disabled JS on the new tab. Now, opening DevTools in the new tab
will not have the same setting as the last tab.

Behavior when closing/opening DevTools on the same tab, navigating the page, and
toggling the checkbox should not be affected by this CL.

BUG= 684403 

Review-Url: https://codereview.chromium.org/2708413003
Cr-Commit-Position: refs/heads/master@{#454885}

[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/Tests.js
[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/common/Settings.js
[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/help/Help.js
[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/main/module.json
[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/sdk/NetworkManager.js
[modify] https://crrev.com/d86ba3089c88fd85df42b2660bf5dd8a2cda6dfe/third_party/WebKit/Source/devtools/front_end/sdk/module.json

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]

Now that the setting checkbox is temporary, there should be less confusion.