After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 688862 - Low res icons/grouping failure hostname change
Low res icons/grouping failure hostname change
Status: RESOLVED DUPLICATE of bug 688716
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-22 10:44 UTC by Vít Ondruch
Modified: 2012-11-22 10:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vít Ondruch 2012-11-22 10:44:36 UTC 
This was initially reported as rhbz#817500 [1]

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
gnome-shell-3.6.2-2.fc18.x86_64

But I observed the same issues in F16 with gnome 3.2 and F17 with gnome 3.4


How reproducible:
Always


Steps to Reproduce:
1. Boot computer connected by wire to the network.
2. Disconnect cable.
3. Wake up the computer.
  
Actual results:
Newly executed applications uses just low resolution icons and they are not properly grouped.

Expected results:
High resolution icons are used and application windows are properly grouped

Additional info:
Seems to be related to the hostname changes. It is easy to reproduce using:

# echo "foo" > hn
# hostname -F hn



[1] https://bugzilla.redhat.com/show_bug.cgi?id=817500
Comment 1 Allan Day 2012-11-22 10:54:57 UTC 
Just to clarify - does this happen with all applications?
Comment 2 Rui Matos 2012-11-22 10:57:46 UTC 
(In reply to comment #0)
> Seems to be related to the hostname changes. It is easy to reproduce using:
> 
> # echo "foo" > hn
> # hostname -F hn

Probably bug 688716 then.

*** This bug has been marked as a duplicate of bug 688716 ***