10de:06fd [Dell Precision T5500] Ubuntu 13.10 dual monitor screen lock causes windows to disappear off-screen

[Chris Plummer]

I have a dual monitor set up with a Dell T5500 and an Nvidia Quadro NVS 295 graphics card. I lock the screen with a window open on the second monitor, then unlock it again. When the desktop shows again, the windows that were on the second screen are gone offscreen. I expected them to still be on the second screen - I can workaround this by using Alt+Spacebar to move the window back. This happens every time I lock the screen, and it happens if I use the Nouveau driver or if I use the proprietary driver. I expected the windows on the second screen to stay on the screen after unlocking the system. Instead, the windows disappeared off-screen - the Unity launcher still shows them being open, plus if I have multiple windows of an application open (i.e. the terminal), then double click the launcher icon, then it shows me all the windows and lets me choose one to bring forward, even the ones offscreen. When I pick the offscreen one to bring forward, its icon just shoots offscreen again.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013
 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Dec 3 09:51:37 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus:
 nvidia-319, 319.32, 3.11.0-13-generic, x86_64: installed
 nvidia-319, 319.32, 3.11.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G98 [Quadro NVS 295] [10de:06fd] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:062e]
InstallationDate: Installed on 2013-11-27 (5 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Precision WorkStation T5500
MarkForUpload: True
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=b56473e8-ada5-4f33-bd1a-ea5d818c8ecf ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D883F
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/16/2010:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA06:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T5500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Tue Dec 3 09:18:08 2013
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Dell Dell QuietKey Keyboard KEYBOARD, id 8
 input USB Optical Mouse MOUSE, id 9
 input Dell WMI hotkeys KEYBOARD, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.14.3-3ubuntu2
---
.tmp.unity.support.test.0:

ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G98 [Quadro NVS 295] [10de:06fd] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:062e]
InstallationDate: Installed on 2014-01-06 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140106)
MachineType: Dell Inc. Precision WorkStation T5500
MarkForUpload: True
Package: xorg 1:7.7+1ubuntu7
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=7197666d-a320-4893-bf03-0e3bb65ce20d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Tags: trusty ubuntu regression reproducible has-workaround compiz-0.9
Uname: Linux 3.12.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/16/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D883F
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/16/2010:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA06:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T5500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.50-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
xserver.bootTime: Mon Jan 6 13:05:09 2014
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Dell Dell QuietKey Keyboard KEYBOARD, id 8
 input USB Optical Mouse MOUSE, id 9
 input Dell WMI hotkeys KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.5-1ubuntu2
xserver.video_driver: nouveau

[penalvch (penalvch)]

Chris Plummer, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg REPLACE-WITH-BUG-NUMBER

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

apport information

[Chris Plummer (christopher-plummer)]

Hey Chris,

I installed the 01-06-2014 nightly build alongside my ubuntu 13.10 (the live DVD operation just gave me a blank screen) - the issue still occurs and is easily reproducible. Please advise on any other steps you wish me to take to test this.

[Chris Plummer (christopher-plummer)]

Hey Chris,

Thanks for letting me know! I had upgraded the BIOS a while back, but forgot to check for updates after. I've installed the new BIOS using wine and the DELL exe file, as you can see:

cplummer@cplummer-dl:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A16
05/28/2013
cplummer@cplummer-dl:~$

As to what happened, I'm not sure what you mean beyond what I've already reported. Here it is again, hopefully in more detail:

1) opened a terminal in the left-hand screen and dragged it to the right-hand screen
2) opened a file browser in the left-hand screen and dragged it to the right-hand screen
3) opened firefox in the left-hand screen and left it as is
4) Clicked the 'gear' icon in the upper-right of the left-hand screen, then clicked 'Lock' in the dropdown
5) Waited for both screens to go black - they did not go into power save mode
6) Moved the mouse around to unlock - the mouse icon moved, then hesitated for about 2 seconds. The right-hand screen flickered - I could see the two windows I'd put in it, then the right-hand screen went black. The left-hand screen then showed me the unlock password dialog.
7) I typed my password in, then hit Enter.
8) Both monitors unlocked to show me the desktop, with the Firefox window in the left-hand screen visible, but the windows in the right-hand screen were gone. The Unity launcher on both screens showed me that the file browser and terminal were still open with white arrows on the left of their icons.
9) I clicked on the file browser icon in the right-hand screen's launcher and used the Alt+Spacebar key sequence to bring up a context menu, which appeared on the right-hand screen at the right-most edge.
10) I clicked on the 'Move' item in the context menu, then dragged the window to the left-hand screen with my mouse. I repeated this action again and the file browser window moved into the right-hand screen.
11) I repeated this for the terminal window to make it move back into the right-hand screen.

