Screen output selection broken with Dell Latitude E-series advanced dock

Bug #575015 reported by fubarbundy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-desktop (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xrandr

Hardware: Latitude E6500/Intel GMA-4500MHD graphics, E-series advanced dock, 2 x DVI monitors

Actual behaviour:
- on boot (login screen), docked with the laptop lid closed, The external displays are deactivated (I assume that the laptop panel is activated). Opening the lid deactivates the laptop display and activates both external displays in clone mode. Closing the lid deactivates the external panels again.
- On login, the displays remain in clone mode. Opening the laptop lid, waiting for display switching and then closing it again causes the external displays to (correctly) switch to extended desktop
- Undocking with the laptop lid closed often causes X to hang (PC still available over SSH, only killing the X server brings it back to life)
- Docking with the laptop lid closed almost always causes X to hang
- Docking with the laptop lid open, then closing the lid results in (incorrect) clone mode or nothing on the external displays. Repeated opening and closing of the lid sometimes fixes this; other times the displays have to be manually reconfigured.

Expected behaviour:
- At least one external display should ALWAYS be activated when the laptop lid is closed!
- Xrandr/Gnome should remember its last configuration for each combination of connected/active (e.g. laptop lid when not closed) displays, and always switch to that when they are next active in the same combination.
- No crashes :)
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
MachineType: Dell Inc. Latitude E6500
Package: xrandr (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=db1f8334-529f-427e-9f74-90ce9005abc8 ro quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
XorgConf:

dmi.bios.date: 08/29/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0NY667
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/29/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi fubarbundy,

Please run the command 'apport-collect BUGNUMBER', which will attach several files we need for debugging.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in xrandr (Ubuntu):
status: New → Incomplete
Revision history for this message
fubarbundy (launchpad-mailtic) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
fubarbundy (launchpad-mailtic) wrote : CurrentDmesg.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : Lspci.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : Lsusb.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : PciDisplay.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : ProcInterrupts.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : ProcModules.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : UdevDb.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : UdevLog.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : XorgLog.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : XorgLogOld.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : Xrandr.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : glxinfo.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : monitors.xml.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : setxkbmap.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : xdpyinfo.txt

apport information

Revision history for this message
fubarbundy (launchpad-mailtic) wrote : xkbcomp.txt

apport information

Changed in xrandr (Ubuntu):
status: Incomplete → New
Revision history for this message
fubarbundy (launchpad-mailtic) wrote :

More info on display selection behaviour:

Active displays and layout with the following sequential actions:

Laptop undocked, lid open: Laptop display, single screen
Docked, open: Laptop display, single screen
Docked, closed: 2 external displays, clone
Docked, open: 2 external displays, extended desktop
Docked, closed: Laptop displays, single screen (assumed config as not visible :) )
Docked, open: 2 external displays, clone
Docked, closed: 2 external displays, extended desktop

It looks like every time a lid action is received, the display config cycles to the next of 3 configs (which is pretty useless)

Bryce Harrington (bryce)
tags: added: lucid
Bryce Harrington (bryce)
Changed in xrandr (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Actually the heuristics that manage what to do when hotplugging is in the gnome control utilities (gnome-rr.c in gnome-desktop). Sounds like it's not handling things as you expect; refiling (there is no 'xrandr' package anymore).

affects: xrandr (Ubuntu) → gnome-desktop (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

is there any chance you could try with a newer version of Ubuntu? the bug seems to mix several issues, like "booting lid close leads to have no screen activated" seems rather an xorg issue, I can't confirm that here on a latitude serie-e with a dock station on Oneiric though

affects: gnome-desktop (Ubuntu) → gnome-desktop3 (Ubuntu)
Changed in gnome-desktop3 (Ubuntu):
importance: Undecided → Low
affects: gnome-desktop3 (Ubuntu) → gnome-desktop (Ubuntu)
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Been a while with no activity, feel free to reopen if you're still having this issue.

Changed in gnome-desktop (Ubuntu):
status: Confirmed → Invalid
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.