Policy to deploy desktop wallpaper does not always apply
Reported by
rdni...@wheatleypark.org,
Nov 16 2016
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8743.83.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.93 Safari/537.36 Platform: 8743.83.0 (Official Build) stable-channel mccloud Steps to reproduce the problem: 1. Logon 2. Wallpaper is not set 3. Logon on again and wallpaper appears - but disappear if device sleeps. What is the expected behavior? Wallpaper appears first time for all users on all devices. What went wrong? Appearance of the wallpaper seems to depend on whether the to policy to wipe user data on logoff is set. If this policy is set the wallpaper does appear on first login to a device. If it is not set then the wallpaper normally does not appear until the user logs off then on again. In addition, if a device locks and then is woken - the wallpaper often reverts to the default for the specific ChromeOS device. The user cannot change the wallpaper as expected - but the domain deployed wallpaper does not always apply and its appearance is sporadic and seems linked to the wipe user data policy. Did this work before? No Chrome version: 54.0.2840.93 Channel: stable OS Version: 8743.83.0 Flash Version: Shockwave Flash 23.0 r0 I'd say its got worst in recent revisions of ChromeOS.
,
Nov 28 2016
,
Nov 29 2016
Not able to reproduce. If you think these are not the exact steps, please provide very detail in steps. M ChromeOS Chrome ARC Type Channel 54 8743.87.0 54.0.2840.101 3505285 release stable Device: Peppy MP Pre-condition: On Cpanel: 1. ensure User Settings > Force Ephemeral Mode is set to "Erase all local user data". 2. ensure User Settings > General > Wallpaper is set to a custom wallpaper. Procedure: 1. The very first time (never sign-in before) sign-in to a managed user account which has the pre-condition as described in above. Results: Observed Wallpaper was updated to the custom wallpaper in step 2 in Pre-condition after the sign-in. From now on, any or many of sign-out and sign-in or log-out and log-in to the user account, it always shows the custom wallpaper.
,
Nov 29 2016
,
Nov 30 2016
Its pretty random. It happens most often when a device is not set to wipe local user data. 1st time a user signs in wallpaper tends not to apply. Logoff and back on and they get it. However, the issue with it disappearing on the lock screen seems to have vanished. We do see users around the place without the school wallpaper - but as I say - its sporadic.
,
Dec 14 2016
Polite ping, any updates to share? Raised by another customer (EDU).
,
Jan 20 2017
Any news on this? It is still an issue on version 55 ?
,
Feb 7 2017
,
Feb 7 2017
Yes its still an issue. The first time a user logs into a device that is not set to wipe user data, the desktop wallpaper almost always fails to appear - but they cannot change it. Log off and back on and it appears. If the devices is set to wipe local data on logoff, then it sometimes appears. Also the policy is very sensitive to the resolution of the jpg. I have one last week that was 1980x1020 - applied in the management console - verified and you could preview it - but did not apply until I spotted the error and changed it to 1920x1080.
,
Mar 1 2017
I can reproduce the issue in M57.0.2987.75:9202.37.0 beta and M58.0.3021.0:9325.0.0 dev on both peppy and lulu when network connection is via WIFI and not Ethernet. I used three user accounts in three separate OUs. When network is connected via Ethernet (using USB adapter to RJ45), after enrollment, I signed in one user account and immediately the custom wallpaper was refreshed. Signed out and signed in using the second user account and saw the same result. Repeated with the third account and saw the same result as well. No issue here. When network was connected via WIFI, I saw the mentioned issue intermittently but not once could all three user accounts got the custom wallpaper in the first sign-in. Most of the time, each user account required the second or third sign-in to display the custom wallpaper. Sometimes, when the issue persisted, removing and re-adding the user at sign-in page might help. Network speed seems to be a factor and I suspect the issue might be caused by a racing condition.
,
Mar 1 2017
,
Mar 8 2017
This is not really my area. Reassigning to dskaram@ for further triage.
,
Dec 19 2017
Hi - we are starting to see issues with our student accounts and chromebooks not receiving the standard wallpaper. This is causing issues with our classrooms because it distrupts class time and causes distractions for students. Please work on resolving this issue!
,
Dec 20 2017
,
Jan 4 2018
Hi mpeskay@ Do you have the build version information? Does this happen on any particular models of Chromebook?
,
Jan 4 2018
i tested across a few models (ASUS C202; ASUS C302 (flip) - all on latest ChromeOS builds (we ran updates during testing to ensure devices were on latest release. <http://www.kippla.org> <https://www.facebook.com/kipplaschools> <https://twitter.com/kipplaschools> <https://www.instagram.com/kippla_schools/> <https://www.linkedin.com/company/420856/> <https://vimeo.com/kipplaschools> <https://www.youtube.com/user/KIPPLASchools> Matthew A. Peskay Chief of Innovation & Technology 3601 East 1st Street | Los Angeles, CA 90063
,
Jan 6 2018
As tested in M63.0.3239.132 10032.79.0 stable lulu and M64.0.3282.65 10176.34.0 beta lulu, the issue persists. I signed in three users each in different OU and none showed custom wallpaper in first sign-in. On the second try, only the first of the three users showed the custom wallpaper. The other two would never show custom wallpaper despite several sign-out and sign-in. When I changed the custom wallpaper in CPanel, the user in that OU would automatically refresh and load the new wallpaper after a short while.
,
Mar 20 2018
+1 - wallpaper only applies after second login and without “delete user info” setting enabled. Wallpaper policy is shown properly in chrome://profile but not applied.
,
Jun 23 2018
,
Aug 23
,
Dec 14
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by krishna...@chromium.org
, Nov 22 2016