Second monitor flickery and unusable

Bug #1063797 reported by Alex Whitman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After boot or after log out, my second monitor is flickery and unusable at the login screen. The mouse won't move from the primary monitor to the secondary. After login the secondary monitor works fine.

In 12.04 the secondary monitor would show a clone of the primary monitor which it could be doing currently but the screen doesn't display correctly for me to know.

lspci reports my graphics card as:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device 2008
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 53
 Region 0: Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at f000 [size=64]
 Expansion ROM at <unassigned> [disabled]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: lightdm 1.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Mon Oct 8 15:00:29 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to quantal on 2012-09-25 (12 days ago)

Revision history for this message
Alex Whitman (alexwhitman) wrote :
Revision history for this message
Alex Whitman (alexwhitman) wrote :

I've managed to work around this for now by using a the display-setup-script config option to run:

xrandr --output HDMI1 --off && xrandr --output HDMI1 --auto --right-of HDMI3

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Closing assumed fixed. Sounds like a driver issue anyway.

Changed in lightdm (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.