Let me know if that helps, if you need more info, or if you want me to upload log files again.

Chris

[Chris Plummer (christopher-plummer)]

Sorry, I should be more clear - after the BIOS update, the issue still occurs, both on 13.10 and the nightly 14.04 that I've installed alongside it. My detailed 'what happened' description is how I verified that it still happens after the BIOS update.

Thanks,

Chris

[penalvch (penalvch)]

Chris Plummer, thank you for updating your BIOS. Could you please boot with the irqpoll kernel parameter following https://help.ubuntu.com/community/BootOptions and advise if this changes anything?

[Chris Plummer (christopher-plummer)]

Just tried it on the nightly build and the problem still happens - I'm not sure if it was like this before, but if I try to reproduce now, it happens about 6 times out of 8. A couple of times it worked fine, but never twice in a row. Usually, the screen goes black and then the unlock password screen shows up on the left-hand screen - it seemed like before, that the unlock password screen didn't come until after I'd moved the mouse. Also, one of the times that I tested, both screens went black, then the left hand screen showed firefox without any password unlock (it was like the screen was still unlocked) until I moved my mouse, then the left-hand screen went away and the unlock dialog came back.

I'll remove the 'irqpoll' and do some more testing to see if it's the same without it.

[Chris Plummer (christopher-plummer)]

When I removed the 'irqpoll' option, it still occurred, but a lot less frequently - it seemed like it was almost 1 out of 2 times it would happen. I actualy did have a streak of 5 or 6 times that I locked the screen and it worked fine. I got the 'one screen is still unlocked' problem a couple of times; also somtimes I would see the unlock password dialog right away and then somtimes I would have to shake the mouse to get it to come up. It seemed like most of the time with the 'irqpoll' option that I'd get the problem and it would show the unlock dialog right away without any intervention.

[penalvch (penalvch)]

Chris Plummer, thank you for providing the requested information. Could you please provide the missing information following https://help.ubuntu.com/community/DebuggingIRQProblems ?

[Chris Plummer (christopher-plummer)]

I'm not sure what you mean by missing information - I tried the other four boot options in the article:

* noapic

Same as before, except that IRQ #11 was disabled instead of 16. Same problem occurs with windows disappearing, seemingly random (works sometimes, doesn't work other times).

* pci=routeirq

Same as before, IRQ #16 was disabled. Same problem occurs with windows disappearing, seemingly random (works sometimes, doesn't work other times).

* pci=noacpi

Same as before, except that IRQ #11 was disabled instead of 16. Same problem occurs with windows disappearing, seemingly random (works sometimes, doesn't work other times).

* acpi=off

Second screen didn't appear and the single screen that did had very poor resolution. No bug because I didn't have dual screens.

* irqpoll

As I described before, the same as without it - the windows appear sometimes correctly and disappear at other times. Sometimes the windows stay across multiple locks, sometimes they don't.

Let me know if you want something else - also, I'll note that I'm not experiencing any of the IRQ problem symptoms described in the article, like hardware devices not working, multiple hardware device problems, or system hangs.

[penalvch (penalvch)]

Chris Plummer, thank you for providing the missing information. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Chris Plummer (christopher-plummer)]

I installed the amd64 mainline kernel packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc7-trusty/ according to your instructions and the issue still occurs. When I tested, it happened every time, 5 times in a row. I'll update the status and tags to reflect it.

Another note about the IRQ problem - this window disappearing issue happens whether or not the IRQ is disabled during boot. When it's disabled, my mouse is really sluggish and then when it isn't, my mouse is just fine. It happens at seemingly-random times - sometimes I boot and it comes up, and other times when I boot it doesn't. So I guess I am experiencing the IRQ symptom of a hardware device not working correctly, but it doesn't affect whether or not I can reproduce this bug.

[penalvch (penalvch)]

