[Dell Latitude D400] Black screen on resume after suspend by lid close persists in Xubuntu 14.10

Bug #1385926 reported by Damian Campbell
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Closing the lid does not activate a clean suspend and results in black screen with frozen cursor upon re-opening the lid in Xubuntu 14.10 and upgraded from 14.04.1. Once black screen mode is invoked, the only recourse is power off re-boot. Suspend by lid close worked correctly in Xubuntu 12.04.

Fix reported http://xubuntu.org/news/laptop-users-fix-available-for-the-black-screen-on-unlock-bug/ does not apply.

WORKAROUND: Suspend via menus or keyboard before closing lid.

---
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chezcampbell 2171 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=504c20f7-bda6-4b15-ac0a-d5c9021f07c4
InstallationDate: Installed on 2014-08-14 (73 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Latitude D400
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=b11ff414-9135-4c64-bf12-3cdc8bfeed18 ro forcepae quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-23-generic N/A
 linux-backports-modules-3.16.0-23-generic N/A
 linux-firmware 1.138
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: utopic
Uname: Linux 3.16.0-23-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/28/2005
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A08
dmi.board.name: 0W0327
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA08:bd06/28/2005:svnDellComputerCorporation:pnLatitudeD400:pvr:rvnDellComputerCorporation:rn0W0327:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude D400
dmi.sys.vendor: Dell Computer Corporation

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1385926

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Damian Campbell (dcampbell305) wrote : AlsaInfo.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: apport-collected utopic
description: updated
Revision history for this message
Damian Campbell (dcampbell305) wrote : BootDmesg.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : CRDA.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : IwConfig.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : Lspci.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : ProcEnviron.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : ProcModules.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : PulseList.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : UdevDb.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : UdevLog.txt

apport information

Revision history for this message
Damian Campbell (dcampbell305) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

Damian Campbell, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (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 exactly shown as:
kernel-fixed-upstream-3.18-rc1

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.

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

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.

tags: added: latest-bios-a08
tags: added: trusty
summary: - Black screen on resume after suspend by lid close persists in Xubuntu
- 14.10
+ [Dell Latitude D400] Black screen on resume after suspend by lid close
+ persists in Xubuntu 14.10
description: updated
tags: added: regression-release
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Damian Campbell (dcampbell305) wrote :

Further to this :

The keyboard suspend now no longer operates since the upgrade from 14.04.1 to 14.10. (worked in 12.04)

Suspend by menu continues to function.

Revision history for this message
Damian Campbell (dcampbell305) wrote :

Strike last comment. Finger trouble with new power manager. Keyboard working as expected

Apologies for noise

Revision history for this message
bobbaer (bobbaer) wrote :

confirming this affect me too:

uname -a
Linux karoushi 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu 14.10

suspend itself works fine
Laptop: SONY VAIO VPCCB3S1E (Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz, with additional [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] )

using XFCE POwerManager with xscreensaver.

* system upgraded from 14.01
* created new user to exclude possibility of old configuration files messing up something to no avail
* to make suspend work changes in /etc/systemd/logind.conf
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
* Fixes didn't work in 14.04* already

Workarounds as described either
1. type blind, open terminal with shortcut and enter xrandr --auto or
2. suspend before closing the lid (e.g. powerbutton)

Also: happens only with internal Monitor, if external is
connected (here HDMI), only LVDS remains black.

Tried with upstream Kernel (daily, had issues with rc2)
linux-image-3.18.0-999-generic_3.18.0-999.201410290205_amd64.deb
but problem still exists.

Revision history for this message
penalvch (penalvch) wrote :

bobbaer, thank you for your comment. Unfortunately, this bug report is not scoped to you, your hardware, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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

Revision history for this message
bobbaer (bobbaer) wrote :

sorry for that.
Will file a new report

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

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
penalvch (penalvch) wrote :
Changed in linux (Ubuntu):
status: Expired → 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.