[Hewlett-Packard Compaq Presario CQ40 Notebook PC] suspend/resume failure [non-free: wl]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Critical
|
Unassigned |
Bug Description
suspend resume failure problem happen when you suspend your system and after sometime when you resume your system this type of problem happen you can not able to login and login screen not appearing.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelMo
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Tue Feb 25 13:05:25 2014
ExecutablePath: /usr/share/
Failure: suspend/resume
InstallationDate: Installed on 2014-02-16 (8 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140215)
InterpreterPath: /usr/bin/python3.4
MachineType: Hewlett-Packard Compaq Presario CQ40 Notebook PC
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.125
SourcePackage: linux
Title: [Hewlett-Packard Compaq Presario CQ40 Notebook PC] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/07/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.11C
dmi.board.
dmi.board.name: 3607
dmi.board.vendor: Compal
dmi.board.version: 99.61
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Compaq Presario CQ40 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.