Bug 1366766
Summary: | Lock screen wallpaper gets automatically sets to Desktop Background | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | ptoshniw |
Component: | gnome-shell | Assignee: | Florian Müllner <fmuellner> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | ayadav, bmilar, ccopello, chrislf, cww, fmuellner, jkoten, mboisver, mclasen, oliver, rstrode |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 22:41:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1298243, 1369100 |
Description
ptoshniw
2016-08-12 18:23:35 UTC
*** Bug 1374277 has been marked as a duplicate of this bug. *** Is there any update on the issue? I am planing to move over 1000 users to RHEL 7.2 (from 7.1) and because the lock screen is set to a default background it will change all user backgrounds. Not the greatest experience, especially when they try to set the background again and it will be overwritten on next reboot with the lock screen background. Thanks Oliver I can see this is fixed in https://bugzilla.gnome.org/show_bug.cgi?id=741453. In which version is it fixed for RHEL 7.2? The fix for this particular defect has not yet been integrated into a release of Red Hat Enterprise Linux 7. It is currently being evaluated for inclusion in a future Red Hat Enterprise Linux 7 synchronous update. *** Bug 1405900 has been marked as a duplicate of this bug. *** What is the meaning of ON_QA? Does it mean solved or pending? Thanks a lot. ON_QA means that a fix for this issue is currently committed and built, and QE is evaluating the fix to ensure it works and doesn't cause any regressions. Thanks a lot, I am sorry about the next step, will the patch be integrated in future version? and which version it will be? The fix for this issue is currently targeting Red Hat Enterprise Linux 7.4. The fix should be available in package gnome-shell-3.22.3-1.el7 or later. *** Bug 1435437 has been marked as a duplicate of this bug. *** I can change the desktop and lock screen backgrounds independently on gnome-shell-3.22.3-14.el7. Verified. (In reply to Michael Boisvert from comment #18) > I can change the desktop and lock screen backgrounds independently on > gnome-shell-3.22.3-14.el7. Verified. Hi Michael, just want to confirm that after restart, the lock screen background isn't rendered as the desktop background. Thank you. (In reply to Chuck Copello from comment #19) > (In reply to Michael Boisvert from comment #18) > > I can change the desktop and lock screen backgrounds independently on > > gnome-shell-3.22.3-14.el7. Verified. > > Hi Michael, just want to confirm that after restart, the lock screen > background isn't rendered as the desktop background. Thank you. Correct, multiple restarts combined with multiple different lock screens. The lock screen wallpaper was never automatically used as the desktop wallpaper. (In reply to Michael Boisvert from comment #20) > (In reply to Chuck Copello from comment #19) > > (In reply to Michael Boisvert from comment #18) > > > I can change the desktop and lock screen backgrounds independently on > > > gnome-shell-3.22.3-14.el7. Verified. > > > > Hi Michael, just want to confirm that after restart, the lock screen > > background isn't rendered as the desktop background. Thank you. > > Correct, multiple restarts combined with multiple different lock screens. > The lock screen wallpaper was never automatically used as the desktop > wallpaper. Excellent! Thank you! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2098 |