Red Hat Bugzilla – Bug 817500
Low res icons/grouping failure hostname change
Last modified: 2014-02-05 06:57:23 EST
Description of problem:
Application windows grouping is broken as well as just low resolution icons are used when computer is woke up disconnected.
Version-Release number of selected component (if applicable):
$ rpm -q gnome-shell
But I observed the same issues in F16 with gnome 3.2
Steps to Reproduce:
1. Boot computer connected by wire to the network.
2. Disconnect cable.
3. Wake up the computer.
Newly executed applications uses just low resolution icons and they are not properly grouped.
High resolution icons are used and application windows are properly grouped
Created attachment 581163 [details]
Mix of hi-res and low-res icons
The attached screenshot shows how the high resolution and low resolution icons get mixed. Also note that GVIM is not properly grouped.
Not sure if that might be related to hostname change or something similar. Why it should have influence is not clear to me.
Can you attach the result of running xprop and clicking on each gvim window before and after waking up?
(The low-res icons are the same problem as the grouping failure - if you have a gvim window which is not associated with the gvim application, it will get whatever icon gvim set directly on the window, which will not match the application icon and will often be low-res)
Created attachment 581200 [details]
After wake up
Created attachment 581201 [details]
The VIM's were not in the same state editing the same file, hope it doesn't matter.
The two files are byte-per-byte identical, including:
WM_NAME(STRING) = "rubygem-backports.spec (~/fedora-packages/rubygem-backports) - GVIM"
are you sure you didn't attach the same file twice, since you say "The VIM's were not in the same state editing the same file".
Created attachment 581214 [details]
After wake up
Ups, sorry. Hope I'll do better this time
Created attachment 581215 [details]
After wake up - 2nd instance
I add also ouptut of second instance of GVIM after wake up if that helps, since the instances are not matched among themselves
Same issue here, started occuring after hostname change. The applications that were run before the change still have high-res icons, but anything run after the hostname was changed has low-res icons.
BTW it is easy to reproduce:
# echo "foo" > hn
# hostname -F hn
Confirming I've seen this issue. I can't really understand why a desktop environment breaks on hostname changes. I've seen such bugs years ago with XFCE and was equally surprised.
It appears that this bug has just been fixed upstream:
Would it be possible to backport if for F18 and possible older releases? It looks to be tiny patch. Thank you.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.