** Changed in: xorg-server
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
To manage
There is some progress upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=41115
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on
Hi. This bug^H^H^H"feature" is now over nine years old. As much as I'd
like to see a proper solution, I think it would really be best at this
point to at *least* add the patch given while we wait for that to
happen. Pretty please?
--
You received this bug notification because you are a member of
** Tags removed: 16.04
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
To manage notifications about
Hi All,
I'm jumping in this thread because I think this 'bug' is the source of
many scaling issues.
I'm the owner of a 13" laptop with a 3200x1800 native resolution. As
recommended elsewhere, I set the scale factor to 2 and most applications
are readable now. However, readable is does not mean
Yes. As mentioned it is a single patch to apply, that has been available
since the very first day the bug was reported, actually 8 years ago (I
was wrong when I said 6). Incidentally, I was the second reporter of
this issue, with Bug #572943, the second lowest numbered duplicate, one
month before
@Sergio, sorry but your comments are OT. Different resolutions for
different screens are not supported on the toolkit level; a window can
be on both screens at once and such, and it is beyond the scope of this
bug. Viewing distance again has nothing to do with this bug; DPI does
not depend on the
Thanks for your observations.
In fact, in my comments there were multiple points.
One of them is different DPI for different screens. As you mention, this
cannot be more than a wish for now, as Linux is very badly lagging wrt
windows that has been enjoying per-display DPI settings for more than
There is 62 people who think this bug *is* important. It is a problem
mainly with displays of which DPI is far from 96x96, such as more and
more common HiDPI.
Let's not turn it into discussion forum on Linux vs. Windows, or ideal
state of Linux. We simply want Xorg to respect the DPI reported by
** Tags added: 16.04 xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
To manage notifications about this bug go to:
** Changed in: xorg-server
Importance: Wishlist = High
** Bug watch added: freedesktop.org Bugzilla #89820
https://bugs.freedesktop.org/show_bug.cgi?id=89820
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Argh. I am yet another hapless user clamouring for help.
My hardware: Apple MacBook 13 Retina, DPI of 227.
X.Org's infinite wisdom: DPI of 96.
My eyes are now broken, and i find myself tweaking individual apps in
the hope that they'll become usable. Inevitably, proportions become
crooked.
A couple more notes.
IMHO, the biggest issues with the current situation are the following:
1) The physical display size is available via xrandr. However xrandr delivers
it in a format that is rather uncomfortable to parse.
2) The hardware only provides a physical display size and not the
I would also add that in the case of multiple screens with different
features (e.g. laptop screen + desktop monitor), it would be great to
have different dpi values and apps notified of the dpi change when they
are moved from one screen to another.
--
You received this bug notification because
Could someone provide an update on the status?
Upstream insists on keeping xorg broken along winxp lines; I wouldn't be
surprised if they fix it in wayland some day, years after winvista and ages
after it worked in X. I'd call this $name_that_sexual_minority default based
on the methods used
Fair point. Unfortunately from what I can see the xorg developers are
not interested in fixing this and believe that the current behaviour is
both correct and acceptable. Some of them seem to be suggesting that it
is the job of the window manager/desktop environment to pass the desired
settings
A couple of last minute HiDPI fixes have just been added to GNOME shell
3.12.
More relevantly, Unity 7 on Ubuntu 14.04 Trusty Tahr will have support
for HiDPI displays.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the info! However, let me recall that the bug is not against unity
and gnome, but xorg. For many reasons one may have X starting without unity or
gnome (because of using another desktop or a transient misconfiguration). In
this case, X should be able to provide readable chars even
This should definitely be fixed for Ubuntu 14.04 (Trusty).
This is NOT a wishlist item, this is a BUG.
Using a default DPI of 96 on a 200 DPI monitor is /NOT/ helpful at all!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not sure if this is being worked on for the Unity desktop in Ubuntu,
but you might like to try the Ubuntu GNOME 14.04 Trusty Tahr beta 1
which is based on GNOME 3.10 - see
https://wiki.ubuntu.com/TrustyTahr/Beta1/UbuntuGNOME for info and
download links. As per
I too thing this should be fixed. The best argument I see for it is that
at least Gentoo tells you to rely on autodetection of the settings.
There was a time where you could generate an xorg.conf and then tweak it
but we've progressed past it because the config always broke. Now,
requiring someone
I would assume that by now a great deal of people do have a hi-res
display and are affected. This bug should receive highest priority,
certainly over feature enhancements as it ruins the experience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Red Hat Bugzilla #534047
https://bugzilla.redhat.com/show_bug.cgi?id=534047
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and
I may not agree with the tone that appears a bit aggressive, but the
observations by Tfa7 appear to be correct.
Furthermore, with reference to the justification that there are monitors
that report wrong/crazy EDID values, I really do not think that the
majority of users who have bought and paid
See also https://help.ubuntu.com/community/AsusZenbook#LCD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
To manage
With the new Retina displays and the trend that they impose we are
shortly going to have displays dpi values from 90 (old large monitors)
to over 300 (newer laptops and tablets). Assuming 96 dpi for everything
will surely lead to interesting times.
--
You received this bug notification because
I wonder how much configuration iOS users need to do to get a Retina
display set up? The answer none comes to mind.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical
Launchpad has imported 10 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=41115.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: freedesktop.org Bugzilla #41115
http://bugs.freedesktop.org/show_bug.cgi?id=41115
** Changed in: xorg-server
Importance: Medium = Unknown
** Changed in: xorg-server
Status: Invalid = Unknown
** Changed in: xorg-server
Remote watch: freedesktop.org Bugzilla
** Changed in: xorg-server
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
To manage
** Changed in: xorg-server
Status: Unknown = Confirmed
** Changed in: xorg-server
Importance: Unknown = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
--
ubuntu-bugs mailing list
** Changed in: xorg-server
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
--
ubuntu-bugs
** Changed in: xorg-server
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
--
ubuntu-bugs
This looks like one good reason to go with NVIDIA whenever you have a
decent screen :-)
Could someone be so kind to explain on what basis it is being stated
that the current behavior leaves the same flexibility as before?
Former behavior:
- do nothing to get the dpi from the screen, write 96 dpi
This change was introduced for all RandR 1.2 drivers by
http://cgit.freedesktop.org/xorg/xserver/commit/?id=fff00df . (Notably,
the nvidia binary driver is not affected.)
GNOME does also force X back to 96 DPI when gnome-settings-daemon starts
up (bug 157398, bug 246718). It’s even more
36 matches
Mail list logo
