Bug 123156 - kde dpi-problem (related to gtk?)
Summary: kde dpi-problem (related to gtk?)
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-06 10:27 UTC by Anders Storsveen
Modified: 2006-03-07 21:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Storsveen 2006-03-06 10:27:39 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    Gentoo Packages
OS:                Linux

The fonts (dpi) gets messed up after starting gtk apps. started out fine (look at taskbarfonts), but after starting a gtk app they get too small, look at konq's menubar (in the top), they're originally the same size:

http://huldreveien.generation.no/~wakko/secondscreen1.jpg

Seems like gtk somehow messes up the fonts....
Comment 1 Anders Storsveen 2006-03-06 10:39:13 UTC
just to clear stuff up, all my fonts (except desktop fonts) are size 10 and my lcd has correct sizes, even on gtk apps.
Comment 2 Stephan Kulow 2006-03-06 11:31:07 UTC
gtk apps start gnome-settings-daemon that will set the DPI number to 96. But you need to have a very odd resolution to make this a problem. What is your dpi number before you start gtk apps? (xdpyinfo | grep res)

And yes, the problem is known, but hardly a KDE bug ;(
Comment 3 Anders Storsveen 2006-03-06 12:34:44 UTC
This is my output from dpyinfo, this is the numbers I have WHEN the problem is active, nothing here that says 96...


screen #0:
  print screen:    no
  dimensions:    1400x1050 pixels (418x314 millimeters)
  resolution:    85x85 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16

screen #1:
  print screen:    no
  dimensions:    1280x1024 pixels (612x459 millimeters)
  resolution:    53x57 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32
Comment 4 Anders Storsveen 2006-03-06 12:56:35 UTC
edit: start gnome-font-properties just to check, then suddenly my fonts were back to normal I think... It also changed my mouse settings and whatnot... :/ xdpyinfo shows the same output though.

wakko     7560  0.2  1.2  43588 12588 ?        Sl   12:51   0:00 /usr/libexec/gnome-settings-daemon --oaf-activate-iid=OAFIID:GNOME_SettingsDaemon --oaf-ior-fd=25

it seems that settingsdaemon started when I started the fontconfig app. So has to be something else wrong then? start stuff like xchat-2 didn't start it.
Comment 5 Stephan Kulow 2006-03-06 13:01:35 UTC
well, you will know best if your screen 1 has a height of 459 millimeters. That's pretty huge, so don't be suprised fonts are small. Either your monitor lies or you have a bug in your X server - neither is KDE.
Comment 6 Anders Storsveen 2006-03-06 13:08:18 UTC
well, screen 1 has a sticker on it saying 50CM 19 inch... so seems to be right... but isn't the point with DPI that fonts should have same size if the DPI is right... but might be that the calculation of DPI from res and millimeters is wrong? could it be my crappy fglrx drivers?
Comment 7 Stephan Kulow 2006-03-06 13:22:27 UTC
19 inch monitors are around 400mm x 300mm - that's 60% of what your monitor says it is - explaining why your 10pt are 7pt in reality.
Comment 8 Anders Storsveen 2006-03-06 13:30:44 UTC
Dimensions  	452 mm (W) x 455 mm (H) x 478 mm (D)
17.8" (W) x 17.9" (H) x 18.8" (D)

this is from the eizo page... where does the problem lie then ? EDID info or what?

snip from my Xorg.0.log

(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: EIZ  Model: 1014  Serial#: 1418236009
(II) fglrx(0): Year: 2212  Week: 63
(II) fglrx(0): EDID Version: 1.1
(II) fglrx(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) fglrx(0): Sync:  Separate  Composite  SyncOnGreen
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 36  vert.: 27
(II) fglrx(0): Gamma: 1.80
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): redX: 0.625 redY: 0.340   greenX: 0.280 greenY: 0.600
(II) fglrx(0): blueX: 0.155 blueY: 0.070   whiteX: 0.283 whiteY: 0.298
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 720x400@88Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@87Hz (interlaced)
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1024  vsize 768  refresh: 85  vid: 22881
(II) fglrx(0): #1: hsize: 1152  vsize 864  refresh: 75  vid: 20337
(II) fglrx(0): #2: hsize: 1152  vsize 864  refresh: 85  vid: 22897
(II) fglrx(0): #3: hsize: 1280  vsize 1024  refresh: 85  vid: 39297
(II) fglrx(0): #4: hsize: 1600  vsize 1200  refresh: 65  vid: 17833
(II) fglrx(0): #5: hsize: 1600  vsize 1200  refresh: 75  vid: 20393
(II) fglrx(0): #6: hsize: 1920  vsize 1080  refresh: 72  vid: 52433
(II) fglrx(0): #7: hsize: 2048  vsize 1536  refresh: 60  vid: 16609
(II) fglrx(0): Serial No: 54889069
(II) fglrx(0): Ranges: V min: 50  V max: 160 Hz, H min: 30  H max: 96 kHz, PixClock max 250 MHz
(II) fglrx(0): Monitor name: EIZO T68
(II) fglrx(0):
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Connected Display2: LCD on internal LVDS
(II) fglrx(0):  Display2: No EDID information from DDC.
(II) fglrx(0): Derived EDID from BIOS and internal tables for Display2:
(II) fglrx(0): Display2 EDID data ---------------------------
(II) fglrx(0): Manufacturer: MS_  Model: 0  Serial#: 0
(II) fglrx(0): Year: 1990  Week: 0
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) fglrx(0): Sync:Serration on. V.Sync Pulse req. if CompSync or SyncOnGreen
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 40  vert.: 30
(II) fglrx(0): Gamma: 1.00
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; Non RGB Multicolor Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.000 redY: 0.000   greenX: 0.000 greenY: 0.000
(II) fglrx(0): blueX: 0.000 blueY: 0.000   whiteX: 0.000 whiteY: 0.000
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 640  vsize 480  refresh: 60  vid: 16433
(II) fglrx(0): #1: hsize: 800  vsize 600  refresh: 60  vid: 16453
(II) fglrx(0): #2: hsize: 1024  vsize 768  refresh: 60  vid: 16481
(II) fglrx(0): #3: hsize: 1152  vsize 864  refresh: 60  vid: 16497
(II) fglrx(0): #4: hsize: 1280  vsize 960  refresh: 60  vid: 16513
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz   Image Size:  0 x 0 mm
(II) fglrx(0): h_active: 1400  h_sync: 1440  h_sync_end 1552 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1050  v_sync: 1050  v_sync_end 1050 v_blanking: 1063 v_border: 0
Comment 9 Stephan Kulow 2006-03-06 13:45:43 UTC
Am Montag, 6. März 2006 13:30 schrieb Anders Storsveen:
> Dimensions      452 mm (W) x 455 mm (H) x 478 mm (D)
> 17.8" (W) x 17.9" (H) x 18.8" (D)
>
> this is from the eizo page... where does the problem lie then ? EDID info
> or what?

They report the size of the monitor not the ones of the display.
I bet 15cm are the frame + speakers and whatnot.
 
Greetings, Stephan
Comment 10 Anders Storsveen 2006-03-06 14:10:38 UTC
Not to use this bugreport as my personal helpdesk though, but:

Active Display Size 	362 mm (H) x 271 mm (V) / 14.2" (H) x 10.7" (V)
Viewable Image Size 	Diagonal: 452 mm / 17.8"

Seems like this is what X should be getting as dimensions perhaps?
362x271? If so, do you have any idea where the error lies? in edid or perhaps display drivers?
Comment 11 Thiago Macieira 2006-03-07 20:27:12 UTC
Probably in the monitor itself (hardware).
Comment 12 Anders Storsveen 2006-03-07 21:31:07 UTC
I think from past experiences that I've had this problem before though,with other monitors... Will try to confirm somehow soon.