Mailinglist Archive: opensuse-bugs (13484 mails)

< Previous Next >
[Bug 331609] intel: Bad DPI value is uncorrectable via xorg.conf
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 7 Oct 2007 07:24:39 -0600 (MDT)
  • Message-id: <20071007132439.56640245269@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=331609#c11





--- Comment #11 from Felix Miata <mrmazda@xxxxxx> 2007-10-07 07:24:38 MST ---
(In reply to comment #10 from Stefan Dirsch)
My understanding was that you're talking about the Xserver -dpi option and not
the xrandr --dpi option.

That commentary was just about what didn't work to try to solve this Intel-only
DPI problem.

Resolution/DPI chosing in RANDR 1.2 is just so broken. :-(

The i810 driver still obeys DisplaySize to produce correct DPI. Why does sax2
prefer the broken intel/randr driver set over i810 for the final 10.3 release?
With so many bugs they seem too far from ready to live as a default in a public
release.

So does using xrandr for setting DPI help?

As stated in comment 9, only partially:
1-Does not work for Kicker and other autostarted apps
2-Works for apps started after running it

I suggest to open an enhancement request for krandrtray to set also the DPI.

That shouldn't be necessary except as workaround for current brokenness. i810
seems a better user workaround until intel/randr work right. Proper DPI should
be at least semi-automatic, not something users need to routinely choose off
some toolbar that doesn't help for apps already running anyway. xorg.conf is
supposed to be the mother config file that controls how X starts. If xrandr is
the only way to do something that needs doing on X startup on Intel, then
something in xorg.conf should at least trigger it even if some other config
file must be used for xrandr to know what to do.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References