[ASUSTeK COMPUTER INC. X55U] suspend/resume failure [non-free: fglrx]

[Brock]

Logged in, error popped up out nowhere. Please fix A.S.A.P.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-13-generic 3.18.0-13.14
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: fglrx
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: blaine 3417 F.... pulseaudio
 /dev/snd/controlC0: blaine 3417 F.... pulseaudio
Date: Sat Feb 21 12:31:29 2015
DuplicateSignature: suspend/resume:ASUSTeK COMPUTER INC. X55U:X55U.420
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2015-02-11 (11 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterpreterPath: /usr/bin/python3.4
Lsusb:
 Bus 003 Device 002: ID 1bcf:2883 Sunplus Innovation Technology Inc.
 Bus 003 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 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X55U
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.18.0-13-generic N/A
 linux-backports-modules-3.18.0-13-generic N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [ASUSTeK COMPUTER INC. X55U] suspend/resume failure [non-free: fglrx]
UpgradeStatus: Upgraded to vivid on 2015-02-17 (5 days ago)
UserGroups:

dmi.bios.date: 11/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X55U.420
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X55U
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55U.420:bd11/30/2012:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X55U
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/

[Brock (mesuki230)]

On Monday, February 23, 2015 06:42:06 PM you wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.0 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not boot,
> please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the
> upstream kernel is complete, please mark this bug as "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete

Yes. It started after upgrading from Ubuntu 14.10 to the 15.04 daily build.
I'd upgraded via network install, said-upgrade being performed via terminal.
Prior to aforementioned-upgrade, I had upgraded from kernel version 3.16 to
3.18, though I hadn't experienced this error until I'd upgraded to 15.04.

Another thing which I believe I should mention is that this issue began
occurring after installing the KDE Plasma 5 Tech Preview, said-install also
being performed via terminal. I've since installed Kubuntu 14.10 64-bit with
KDE Plasma 4 Stable and I'm not planning on moving to 15.04 until this issue
with KDE Plasma 5 is fixed, though I know that this is not really of your
concern since KDE Plasma 5 is not of Canonical's design, but the KDE Plasma
Team. I will definitely send them a report soon to let them know of this issue.

Either way, I'm not really impressed with 15.04. I don't really see anything
new in Ubuntu which makes me want to stay. If anything really impressed me, it
was KDE Plasma 5. I really like KDE Plasma 4, but, after seeing the Plasma 5
alpha, that made me truly excited about 15.04, if not 15.10.

Thank you for reading this email and I hope that this issue will be solved
soon.

[Launchpad Janitor (janitor)]

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