ubuntu unity virtual desktop reset after screen lock

Bug #1579678 reported by Friedemann Sommer
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Confirmed
High
Unassigned

Bug Description

1)
Description: Ubuntu 16.04 LTS
Release: 16.04

* 2 Monitor Setup (onboard HDMI, onboard DVI)
* both Monitors @ 1920x1080

2)
unity:
  installed: 7.4.0+16.04.20160415-0ubuntu1
  installation candidate: 7.4.0+16.04.20160415-0ubuntu1
  version table:
 *** 7.4.0+16.04.20160415-0ubuntu1 500
        500 http://mirror.netcologne.de/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

3)
After a screen lock (SUPER + L), display turning off after given time out and then reactivate display by pressing (CTRL) and logging in, all windows on every workspace are on different location if they were not maximised sometimes they are on different workspaces then before.

4)
I expected all windows after screen lock at the same position then before

Screenshots before/after

Before screen lock + time out for monitor turn off
http://i.imgur.com/PtbHMMg.png

After turn on monitor + logging in
http://i.imgur.com/f5EYZGa.png

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2
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
Date: Mon May 9 10:38:25 2016
DistUpgraded: 2016-04-22 11:12:25,305 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412]
InstallationDate: Installed on 2015-11-04 (186 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to xenial on 2016-04-22 (16 days ago)
dmi.bios.date: 07/02/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.90
dmi.board.name: H81M-HDS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/02/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon May 9 08:43:17 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 41124
 vendor DEL
xserver.version: 2:1.18.3-1ubuntu2

Revision history for this message
Friedemann Sommer (friedemannsommer) wrote :
Revision history for this message
Friedemann Sommer (friedemannsommer) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, that looks similar to bug #1295267

Could you try to do a fresh boot, log in, lock screen, unlock and attach the Xorg.0.log to the bug?

The logs reported have snippets like

"[ 18.916] (II) intel(0): resizing framebuffer to 3840x1080
[ 18.932] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (1920, 0), rotation normal, reflection none
[ 23.688] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1920, 0), rotation normal, reflection none
[ 23.691] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation normal, reflection none
[ 2239.871] (II) intel(0): resizing framebuffer to 1920x1080
[ 2239.873] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 0, position (0, 0), rotation normal, reflection none
[ 2240.201] (II) intel(0): resizing framebuffer to 3840x1080"

unsure if that matches an user triggered change or if the monitor config in xorg changes when power saving starts or something

Changed in unity (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

oh also the bug title is confusing/doesn't match the description, is your issue that windows are being moved or with the workspace switcher?

Revision history for this message
Friedemann Sommer (friedemannsommer) wrote :

"oh also the bug title is confusing/doesn't match the description, is your issue that windows are being moved or with the workspace switcher?" - Sebastien Bacher (seb128)

Sorry for that. I meant to say that my windows are being moved.

Revision history for this message
Krister Swenson (thekswenson) wrote :

What happens on screen activation is the following:
1. the laptop screen activates first (for just an instant), so all the windows are placed according to the parameters of the workspaces according to this screen size.

2. the multi-monitor configuration then kicks in, the windows getting placed again according to the new configuration.

Practically speaking what happens to me is the following...
  I will have my windows arranged according to a single high resolution external display.
The instantaneous step 1 replaced the windows according to my lower-res laptop display.
Step 2 then tries to distribute these replaced windows according to the external display.

The result is a bunch of window scattered onto various workspaces.

Revision history for this message
Krister Swenson (thekswenson) wrote :

Ubuntu 15.10 did not behave this way (Step 1 described above did not happen).

Revision history for this message
Krister Swenson (thekswenson) wrote :

by "replace" i mean "relocate".

summary: - ubuntu unity workspace switcher state reset after screen lock
+ ubuntu unity virtual desktop reset after screen lock
Revision history for this message
Andrea Azzarone (azzar1) wrote :

I'm not yet able to reproduce this problem but marking as "confirmed" because there are several duplicates.

Changed in unity (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Krister Swenson (thekswenson) wrote :

By the way, this happens to me even when the screen is blanked out (screen-saver mode) and the mouse is moved to activate the monitor. The screen doesn't have to be locked or anything.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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