[Dell Inc. Inspiron 5521] suspend/resume failure [non-free: fglrx]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
freezes some time
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.16.0-22-generic x86_64
NonfreeKernelMo
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Tue Oct 21 22:06:28 2014
DuplicateSignature: suspend/resume:Dell Inc. Inspiron 5521:A05
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-10-16 (4 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Inspiron 5521
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.136
SourcePackage: linux
Title: [Dell Inc. Inspiron 5521] suspend/resume failure [non-free: fglrx]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/03/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Dell Inc.
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 5521
dmi.product.
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1383827, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.