New issue
Advanced search Search tips

Issue 767840 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 749755
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

No way to block students from changing wallpaper

Reported by rabb...@anderson4.org, Sep 22 2017

Issue description

There is no policy currently that will block the student in a K12 environment from changing the designated wallpaper that has been chosen....


 
Hi,

I'm new to chromebooks and having the same issue.

I have applied a custom corporate wallpaper image to the chromebooks which works well, as I understand it the users should not be able to change this wallpaper. If a user taps with two fingers on the desktop a menu appear and the option to 'Set wallpaper...' is greyed out (as i'd expect). However if the user goes in to settings they can access the wallpaper chooser from the 'Appearance' section. Once they have changed the wallpaper the desktop 'Set wallpaper...' option is no longer greyed out and can be used to make further changes.

Version 60.0.3112.114 (64Bit)

Asus Chromebook C202S
I am seeing the same thing in our district.  I have forced a custom wallpaper in both the user and the device settings.   But students that go to Settings and change wallpaper can then choose a custom wallpaper.   This defeats the purpose of setting a custom wallpaper.  Is this a glitch in the system?  In OS version?

I have seen this in Version 60 and 61.0.3163.120
Components: Services>SupervisedUser Enterprise
Labels: Enterprise-Triaged
Owner: dskaram@chromium.org

Comment 5 by dskaram@google.com, Nov 6 2017

Cc: abodenha@chromium.org omrilio@chromium.org maxkirsch@chromium.org
Labels: -Type-Bug -Pri-3 Pri-1 Type-Bug-Regression
Owner: omrilio@chromium.org
This seems like a regression. Adding Omri and Albert and raising priority.

+Max for visibility.
Cc: steve...@chromium.org x...@chromium.org
Components: UI>Settings
Labels: ReleaseBlock-Stable M-63
This sounds really bad.

Comment 7 by x...@chromium.org, Nov 6 2017

Mergedinto: 749755
Status: Duplicate (was: Unconfirmed)
It has been fixed in M62.
+1 this should be fixed on latest stable.

Comment 9 by x...@chromium.org, Nov 6 2017

Re Omri: Do you mean we should merge the fix in latest 61 stable? (It's already in 62) Not sure if it's feasible at current moment. 
Stable channel is already at 62. There's no value in a merge to 61.

Sign in to add a comment