Chris Plummer, thank you for performing the requested test. Did this problem not occur in a release prior to Saucy? If not tested, could you please test the 3.2.x series Precise release via http://old-releases.ubuntu.com/releases/precise/ and advise to the results?

[Chris Plummer (christopher-plummer)]

This didn't occur for me when I used the 13.04 release - I'll see if I can try 12.04.2 and recreate the problem.

[Chris Plummer (christopher-plummer)]

I just tried the AMD 64 Precise Pangolin 12.04.2 release using this file - http://old-releases.ubuntu.com/releases/precise/ubuntu-12.04.2-desktop-amd64.iso. The screen locking works perfectly - I tried it about 20 times in a row, and every time it's consistently good - the screen immediately blanks with no flickers and a mouse movement brings up the enter password dialog on the left-screen. When I unlock, all the windows are positioned as I left them before I locked the screen.

Trying this on 12.04 makes me realize just how bad the experience is on 13.10+; the screen lock is just plain broken. It's very non-deterministic in that it flickers or flashes often, sometimes one of the screens shows what was on it before the lock, and most of the time the enter password / unlock dialog shows up immediately without any mouse or keyboard input. This is in addition to the windows that I had open disappearing offscreen. I expect the consistent behavior of the 12.04 screen lock - both screens are blanked immediately with no flashes or flickers and the unlock dialog only shows up after I move the mouse.

[penalvch (penalvch)]

Chris Plummer, thank you for performing the requested test. This fully verified a regression. The next step is verifying this a kernel or userspace one. In your Saucy+ install, could you please test the same Precise kernel as the live environment following https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions and advise if this problem is reproducible?

[Chris Plummer (christopher-plummer)]

It took a while to find the right build - it's hidden in the Quantal packages at https://launchpad.net/ubuntu/+source/linux-lts-quantal/3.5.0-23.35~precise1.

I installed the kernel packages, rebooted, and verified that with 3.5.0-23-generic, the issue still occurs in Ubuntu 13.10. This seems to be a userspace issue of some kind.

cplummer@cplummer-dl:~$ cat /proc/version
Linux version 3.5.0-23-generic (buildd@komainu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013
cplummer@cplummer-dl:~$

[penalvch (penalvch)]

Chris Plummer, thank you for performing the requested test. Just to confirm, when you initially reported this bug with Saucy, were you using the drivers from a Ubuntu repository as noted here https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#NVIDIA_drivers_provided_by_the_Ubuntu_repositories ? If so, which one?

[Chris Plummer (christopher-plummer)]

For Saucy, I've been using the 319 driver from Ubuntu - https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319. In my tests with 14.04, I kept the Nouveau driver installed; the same is true for my tests with 12.04.2, which I used the Nouveau driver for. The bug is reproducible if I use either driver.

[penalvch (penalvch)]

Chris Plummer, thank you for providing the requested information. Regarding your comments :
>"For Saucy, I've been using the 319 driver from Ubuntu - https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319."

Ok. Would anything change if you use either or newer or older driver version as noted in https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#NVIDIA_drivers_provided_by_the_Ubuntu_repositories ?

>"...the same is true for my tests with 12.04.2, which I used the Nouveau driver for. The bug is reproducible if I use either driver."

This would appear to contradict the results you provided in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1257327/comments/38 . Could you please clarify?

[Chris Plummer (christopher-plummer)]

I simply meant that in both 12.04.2 and 14.04 I had used the Nouveau driver. My statement that "The bug is reproducible if I use either driver." was meant to be a summary of the situation, not a contradiction of my testing in 12.04.2. 12.04.2 works fine (as did 13.04 before I upgraded to 13.10). 13.10 and 14.04 do not work - I can easily reproduce the bug in those versions.

That said, I am not going on a wild goose hunt and trying random Nvidia drivers to see if it fixes anything - you're guessing at what the problem is, when the evidence I've provided you so far indicates that the problem happens if I use the Nvidia driver or the Nouveau driver. Unless you can give me a good reason to try a different driver, it's a waste of my time.

[Maarten Lankhorst (mlankhorst)]

More likely a unity bug, not a xorg bug.

[Christopher Townsend (townsend)]

Hi Chris,

Wow, you have really had to jump through some hoops for this:)

At any rate, does this issue still occur on latest 14.04? It does sound like a Unity/Compiz issue, but I have not seen this issue on my dual screen setup, nor I have seen other users reporting an issue like this. Could be something specific to your setup.

