Bug 927327 - gnome-settings-daemon should cap maximum resolution at 2048 pixels in either dimension on Intel adapters that lose 3D acceleration above 2048
Summary: gnome-settings-daemon should cap maximum resolution at 2048 pixels in either ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 19
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Adam Williamson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-25 16:39 UTC by Jeff Bastian
Modified: 2015-02-17 14:54 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:54:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 646280 0 None None None Never

Description Jeff Bastian 2013-03-25 16:39:22 UTC
Description of problem:
I have a Lenovo T60 with Intel 945GM graphics.  If I attach a second monitor or projector, then Gnome runs *really* slowly.  This is because the Intel graphics are limited to surfaces <= 2048 pixels wide, but with the external display the virtual desktop exceeds that 2048 limit.

Gnome 3.6 would pop up a warning and drop to fallback mode and run fine, but 3.8 has dropped fallback mode, so it just runs extremely slowly and is pretty much unusable.

I hit this problem with KDE 4.10 also -- see bug 921781 -- but KDE can turn off the desktop effects.  For Gnome 3.8, I have to launch a terminal and run
  LIBGL_ALWAYS_SOFTWARE=y gnome-shell -r
to make it somewhat usable with software rendering.

Gnome 3.8 should detect the hardware can't handle the large desktop and auto-switch to software rendering.

Version-Release number of selected component (if applicable):
gnome-shell-3.7.92-2.fc19.x86_64

How reproducible:
every time

Steps to Reproduce:
1. run Gnome 3.8 with Intel graphics and a display that exceeds 2048 pixels in at least one dimension
 
Actual results:
Gnome is very slow

Expected results:
Gnome remains usable

Additional info:

Comment 1 Adam Williamson 2013-04-23 22:14:27 UTC
ajax says that switching to software rendering on the fly is unfeasible for now. What he suggests instead is that GNOME should not extend the total resolution beyond 2048 pixels in either axis on affected Intel hardware - this will involve running one or other monitor below its native resolution, but it's better than effectively killing the usefulness of the desktop. It should probably show some kind of warning explaining what's going on.

<ajax> and i thought g-s-d was meant to forbid you from going to configs that won't work at runtime.
<adamw> ajax: ah, so we should maybe redirect this to g-s-d and get it to try and cap at 2048 for affected intel chips?
<ajax> that's the near term fix anyway
<adamw> roger
<adamw> i guess the gnome guys will want a way to identify the affected chips, presumably the same thing gnome-session uses
<ajax> it should be posting the maximum desktop size to the root window as a property
<ajax> % xprop -root | grep _GNOME_MAX
<ajax> _GNOME_MAX_SCREEN_SIZE(CARDINAL) = 8192

Comment 2 Todd Morgan 2013-05-27 18:57:49 UTC
I am experiencing the same or similar issue with a Dell D430 running the latest F19 32-bit packages. Gnome-shell performs great with the laptop only using the primary screen. If I boot with an external monitor (tv) or add a screen to the VGA port while Gnome-shell is running, the shell locks up.

I have another laptop (Toshiba M105) that has the exact same video chipset. I've done an A/B test with F19 and Ubuntu 13.04 with Gnome 3.8.2. With Ubuntu I can add an external monitor and everything works smoothly. With F19, I can add the external monitor and even turn off the built-in one, BUT the video on the external monitor is horrible. It appears to be doing software rendering.

With these video issues it makes it difficult or impossible to use F19 on either of these laptops in a business setting where connecting to a projector is a fairly common task.

If there is anything I can do to help provide assistance in remedying this issue, let me know.

Comment 3 Jonathan Underwood 2013-07-29 23:18:06 UTC
Seeing this on a Dell XPS M1210 as well, and it's crippling.

Comment 4 Fedora End Of Life 2015-01-09 17:49:01 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-17 14:54:13 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.