Bug#239448: Getting closer. It isn't libxft2 after all?

[Scott Robinson]

After checking all the dependencies, I decided to check the ancestry.
Specifically, libgtk2.0-0. I ran:

apt-get --reinstall install libgtk2.0-0

This has apparently solved the firebird crashing and font sizing issues.
However, when running my normal test:

GDK_USE_XFT=1 gcalctool

The fonts now appear incredibly small. An example screenshot is available
here:

http://tranzoa.net/~scott/small-fonts.jpeg

This struck me as a DPI issue so I opened the GNOME Font preferences,
clicked on "Details...", and found my Resolution listed as 50 dpi. This
seems small to me; but, I don't really know.

I remembered that The Gimp somehow can automatically determine the DPI of
your monitor, though it warns the values are not necessarily accurate. I
figure it got it from X somehow...

scott@tara:~$ [0] xdpyinfo
...
screen #0:
dimensions: 1600x1200 pixels (301x231 millimeters)
resolution: 135x132 dots per inch
...

So I set the Resolution in GNOME to 130 dpi. gcalctool appeared larger but
not necessarily fixed.

I'm now at a stand still. The problem does not appear to be libxft2, so I
should reassign the bug. But, I don't know where to. This appears to be
either a libgtk2.0-0 package bug or one af the many GNOME packages...

I checked if the issue is from my account in particular (maybe a setting
didn't migrate properly) and created a new user. Logging into a freshly
created user causes the same problem to occur. Furthermore, the problem
occurs when running both my user and the new user in Failsafe GNOME from
gdm.

Any advice on how to proceed would be much appreciated!

Scott.

--
http://quadhome.com/ - Personal webpage
http://tranzoa.net/ - Corporate webpage

[Scott Robinson]

The problem is not with libxft2. It is with GNOME. Specifically, capplets
and capplets-data. This bug should be re-assigned, though I'm not certain
how the maintainer would fix it? (The depends has already been added to
capplets-data.)

Quick answer:

apt-get install --reinstall capplets-data

Long answer:

My GNOME schemas were messed up because of an out of order install of the
capplets packages.

There was a period of time where gnome-control-center did not require
capplets and capplets-data. During that period of time, I was sent an IM
from a friend noting that gnome-control-center would be giving me problems
unless I apt-get'ed capplets-data. (this was passed on from #debian)

I proceeded to do this, but was confused by the requisite of the -data
package without the base package. I installed the base package afterwards.
gnome-control-center, as installed on my system, did not require either of
these!

It was only in this latest update cycle, with gnome-control-center updated,
that the issue finally reared its head. I have tested this by rolling back
to versions in my archives.

The upgrade path was as thus:

[gnome-control-center (1:2.4.0-5)] (Initial State)
capplets-data (2.4.0-7) -> capplets (2.4.0-7) (BROKEN!)
gnome-control-center (2.4.0-9), capplets (2.4.0-9), capplets-data (2.4.0-9) (FIXED!)