Thanks!

[Chris Plummer (christopher-plummer)]

Yep, it's been something slightly short of a circus act : )

It does still occur, but not nearly as often as it used to. The new lock screen in 14.04 is much better than the one in 13.10 - I just tried locking the screen a dozen times in a row with no issue, and I've probably only seen the issue occur 2-3 times since I installed 14.04 (I blew away my old/other linux installs and fresh installed 14.04 the day it came out, looks like that was the 17th of April). I believe the times that it did re-occur, I had my screen locked overnight and when I came back to work in the morning, a terminal window in the second monitor had gone off screen (it was the only window on that screen). This actually happened to me this morning when I came in (May 30th, 2014).

The process I go through every night is: 1) lock the screen with Super + L, 2) turn off the monitors manually (push the physical power button). When I come in in the morning, I push the power buttons back on, and the lock screen is always there. I can then put in my password to unlock and get working. The first thing I usually run is 'sudo apt-get update' and 'sudo apt-get dist-upgrade' in a terminal to be sure I've got the latest packages and updates.

In a potentially related issue, I can't reliably use the inactivity screen shutdown on my monitors - I have to set the 'System Settings'->'Brightness and Lock'->'Turn screen off when inactive for' to 'Never', otherwise my monitors will never come back once they've started sleeping (clicking or typing or running 'xset dpms force on' via ssh - I have to reboot the computer). I also have problems occasionally with my left monitor not coming on during a reboot - I sometimes have to power it off and power it on manually before the Ubuntu login screen will recognize it and drive the display.

[Christopher Townsend (townsend)]

Hmm, I'm thinking turning off the monitor is the root issue here. Compiz does not always handle monitor hotplugging very well which is what happens when powering off the monitor.

A few more questions to help me narrow this down.

1. Are you using more than one workspace? If so, what is your workspace geometry like, ie, 2x2 workspaces? If you don't have workspaces enabled, could you try enabling workspaces when this issue occurs and see if it shows up in one of the workspaces.
2. Are any of the windows on your second monitor maximized?
3. You say "monitors", implying you turn off more than one monitor. Is this something like a dual monitor desktop system?

As far as the monitors not powering off when they are supposed to, I think that is either an issue in power management or the kernel and not in Unity/Compiz.

Lastly, I've been doing some work with windows getting shuffled around when removing/adding a monitor, so if you feel a bit adventurous, you could try a test Compiz package I have that could (hopefully) fix this issue. Try adding https://launchpad.net/~townsend/+archive/compiz-test and see if it helps and report back to me.

Thanks!

[Chris Plummer (christopher-plummer)]

1. I'm using just a single workspace, I believe - I've never enabled workspaces, so I'm guessing it's disabled by default? I'll see if I can turn it on if it's off and set up additional workspaces.

2. None of them are maximized. I usually have Eclipse maximized in the left-hand monitor and some terminals and source-control UIs open in my right-hand monitor.

3. It is a dual monitor desktop system.

Like I said, it doesn't reproduce much anymore, but if it happens again with the workspaces enabled, I'll report any findings to you. I don't have time to install your compiz package right now - I'm actually in the midst of some family transition time and probably won't be able to get back to you for the next month. If you think of any questions or things you want me to try, just let me know and when I'm back in the office I'll try to answer at the beginning of July.

Thanks for helping!

[Chris Plummer (christopher-plummer)]

Well, what do you know - I enabled workspaces in a 2x2 configuration, then locked the screen, turned off both monitors, turned them back on, and the two windows I had in the right-hand monitor disappeared. When I clicked the launcher icon for them, they immediately showed up in the workspace in the upper-right hand corner of the grid.

I just did it a second time, and it happened again - I think you must be right that it's the turning off of the monitors that's causing it now. It seems like I have a pretty reproducible test case, so maybe I could find time to try your package this week before I'm unavailable again for a while. Also in case it helps, I believe that just locking the screen back in 13.10 would set it off - I don't think I had to turn off the monitors.

I'm thinking the reason that I haven't run into this consistently in 14.04 is that I haven't been leaving a lot of windows open when I go home and turn off the monitors; I think that I've just been closing most of them before leaving.

[Launchpad Janitor (janitor)]

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Unity because there has been no activity for 60 days.]