Failed to hibernate session not authorized Acer Aspire 5750-9668

Bug #983879 reported by penalvch
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) uname -a
Linux monikerpc 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 i686 i686 i386 GNU/Linux

3) What is expected to happen when one clicks the Start button -> Hibernate it does so.

4) What happens instead is a window pops up noting:
Shutdown failed
Failed to hibernate session
not authorized

Following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

Hibernate specific information

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3083295/+files/dmesg

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=5f00cb9d-c358-4021-95da-a9f8737429eb ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor vt.handoff=7

cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=273ef9ea-9e00-4831-9f03-662a7d60ba46

Hibernating from text mode

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3083477/+files/dmesg

cat /sys/power/pm_test
[none] core processors platform devices freezer

cat /sys/power/disk
[platform] test testproc shutdown reboot

sudo -i

lsmod > lsmod.output.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3133878/+files/lsmod.output.txt

echo devices > /sys/power/pm_test
echo platform > /sys/power/disk
echo disk > /sys/power/state
dmesg > /tmp/dmesg-devices-platform.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3133880/+files/dmesg-devices-platform.txt

echo core > /sys/power/pm_test
echo platform > /sys/power/disk
echo disk > /sys/power/state
dmesg > /tmp/dmesg-core-platform.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3133881/+files/dmesg-core-platform.txt

echo core > /sys/power/pm_test
echo reboot > /sys/power/disk
echo disk > /sys/power/state
dmesg > /tmp/dmesg-core-reboot.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/+attachment/3133882/+files/dmesg-core-reboot.txt

+ Reproducible in mainline.
uname -a
Linux monikerpc 3.4.0-030400rc5-generic #201205011817 SMP Tue May 1 22:24:50 UTC 2012 i686 i686 i386 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: monikerpc 2006 F.... pulseaudio
                      monikerpc 2059 F.... xfce4-volumed
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0700000 irq 51'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10250504,00100100 HDA:80862805,80860101,00100000'
   Controls : 26
   Simple ctrls : 12
Date: Tue Apr 17 07:27:39 2012
HibernationDevice: RESUME=UUID=273ef9ea-9e00-4831-9f03-662a7d60ba46
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Acer Aspire 5750
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=5f00cb9d-c358-4021-95da-a9f8737429eb ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-04-06 (10 days ago)
dmi.bios.date: 02/11/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: dmi:bvnAcer:bvrV1.05:bd02/11/2011:svnAcer:pnAspire5750:pvrV1.05:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.05:
dmi.product.name: Aspire 5750
dmi.product.version: V1.05
dmi.sys.vendor: Acer

Revision history for this message
penalvch (penalvch) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :
description: updated
Revision history for this message
penalvch (penalvch) wrote :
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

I'm having the same (or a similar) issue.
I even did a fresh install of Xubuntu (for remotely related reasons), with no change in behaviour.
Here is what I observed:

The taskbar menu will show all normal menu entries (lock screen, standby, hibernate, restart, shutdown, logout).
Clicking hibernate will report failure due to "not authorized". The exact message is: "Herunterfahren fehlgeschlagen", "Kann Sitzung nicht in Ruhemodus versetzen", "not authorized". (Note that the first two messages are translated and have proper capitalization, but "not authorized" does not have either. Looks like a message from somewhere deep down that's simply passed through - trouble is that the dialog doesn't tell me where that message came from, so I can't find the true cause.)

xfce4-session-logout --hibernate will show exactly the same message dialog.

sudo xfce4-session-logout --hibernate will give "Fehler beim Abmelden" "Keine Antwort von der Sitzungsverwaltung erhalten" "The name org.xfce.SessionManager was not provided by any .service files". (Rough translations: "Error logging out" "No response received from the session manager".)

If this is really a general problem, Bug #992880 is a duplicate.

Revision history for this message
penalvch (penalvch) wrote :

Joachim Durchholz, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Some more details:

This started to happen after upgrading to 12.04. It worked fine in 11.10.

I'm using a Dell Precision M4600 laptop.

$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

$ uname -a
Linux jodel 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 UTC 2012 i686 i686 i386 GNU/Linux

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=1ca1cfd0-972c-4001-b544-c3c388e4250f ro rootflags=subvol=@ quiet splash vt.handoff=7

My bet is that this is some misconfiguration throwing a spanner into the works before the hibernate/suspend actually happens.

Revision history for this message
penalvch (penalvch) wrote :

Joachim Durchholz, please stop making comments in this report. Please follow the directions already requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983879/comments/5 .

Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Christopher M. Penalver, what happened is that I was working on my message while you gave your instructions, so please stop being rude by alleging that I'm a complete idiot and unable to follow instructions.

Re the infos you were asking for, please take a look at the bug marked as duplicate of this one. It might already cover what you were asking for; give me a yell if you need more.

penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Marking Triaged as mainline tested and all information requested in https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume is provided. This is ready for a developer to begin working on.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: kernel-bug-exists-upstream
tags: added: hibernate resume
Revision history for this message
Charlie Primero (charlieprime) wrote :

Same bug here on fresh install Chris.

Revision history for this message
penalvch (penalvch) wrote :

Charlie Primero, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Revision history for this message
penalvch (penalvch) wrote :

So, initially when I reported this bug, hibernate was enabled by default despite https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/812394 . However, it seems some Xubuntu update greyed it out, and I really am not going to chase down which one.

Anyways, I enabled Hibernate via https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html , and not only is it no longer greyed out, it works.

Marking this Status Invalid as I'm not going against the tide on a design decision (LP # 812394 ), and Hibernate works for me.

Changed in linux (Ubuntu):
importance: Medium → Low
status: Triaged → Invalid
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

To the very least, whoever made the decision to disable hibernate mode should get feedback about how many people were affected.
It would help making future informed decisions about the issue.

Also, there should be a way to discover how to re-enable hibernate mode. I was unaware of that help page about hibernate mode and hadn't found it via Google, so I was left entirely in the dark.
Mucking around with polkit shouldn't be the workaround, too. It should be an option somewhere in the system settings. With proper warnings, of course, so people don't come complaining if it doesn't work (and maybe some code that collects hardware data and gives feedback to the Ubuntu team both for "works" and "does not work" cases so that hardware can be whitelisted).

I'm not sure whether such a bug report exists.

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.