Dual screen, windows in RH screen move workspace on suspend resume

[Colin Law]

On up to date Utopic release candidate with dual screens (laptop + external), windows on the external (right hand) screen often move to next workspace following suspend - resume.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Oct 22 21:55:07 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:17a9]
InstallationDate: Installed on 2014-10-21 (1 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.17
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Wed Oct 22 21:21:24 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 13890
 vendor SEC
xserver.version: 2:1.16.0-1ubuntu1

[Colin Law (colin-law)]

Also present with latest upstream kernel (3.18.0-031800rc1-generic 64 bit).

[Colin Law (colin-law)]

This is particularly severe if workspaces are disabled as it causes windows to completely disappear on resume. Even clicking the active launcher does not show them.

[Colin Law (colin-law)]

Further information:
The problem is only seen if I suspend by closing the lid. If I suspend using pm-suspend or selecting suspend from the top panel cog then the problem is not seen. Also I notice that in the case of closing the lid I get numerous errors in syslog during the suspend, starting with messages of the form
i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment

I am attaching syslog with the errors. The suspend at Dec 5 13:10:16 was by closing the lid and that at 13:17:30 was by cog menu.
I have tried the latest mainline kernel linux-image-3.18.0-031800rc7-generic_3.18.0-031800rc7.201411302035_amd64.deb which does not solve the problem. There are rather fewer messages (possibly due to the fix of bug #1390182) but there are still errors and the windows still move workspace.

Adding kernel package.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.