Hi Bernie, can you please help us to triage or assign if needed?

Daisy, is this something in your jurisdiction?

Let me take a look at it.

Hi all,

Are there any updates on this issue?

Thanks!

Hi, I've received couple of feedback from other customers around this affecting devices on 59 and 60. Asus Flip(minie)

reported on 61 as well, as per customer.
any updates on this issue please?

+bshe@ do you know where the logic to block wallpaper app id is? Is this the same as user wallpaper policy?
And also can we do step (3) in DMTest server?

Hi all,

I have a customer that has this issue and want to have the behavior fix to avoid any distraction for the students.

I hope we have update for this. 

Thanks!

xdai@, bshe@, is there any updates for this issue? Customers are asking.

Sorry. I have no idea. I would guess enterprise policy is party of component/policy. +cc bartfab

Perhaps it doesn't work because wallpaper picker is a component app.

Yes, you cannot block internal parts of Chrome OS like that. However, if the wallpaper is set by policy, any attempt to change it, whether by the wallpaper picker app or otherwise, should fail. There are two bugs here:

1) When the wallpaper is set by policy, any attempts to call the wallpaper setting API should fail.
2) For nicer UX, setting the wallpaper by policy should hide the wallpaper picker app (either via code outside the app or by having the app detect this and show an error message himself).

+atwilson if he wants someone on his team to take this on. I am responsible for ARC Enterprise only these days.

Hello,

We'd like to get any update on this bug please. Thanks!

+dskaram for visibility if we want to escalate priority, definitely picker should not be able to override policy wallpaper.

Re comment#13:
1) Currently if the wallpaper is set by policy, any attempts to set a new wallpaper does fail (even if the user can open Wallpaper Picker app and try to set a wallpaper).
2) Currently if the user wallpaper policy is enforced, there is no way for a user to open the Wallpaper Picker app (there was a MD setting regression that broke this, but it was later fixed in M62.)

Anyone could tell me how to do the step in the bug report? I don't know how to block it thus can't repro it.
(3) Block Wallpaper Picker App ID and set custom wallpaper from User settings in Admin Console 

In Admin Console- we have the User setting set to "Custom Wallpaper" in the General settings See this page for google app policies: https://support.google.com/chrome/a/answer/2657289?hl=en#general

The custom wallpaper loads when user logs into managed chromebook.  If they right click on the desktop-- "Set Wallpaper" is grayed out.   But if they go to Settings and select Wallpaper under appearance --it opens the Wallpaper Picker App and allows them to change the wallpaper.  After they do that once they can now even right click on desktop and now they can "Set Wallpaper"

Defeats the purpose of setting a custom wallpaper in Admin Console if they are able to change it.

Re#17: I believe the bug you described has been fixed in M61 (see  Issue 749755 ). Is that the same issue as this one? 

Re#18  Yes seems to be the same bug.  We are on stable channel and are at version 61.0.3163.123

Guess we have to wait for version 62 or 63 to become stable if I am reading the comments correctly.

Re#18: Right. 62 stable will be out very soon. So the issue should be fixed at that moment (in 62 and later).
I'll close this issue then.