[Asus M5A97 EVO R2.0] Computer not suspending on inactivity when not logged in

[Jan Corazza]

The kernel version and all other info attached is correct (3.13, official kernel).

#DESCRIPTION

My computer is set to automatically dim the screen and lock after 10 minutes, and suspend after an hour of inactivity.

That works fine - but only once I've logged in first.

If I switch the computer on and then leave it, it won't suspend, although it will dim the screen.

#STEPS TO REPRODUCE

0. (computer is powered off)
1. boot computer
2. the log-in screen comes up
3. wait a couple of minutes, the screen will dim and switch off
4. wait for an hour

What happened: computer DIDN'T suspend
What I expected to happen: the computer would've suspended the same as if it locked itself after I've logged in once.

Relevant information:

 - desktop computer
 - mobo: M5A97 EVO R2.0
 - proc: AMD FX-8320
 - graphics: AMD Radeon HD 7790

See the attached files for further info (uname, /proc/version_signature, dmesg, lspci -vvnn).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-36-generic 3.13.0-36.63
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jan 2367 F.... pulseaudio
 /dev/snd/controlC0: jan 2367 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 6 09:25:50 2014
InstallationDate: Installed on 2014-07-14 (83 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=6e991daa-60a1-41a6-86b9-099d96d697f2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-36-generic N/A
 linux-backports-modules-3.13.0-36-generic N/A
 linux-firmware 1.134~gd~t
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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/v3.17-utopic/

[Jan Corazza (corazza)]

As I said Joseph, this was reported after I manually fixed my computer by removing the mainline kernel. Only the kernel version has changed, everything else is the same on the system.

[Jan Corazza (corazza)]

I posted this from school so I wasn't paying full attention - I had a totally different bug in mind when I made that edit!

Actually all of this **does** happen in 3.13 - something unrelated happens in 3.17.

So basically all info I gave originally is correct. Can you validate the bug again?

I will check it with the upstream kernel as you asked as soon as possible.

[Jan Corazza (corazza)]

Hey, what do I need to do to complete the bug report? And why were the files removed? They contained correct information.

[penalvch (penalvch)]

Jan Corazza, just to clarify, before you installed a mainline kernel, suspend was working, and afterwards it was not?

[Jan Corazza (corazza)]

It didn't work before I installed it, and it didn't work after I removed
it. In between, I didn't check. Nothing to do with the new kernel I'd say.

And in general, suspend works, I just have to log in once.
On Oct 8, 2014 3:00 AM, "Christopher M. Penalver" <
<email address hidden>> wrote:

> Jan Corazza, just to clarify, before you installed a mainline kernel,
> suspend was working, and afterwards it was not?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1377820
>
> Title:
> Computer not suspending when inactive in the main log-in prompt
> (official 3.13 kernel)
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> The kernel version and all other info attached is correct (3.13,
> official kernel).
>
> #DESCRIPTION
>
> My computer is set to automatically dim the screen and lock after 10
> minutes, and suspend after an hour of inactivity.
>
> That works fine - but only once I've logged in first.
>
> If I switch the computer on and then leave it, it won't suspend,
> although it will dim the screen.
>
> #STEPS TO REPRODUCE
>
> 0. (computer is powered off)
> 1. boot computer
> 2. the log-in screen comes up
> 3. wait a couple of minutes, the screen will dim and switch off
> 4. wait for an hour
>
> What happened: computer DIDN'T suspend
> What I expected to happen: the computer would've suspended the same as
> if it locked itself after I've logged in once.
>
> Relevant information:
>
> - desktop computer
> - mobo: M5A97 EVO R2.0
> - proc: AMD FX-8320
> - graphics: AMD Radeon HD 7790
>
> See the attached files for further info (uname,
> /proc/version_signature, dmesg, lspci -vvnn).
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-image-3.13.0-36-generic 3.13.0-36.63
> ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
> Uname: Linux 3.13.0-36-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: jan 2367 F.... pulseaudio
> /dev/snd/controlC0: jan 2367 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Mon Oct 6 09:25:50 2014
> InstallationDate: Installed on 2014-07-14 (83 days ago)
> InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
> IwConfig:
> eth0 no wireless extensions.
>
> lo no wireless extensions.
> MachineType: To be filled by O.E.M. To be filled by O.E.M.
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic
> root=UUID=6e991daa-60a1-41a6-86b9-099d96d697f2 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.13.0-36-generic N/A
> linux-backports-modules-3.13.0-36-generic N/A
> linux-firmware 1.134~gd~t
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 04/09/2014
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2501
> dmi.board.asset.tag: To be filled by ...