Description of problem: I tested live gnome and kde images (tc7, rc1), also this is present on installed system, there are some small artifacts (two white "triangles" (or some other similar shapes) on the top left corner of the background. Looks like only 'tv-wide' and 'wide' are affected, other two look good (normalish and standard). location: /usr/share/backgrounds/f21/default/ Version-Release number of selected component (if applicable): f21-backgrounds-base-20.91.0-2.fc21.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Confirmed I see this.
*** Bug 1161944 has been marked as a duplicate of this bug. ***
Proposed as a Freeze Exception for 21-final by Fedora user jreznik using the blocker tracking app because: There are know artifacts on the F21 wallpaper (wide versions). Design team is working on fix, unfortunately, we didn't have it before freeze.
Created attachment 959066 [details] new wallpapers with updated artwork from gnokii and artifacts cleaned Hi, here is gnokii's iteration on the wallpapers and the artifacts are gone in it.
Martin can you please update f21-background package with artwork provided above? I already proposed it for freeze exception.
Discussed in 2014-11-19 blocker review meeting. Voted as an Accepted Freeze Exception: This is a low risk change.
f21-backgrounds-21.1.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/f21-backgrounds-21.1.0-1.fc21
Package f21-backgrounds-21.1.0-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing f21-backgrounds-21.1.0-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15562/f21-backgrounds-21.1.0-1.fc21 then log in and leave karma (feedback).
f21-backgrounds-21.1.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.