Description of problem:
When F29 KDE Live is booted, the default background is the one from F28. That violates:
"The default desktop background must be different from that of the last two stable releases. "
Version-Release number of selected component (if applicable):
$ rpm -qa | grep background
I am seriously *so* sick of this dumbass thing happening every time. We already *had* an FE bug to get the new backgrounds in. It should not take two freaking FE bugs per cycle to change the damn backgrounds.
kde-settings-29.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5f78d4e856
Discussed at 2018-09-13 Fedora 29 Beta Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-09-13/f29-beta-go_no_go-meeting.2018-09-13-17.00.html . It was generally agreed that this is a violation of the criteria as they stand, but there was a split between those voting to accept it as a blocker on that basis (+4) and those who would prefer to change the criterion somehow to no longer cover this - either by moving it to Final, or by having it not cover KDE (-3). As the vote was close to a tie with certainly no clear winner, that was counted as no decision, and the bug remains a proposed blocker. However, there was a clear consensus that it should be at least a freeze exception, so it is accepted as that.
kde-settings-29.0-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-5f78d4e856
f29-backgrounds-29.0.0-3.fc29 kde-settings-29.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5f78d4e856
f29-backgrounds-29.0.0-3.fc29, kde-settings-29.0-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.