touch-packages team mailing list archive

[crs <crs@xxxxxxxxxxxxxxx>]

After some trial and error it seems like I have to rephrase the initial
bug report:

If I resume from suspend caused by systemctl suspend, sudo pm-suspend,
or via the hotkey on my keyboard (K750), the login screen is only shown
on the build-in screen and not on the external monitor. In this case the
external monitor remains off and has to be enabled again by pressing
super+p multiple times.

However, if I resume from suspend caused be the suspend entry in the
menu accessible from the upper right corner (hereafter referred to as
'menu suspend'), the login screen is shown on both screens (build-in and
external). In this case the external monitor works as intended, even
after logging in.

If automatic login is enabled, the login screen is never shown after
resuming (obviously) and both monitors do work as intended. However,
enabling automatic login is not a sufficient work around.

I wasn't able to reproduce this observation on an live CD system (tried
14.04, 14.10, 15.04) since those systems always behaved weird after
another user with password was added.

So, how does 'menu suspend' differ from the other ways mentioned to
suspend the system?

** Changed in: xorg (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1454160

Title:
  External monitor is disabled after resume

Status in xorg package in Ubuntu:
  New

Bug description:
  I have an external screen connected to my machine (T450s, via docking
  station) and after resuming from suspend, my external monitor is
  disabled.

  After some trial and error I made an interesting observation: The
  external monitor only stops working if suspend via systemctl suspend,
  sudo pm-suspend, or via the hotkey on my keyboard (K750).

  However, this problem does not occur if I suspend via the menu entry
  in the upper right corner.

  How is this even possible?

  Mapping the suspend command from the upper right corner to a hotkey
  would be a sufficient workaround. But which command is used by that
  button?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1
  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: Tue May 12 11:10:31 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2015-05-03 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BWS03F00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET47WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS03F00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: dmi:bvnLENOVO:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BWS03F00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS03F00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  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.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue May 12 11:08:05 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1454160/+subscriptions