Bug 1471919

Summary: Close button on windows in Activities Overview is not visible but still works
Product: [Fedora] Fedora Reporter: Michael Cronenworth <mike>
Component: gdk-pixbuf2Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: fmuellner, jan.public, klember, mclasen, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 12:10:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Michael Cronenworth 2017-07-17 16:28:30 UTC
Created attachment 1299949 [details]
Screenshot

Description of problem:
When opening the Gnome Shell Activities view the small "X" circle button is not visible anymore on top right corner of the window screenshot of a running application. I'm attaching a screenshot with a red circle highlighting the area where the close window button was normally visible. If you click your mouse in the area the button would be the window is closed.

Version-Release number of selected component (if applicable):
gnome-shell-3.24.2-1.fc26.x86_64

How reproducible: Always


Steps to Reproduce:
1. Open Activities view
2.
3.

Actual results: No icon visible.
Everytime I open the "Activities" view my system log is spammed with a dozen duplicate messages:
Jul 17 10:32:04 melchior.cchtml.com gnome-shell[1725]: Failed to load resource:///org/gnome/shell/theme/close-window.svg: Unrecognized image file format


Expected results: Icon visible. No log spam.


Additional info:
https://bugzilla.gnome.org/show_bug.cgi?id=769524

Comment 1 Michael Cronenworth 2017-07-21 15:01:19 UTC
This problem is only present on one of three systems I use regularly. On the problem system: The GdkPixbuf SVG loader is present just as it is on the other two systems. However, I notice that it is not loaded into memory as it is on the two working systems.

I then checked out the loader.cache. Bingo. The cache had been regenerated recently, but was smaller than the other systems that work. After regenerating the cache (gdk-pixbuf-query-loaders-64 --update-cache) and restarting gnome-shell the SVG icons appear in Activities and the log messages stop. The 32-bit cache was correct.

Before:
-rw-r--r--. 1 root root 3035 Jul 11 21:05 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache

After:
-rw-r--r--. 1 root root 3355 Jul 21 09:52 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache

I would assume the gdk-pixbuf-query-loaders did not get called when the SVG loader was installed? An issue during the upgrade from Fedora 25 to Fedora 26?

Comment 2 Kalev Lember 2017-08-16 14:17:51 UTC
Hm, not sure what happened, but the way it should work is that librsvg2 drops the loader in %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders and then these two file triggers in gdk-pixbuf2 should take care of rebuilding the cache:

%transfiletriggerin -- %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders
gdk-pixbuf-query-loaders-%{__isa_bits} --update-cache

%transfiletriggerpostun -- %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders
gdk-pixbuf-query-loaders-%{__isa_bits} --update-cache

Comment 3 Jan Vlug 2017-09-09 08:39:19 UTC
I have this issue as well. I have also this error in my logs:

Failed to load resource:///org/gnome/shell/theme/close-window.svg: Unrecognized image file format

Comment 4 Jan Vlug 2017-09-09 09:02:07 UTC
Also for me the issue was resolved after regenerating the cache:

[root@nyx ~]# ls -slah /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 3.0K 25 aug 20:20 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 2.8K 25 aug 20:20 /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
[root@nyx ~]# gdk-pixbuf-query-loaders-32 --update-cache
[root@nyx ~]# gdk-pixbuf-query-loaders-64 --update-cache
[root@nyx ~]# ls -slah /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 3.3K  9 sep 10:54 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 2.8K  9 sep 10:53 /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache

Comment 5 Fedora End Of Life 2018-05-03 08:45:56 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 6 Fedora End Of Life 2018-05-29 12:10:27 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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
bug.

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