That's pretty odd. The "shutdown" button at the login screen is webui. The shelf items are native views UI.

I agree it looks like a resource ID problem.

What revision of chrome are you on?

re:#1 seems to have happened somewhere between r419000 and r419500

hshi, does it go away after a clean build? That would support a missing dependency.

I don't see this on a linux desktop os=chromeos build at r420333 (nor have I seen it there any time this week).

The only other thing I can think of is the deploy_chrome script not copying something we need, or a 100% vs. 200% resource pak problem.

+stevenjb, did anything in deploy_chrome change recently?

Yes, there was bug in deploy_chrome that has a fix pending which is likely the cause of this.

Sadrul, can you mark this as fixed once that is in chromite and chromite for chrome has been rolled (I can help with that if you haven't done it recently)?

I actually removed that part of the change from my CL since it wasn't clear what the fix should be: we seem to not want to unconditionally deploy the 2x resources, and the condition we depend on (having 'highdpi' in USE env variable) does not seem to work [anymore].

OK, yeah, I just saw that. I see that the highdpi issue is still assigned to me. I will mark this as a dupe and continue the discussion there.