Freeze on screensaver deactivate when set to lock on screensaver activate

Bug #1476343 reported by Carl Miller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Low
Unassigned

Bug Description

A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light-locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes.

Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jul 20 10:45:46 2015
InstallationDate: Installed on 2014-07-22 (362 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106]
 NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106]
InstallationDate: Installed on 2014-07-22 (461 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory
 init: indicator-power main process (3022) killed by TERM signal
 init: indicator-application main process (3031) killed by TERM signal
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory
 init: indicator-power main process (2949) killed by TERM signal
 init: indicator-application main process (2958) killed by TERM signal
MachineType: Micro-Star International Co., Ltd. GT70 2PC
Package: xorg 1:7.7+1ubuntu8.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
Tags: trusty ubuntu
Uname: Linux 3.13.0-65-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark
_MarkForUpload: True
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1763IMS.70T
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1763
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.C
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A:
dmi.product.name: GT70 2PC
dmi.product.version: REV:0.C
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 5 09:58:38 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
 NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5920
 vendor CMO
xserver.version: 2:1.15.1-0ubuntu2.7

Revision history for this message
penalvch (penalvch) wrote :

Carl Miller, thank you for reporting this and helping make Ubuntu better. Could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1476343

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Carl Miller (chaz-q) wrote : BootDmesg.txt

apport information

tags: added: apport-collected ubuntu
description: updated
Revision history for this message
Carl Miller (chaz-q) wrote : BootLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : Dependencies.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : DpkgLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : LightdmLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : Lspci.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : Lsusb.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : ProcEnviron.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : ProcModules.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : UdevDb.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : UdevLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : XorgLog.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : XorgLogOld.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : Xrandr.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : xdpyinfo.txt

apport information

Revision history for this message
Carl Miller (chaz-q) wrote : xserver.devices.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

Carl Miller, as per http://us.msi.com/support/nb/GT70-Dominator-GTX-970M.html#down-bios&Win8.1%2064 an update to your computer's buggy and outdated BIOS is available (71D). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-71d
Revision history for this message
Carl Miller (chaz-q) wrote :

Hi, Christopher. Thanks for all the helpful links! Indeed, I applied the BIOS update, and the hard freeze is now gone! It's not all working exactly as I expect, but at least the BIOS change cured the worst symptom.

Changes made:
Applied MSI BIOS update to version 71D.
Changed light-locker back to activate on screensaver activate.

New behavior when coming back to laptop with locked screen:
Make a movement on the touchpad. Screen remains completely black, BUT computer is still running properly, as shown by network traffic.
Click the mouse buttons. Same thing, screen remains completely black, but no hard crash; everything is still running.
Press some non-typing keys (shift, ctrl, etc.). Same thing.
Blindly type my password into the completely black screen. Screen turns on, unlocks, and shows me my full working X environment, exactly as I'd left it.

Which is at least usable. Not ideal, and not what I think is expected behavior, but behavior I can deal with.

chaz@cesium:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for chaz:
E1763IMS.71D
04/17/2015
chaz@cesium:~$

Revision history for this message
penalvch (penalvch) wrote :

Carl Miller, regarding the new problem, you may want to first check if updating to the Vivid enablement stack addresses the issue as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack .

If not, please file a new report via a terminal:
ubuntu-bug xorg

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Regarding the scope of this report, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1476343/comments/24 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in xorg (Ubuntu):
status: Incomplete → 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.