Bug 1311855 - Warning / error overlays not shown on spoke icons
Warning / error overlays not shown on spoke icons
Product: Fedora
Classification: Fedora
Component: distribution (Show other bugs)
x86_64 All
unspecified Severity low
: ---
: ---
Assigned To: Václav Pavlín
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-25 03:35 EST by Adam Williamson
Modified: 2017-12-12 06:04 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-12 06:04:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Williamson 2016-02-25 03:35:07 EST
In current Rawhide installer images, it seems like the 'warning' / 'error' overlays that are supposed to appear on the icons for spokes that require action or hit an error condition don't appear.

This broke all the Rawhide openQA tests today, because one of our matches is on the 'root password' spoke on the during-install hub (it expects to see the orange triangle indicating the root password needs to be set). See e.g.:


note the triangle is missing from the root password spoke icon.

This was OK with the 2016-02-22 nightly:


we've switched from Pungi 3 to Pungi 4 since then, I don't *think* that's relevant but it could be somehow, I guess.
Comment 1 Adam Williamson 2016-02-25 03:41:47 EST
GTK+ 3.19.10 landed between 02-22 and 02-25, so that's the obvious candidate here.
Comment 2 David Shea 2016-02-25 17:00:10 EST
Do you have the logs from the compose that made that iso? It looks like the problem is that the emblems we're trying to add are SVG, and /usr/lib64/gdk-pixbuf-2.0/2.0.10/loaders/libpixbufloader-svg.so is not there. That's mighty strange, since that file is provided by librsvg2 which was last built on 4 Feb, for the mass rebuild.
Comment 3 Adam Williamson 2016-02-25 18:56:12 EST
ah, so it may be compose-related indeed. As it's a shiny Pungi 4 compose, the logs are all there along with the compose:


I do see 'librsvg2' being installed in https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160224.n.0/logs/x86_64/buildinstall-Everything.x86_64.log and https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160224.n.0/logs/x86_64/buildinstall-Server.x86_64.log .

is "/usr/lib64/gdk-pixbuf-2.0/2.0.10/loaders/libpixbufloader-svg.so" just a typo in your comment? Because it's 2.10.0, not 2.0.10.
Comment 5 Adam Williamson 2016-02-25 18:59:08 EST
Goddamn it, I really stink at this. openQA ran on 20160225, not 20160224. And indeed, in the 20160225 logs, librsvg2 is missing for some reason:

running runtime-install.tmpl
2016-02-25 02:54:05,374: installpkg librsvg2 failed: no package matched
installpkg librsvg2 failed: no package matched


indeed, it's listed in the compose 'changelog' as "dropped":


perhaps it got orphaned? Let me take a look into it.
Comment 6 Adam Williamson 2016-02-25 19:08:14 EST
<adamw> dgilmore: librsvg2 was "dropped" from rawhide, according to that
 which breaks anaconda a bit
<adamw> it doesn't appear to be a dead package, i don't see an orphan notification for it..
<nirik> it wasn't in the f25 tag
<nirik> until we fixed it
<adamw> so should be fixed in next compose?
<nirik> hopefully yes
<adamw> ok, thanks
Comment 7 Jan Kurik 2016-07-26 01:11:16 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 8 Fedora End Of Life 2017-11-16 14:40:33 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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 25 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.
Comment 9 Fedora End Of Life 2017-12-12 06:04:19 EST
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.