ubuntu-x-swat team mailing list archive

[Bryce Harrington <745112@xxxxxxxxxxxxxxxxxx>]

On lp #747205 we discovered by creating a new user account, that having
certain RANDR operations present in monitors.xml would trigger it,
presumably because gnome-settings-daemon would pick up those
configuration settings and try applying them, triggering an underlying
bug in RANDR.  Perhaps fiddling with the primary monitor setting did it?

734756 collected register dumps on the issue, and experimented with some
dpms forcing from the userspace side.  My elderberry PPA was found to
have some positive effects, but didn't fix it sufficiently completely to
warrant pursuing that to work around the kernel issue.  drm-intel-next-
proposed did not boot on this reporter's hardware.

Video and photos are available on bug #750259.  We also examined gpu
error states and found this bug is not a gpu lockup issue (as 747205
suggested).  The drm-intel-next-proposed kernel from around 4/21 was
found to fix it.

Bug #737891 includes reports of this issue, among other problems.
Maverick was re-tested via livecd and the issue was not reproduced
(maybe for the same reasons as creating a new account in bug 747205 did
not reproduce?  Reporters also found that deleting monitors.xml has an
ameliorative effect.)  Fiddling with which monitor was listed as primary
in monitors.xml appeared also to resolve things for at least one person.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112

Title:
  [arrandale] desktop is messed up (goes black) when laptop is docked
  with two external 1920x1200 monitors (x86_64)