Gnome-Shell 3.10 staging HUGE fonts, cursors, icons

[mightymouse2045]

Ubuntu Gnome 13.10 from daily build

Installed all updates. Added Gnome3-Next PPA and dist-upgrade and reboot. Have Gnome-Shell 3.10 fonts etc are normal. Display shown as Samsung 55".

Installed Gnome3-Staging PPA and dist-upgrade and reboot. Have latest Gnome-Shell 3.10 fonts etc are HUGE. Display shown as Samsung 7".

This is affected at the GDM login screen so is not user related.

Xorg.0.log from the first boot with Next PPA attached.
Xorg.0.log from the first boot with Staging PPA attached.

The only things I can see are different magic numbers, and everything else looks the same....

Can you let me know what other logs I can look in please so I can get this resolved? Also by using gnome-tweak and scaling the DPI it gets the fonts and windows back to normal but not the cursors and icons.

[mightymouse2045 (eagleeyes426)]

PS I don't think the icons are affected - it could just be the fonts and cursors, but hard to tell when the windows are so HUGE

[mightymouse2045 (eagleeyes426)]

I also noticed this on doing the dist-upgrade to the staging PPA:

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

On running the command it tells me I need to install libgdk-pixbuf2.0-dev

apt-get install libgdk-pixbuf2.0-dev
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
root@mePC:/home/ph# apt-get install libgdk-pixbuf2.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libglib2.0-dev libpcre3-dev libpcrecpp0 libpng12-dev libpthread-stubs0 libpthread-stubs0-dev
  libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev pkg-config x11proto-core-dev
  x11proto-input-dev x11proto-kb-dev xorg-sgml-doctools xtrans-dev zlib1g-dev
Suggested packages:
  libglib2.0-doc libxcb-doc
The following NEW packages will be installed:
  libgdk-pixbuf2.0-dev libglib2.0-dev libpcre3-dev libpcrecpp0 libpng12-dev libpthread-stubs0
  libpthread-stubs0-dev libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev pkg-config
  x11proto-core-dev x11proto-input-dev x11proto-kb-dev xorg-sgml-doctools xtrans-dev zlib1g-dev

[Lars Jarlvik (lars-jarlvik)]

Updated to Gnome 3.10 on my Arch Linux box which is connected to a 58" plasma screen yesterday. I also noticed that everything looked huge almost like the display was showing a 640x480 resolution but sharp.

As mentioned in previous post it reported my display as Samsung 7" in my Display Settings

[Tim Lunn (darkxst)]

gnome3-staging uses the new Mutter DisplayConfig API. It might be worth filing an upstream bug against mutter

[mightymouse2045 (eagleeyes426)]

Is that something for me to do or is that just a general comment for someone else cc'd?

[mightymouse2045 (eagleeyes426)]

Created bug in bugzilla upon request:

https://bugzilla.gnome.org/show_bug.cgi?id=712529

[mightymouse2045 (eagleeyes426)]

As you can see from this output which gives a very detailed view of EDID, on
line 219 the Maximum Image Size is 1210 mm x 680 mm- that is correct and
equates to 55" (which is the size of my monitor).

However from line 248 under detailed timings the Image size is listed as 160 mm
x 90 mm (or 7").

It also states on line 217: Prefer first detailed timing : Yes

So what is happening is the Gnome Settings Daemon from the next ppa is using
xrandr direct (as I've been told), and setting the correct display size of 55"
from the Maximum Image Size and DPI is working as expected.

But the new way g-s-d is getting the display size is from the reported Image
Size as obtained from X which is set by the detailed timings. In this case the
EDID displays the Image size as 160 mm x 90 mm (7") and hence the display is
being set as 7"

Now this seems to be the case for 3 other people with 3 different brands of
large screen monitors, which seems to indicate that Image Size from EDID for
the detailed timings are set to a smaller than actual value for whatever
reason.

As you can also see starting from line 1040, I attempted to work around this
with a custom mode in xorg.conf based on the 1st detailed mode and it says:

Mode is rejected: Only EDID-provided modes are allowed on
SAMSUNG (DFP-1) (continuous frequency modes not allowed).

So some solutions as I see them:

1. Create a custom EDID which is a pain in the ass

2. Have Gnome Settings Daemon force set the display size from the Maximum Image
Size with xrandr, whilst taking DPI, hsync, vsync etc from the values X obtains
from EDID.

3. Have X do that instead of g-s-d.

4. Temporarily patch g-s-d to force set it for now and ensure wayland supports
this in the future.

EDIT:

Option 1 is not an option as the edid block doesn't contain the required
information:

This is an ascii of the extracted EDID:

Section "Monitor"
    # Block type: 2:0 3:fd
    # Block type: 2:0 3:fc
    Identifier "SAMSUNG"
    VendorName "SAM"
    ModelName "SAMSUNG"
    # Block type: 2:0 3:fd
    HorizSync 26-81
    VertRefresh 24-75
    # Max dot clock (video bandwidth) 150 MHz
    # Block type: 2:0 3:fc
    # DPMS capabilities: Active off:no Suspend:no Standby:no

    Mode "1920x1080" # vfreq 60.000Hz, hfreq 67.500kHz
        DotClock 148.500000
        HTimings 1920 2008 2052 2200
        VTimings 1080 1084 1089 1125
        Flags "+HSync" "+VSync"
    EndMode
    Mode "1920x1080" # vfreq 50.000Hz, hfreq 56.250kHz
        DotClock 148.500000
        HTimings 1920 1968 2012 2640
        VTimings 1080 1084 1089 1125
        Flags "+HSync" "+VSync"
    EndMode
    # Block type: 2:0 3:fd
    # Block type: 2:0 3:fc
EndSection

So the max image size is coming from an extension block and I don't know how to
edit that to create a custom one and have xorg.conf point to it.

Please refer to bugzilla for further updates

[mightymouse2045 (eagleeyes426)]

why?

[mightymouse2045 (eagleeyes426)]

Marked as duplicate of this bug:

https://bugzilla.gnome.org/show_bug.cgi?id=709859

[Bruce Pieterse (octoquad)]

Please confirm if you are still experiencing this problem with latest version of Ubuntu Gnome. This was fixed in Gnome 3.12 .