Bug 1749086

I dream of a day when new backgrounds can land before freeze and there is no artificial rush to get this in.  :-/

Sorry, meant to add that to the linked bug.

still, in the sad humdrum world in which we live, can this get done please? :)

Discussed during the 2019-09-09 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criterion:

"The default desktop background must be different from that of the last two stable releases" (for the release-blocking KDE desktop)

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-09-09/f31-blocker-review.2019-09-09-16.00.txt

FEDORA-2019-eaa33dc3b2 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-eaa33dc3b2

Thanks for the assist, I've been unavailable for @dayjob conference

kde-settings-31.0-1.fc31 has been pushed to the Fedora 31 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-2019-eaa33dc3b2

Sigh, we're still missing something here. With kde-settings-31.0-1.fc31 and f31-backgrounds-31.0.2-3.fc31 (which I built with one commit from 'upstream' that fixed a stray '30' that wasn't yet in the downstream package), I still get the "Next" background for a logged-in user session. I get the F31 background for the lock screen and the SDDM screen, though. Not really sure what's missing.

rather than saying "still get the"...I should say "I get the Next background". Previously we got the F30 background, now we get the 'Next' one. This means we're not technically violating the Beta criteria any more which is good, but we should still fix this so we actually get the F31 background.

I guess the metadata.desktop in f31-backgrounds-kde is not valid.

well, per https://github.com/fedoradesign/backgrounds/issues/16 there are actually *two of them*...

indeed, desktop-file-validate passes on /usr/share/plasma/desktoptheme/F31/metadata.desktop but fails on /usr/share/plasma/desktoptheme/F31/metadata.desktop . If I overwrite /usr/share/plasma/desktoptheme/F31/metadata.desktop with a copy of /usr/share/plasma/desktoptheme/F31/metadata.desktop and reboot...

nope, I still get the Last background. Sigh.

As discussed in the Go/No-Go Meeting today, this is moved to Final blocker (as we're not using the F30 background any more, but aren't using the correct F31 background). Also accepted as an FE for Beta, in case we slip and figure out the fix in the meantime, obviously it'd be nice to ship Beta with the *correct* background.

kde-settings-31.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Re-opening because the bug isn't really fixed yet, we don't have the *right* background.

Appears f31-backgrounds-kde config file
/usr/share/plasma/desktoptheme/F31/metadata.desktop
is malformed, some section headings were renamed from f30's version:
[Settings] => [X-Settings]
[Wallpaper] => [X-Wallpaper]
[Branding] => [X-Branding]
[ContrastEffect] => [X-ContrastEffect]

this is most likely why it doesn't work as expected.   I'll go test that theory now.

I don't think it is. I've tried changing both metadata files to have the same contents as the other, but either way around it still doesn't work.

Confirmed, once I put those back to match f30, things work expected in my quick testing (for me).  My testing on f30:  
1.  edit plasmarc:
[Theme]
name=F31

2.  Edit F31/metadata.desktop as described

3.  Create new user

4.  Login as new user, see them using the expected F31 wallpaper

Oh wait. You have to create a new user? The fix won't apply to an existing user?

Right, Note: I think this test will not work:

login as new user, see wrong wallpaper

edit stuff, whether that's plasmarc or F31/metadata.desktop

login as that same user, still see wrong wallpaper

(because I think it only chooses the plasma defaults on first login)

or you can simulate a first login by deleting that users' ~/.config/plasma*  files

ah well, that explains a lot.

FEDORA-2019-6004dba64a has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-6004dba64a

There a lot of taskotron errors reported from rpmgrill.
https://taskotron.fedoraproject.org/artifacts/all/88bee3c8-d5be-11e9-a807-52540077ca13/tests.yml/rpmgrill.json

These are all bogus. See https://bugs.kde.org/show_bug.cgi?id=411876 .

f31-backgrounds-31.0.2-4.fc31 has been pushed to the Fedora 31 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-2019-6004dba64a

FEDORA-2019-d7fbbec3ae has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d7fbbec3ae

(In reply to Adam Williamson from comment #24)
> These are all bogus. See https://bugs.kde.org/show_bug.cgi?id=411876 .

Still with the new update, of course.

f31-backgrounds-31.0.3-1.fc31 has been pushed to the Fedora 31 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-2019-d7fbbec3ae

f31-backgrounds-31.0.3-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.