Red Hat Bugzilla – Bug 963841
update logo on login screen.
Last modified: 2015-01-09 19:03:20 EST
Allan Day and Ryan Lerch have been collaborating on a new logo for the login screen.
We should use it.
Proposing as Beta freeze exception, we're still early in freeze and it'd be nice to get the branding straight. The update for this is https://admin.fedoraproject.org/updates/gdm-220.127.116.11-2.fc19 .
Do we have screenshot? But I'd say I'm +1 FE for tested change.
+1 for freeze exception
Jaro: it's barely distinguishable, to be honest. From what I can see, the difference is that the old package used /usr/share/fedora-logos/fedora_logo_darkbackground.svg , the new one uses /usr/share/pixmaps/fedora-gdm-logo.png . The new one appears to be a fairly low-res png render of the old one, with the "tm"s removed.
Discussed at 2013-05-20 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-20/f19beta-blocker-review-7.2013-05-20-16.07.log.txt . Rejected as an FE issue: as per c#4 the proposed change seems to be microscopic and arguably a downgrade, so a) we don't see much benefit from pulling it in, and b) that seems to indicate some degree of confusion among devel / artwork team about what it is we want to do exactly, and it seems safer to resolve that post-Beta now we're close to the Beta release.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Whatever was going on here, I don't think we need the bug open any more.