Resuming from Suspend cause power button action to be called

Bug #272587 reported by PhilT on 2008-09-20
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
acpi (Ubuntu)
Undecided
Unassigned
acpi-support (Ubuntu)
Undecided
Unassigned
gnome-power-manager (Ubuntu)
Undecided
Unassigned

Bug Description

I've just installed Alpha 6 of Intrepid and tested it on my system. I noticed that when resuming from suspend the power button action is called. The default power button action is set to "Ask Me" so on resume (and once password is entered) the "Log Out of the Session" dialog is displayed. If I change the action (in Preferences->Power Management->General) to say Shutdown my laptop briefly comes on (I see the desktop for a fraction of a second but don't enter my password) then proceeds to shutdown. I have a HP Voodoo Envy 133 with Intel GS965 chipset.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I've been unable to recreate this bug using Intrepid. Could you please include the version of gnome-power-manager that you are using via 'apt-cache policy gnome-power-manager'? Thanks in advance.

Download full text (11.5 KiB)

gnome-power-manager:
  Installed: 2.23.91-0ubuntu2
  Candidate: 2.23.91-0ubuntu2
  Version table:
 *** 2.23.91-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Here is a dmesg output of a suspend and resume:

[ 4845.865421] atkbd.c: Unknown key pressed (translated set 2, code 0xff
on isa0060/serio0).
[ 4845.865435] atkbd.c: Use 'setkeycodes e07f <keycode>' to make it known.
[ 4848.599240] wlan0: disassociating by local choice (reason=3)
[ 4850.622065] iwlagn 0000:06:00.0: PCI INT A disabled
[ 4850.805135] PM: Syncing filesystems ... done.
[ 4850.807099] PM: Preparing system for mem sleep
[ 4850.807889] Freezing user space processes ... (elapsed 0.00 seconds)
done.
[ 4850.809209] Freezing remaining freezable tasks ... (elapsed 0.00
seconds) done.
[ 4850.809267] PM: Entering mem sleep
[ 4850.809269] Suspending console(s) (use no_console_suspend to debug)
[ 4850.810103] pci 0000:00:02.0: PCI INT A disabled
[ 4850.840117] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4850.841348] sd 0:0:0:0: [sda] Stopping disk
[ 4851.624246] ahci 0000:02:00.0: PCI INT A disabled
[ 4851.640274] ata_piix 0000:00:1f.2: PCI INT B disabled
[ 4851.656184] ata2: port disabled. ignoring.
[ 4851.656256] ata_piix 0000:00:1f.1: PCI INT A disabled
[ 4851.656403] ehci_hcd 0000:00:1d.7: PCI INT A disabled
[ 4851.672153] uhci_hcd 0000:00:1d.2: PCI INT C disabled
[ 4851.672199] uhci_hcd 0000:00:1d.1: PCI INT B disabled
[ 4851.672247] uhci_hcd 0000:00:1d.0: PCI INT A disabled
[ 4851.672427] HDA Intel 0000:00:1b.0: PCI INT A disabled
[ 4851.688174] ehci_hcd 0000:00:1a.7: PCI INT C disabled
[ 4851.704149] uhci_hcd 0000:00:1a.1: PCI INT B disabled
[ 4851.704195] uhci_hcd 0000:00:1a.0: PCI INT A disabled
[ 4851.704303] PM: suspend devices took 0.896 seconds
[ 4851.704811] ACPI: Preparing to enter system sleep state S3
[ 4854.704064] Disabling non-boot CPUs ...
[ 4854.808026] CPU 1 is now offline
[ 4854.808030] SMP alternatives: switching to UP code
[ 4854.818707] CPU0 attaching NULL sched-domain.
[ 4854.818709] CPU1 attaching NULL sched-domain.
[ 4854.818749] CPU0 attaching sched-domain:
[ 4854.818751] domain 0: span 0 level CPU
[ 4854.818753] groups: 0
[ 4854.818967] CPU1 is down
[ 4854.819074] Extended CMOS year: 2000
[ 4854.819074] Back to C!
[ 4854.819074] Extended CMOS year: 2000
[ 4854.819074] Enabling non-boot CPUs ...
[ 4854.819074] SMP alternatives: switching to SMP code
[ 4854.830470] Booting processor 1/1 ip 6000
[ 4854.708190] Initializing CPU#1
[ 4854.708190] Calibrating delay using timer specific routine.. 3591.05
BogoMIPS (lpj=7182110)
[ 4854.708190] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 4854.708190] CPU: L2 cache: 4096K
[ 4854.708190] CPU: Physical Processor ID: 0
[ 4854.708190] CPU: Processor Core ID: 1
[ 4854.920714] CPU1: Intel(R) Core(TM)2 Duo CPU P7700 @ 1.80GHz
stepping 0b
[ 4854.920759] CPU0 attaching NULL sched-domain.
[ 4854.924752] Switched to high resolution mode on CPU 1
[ 4854.928021] CPU0 attaching sched-domain:
[ 4854.928024] domain 0: span 0-1 level MC
[ 4854.928026] groups: 0 1
[ 4854.928029] domain 1: span 0-1 level CPU
[ 4854.928031] groups: 0-1
[ 4854.928034] CPU1 a...

PhilT (phil-electricvisions) wrote :
Download full text (11.3 KiB)

gnome-power-manager:
  Installed: 2.23.91-0ubuntu2
  Candidate: 2.23.91-0ubuntu2
  Version table:
*** 2.23.91-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Here is a dmesg output of a suspend and resume:

[ 4845.865421] atkbd.c: Unknown key pressed (translated set 2, code 0xff
on isa0060/serio0).
[ 4845.865435] atkbd.c: Use 'setkeycodes e07f <keycode>' to make it known.
[ 4848.599240] wlan0: disassociating by local choice (reason=3)
[ 4850.622065] iwlagn 0000:06:00.0: PCI INT A disabled
[ 4850.805135] PM: Syncing filesystems ... done.
[ 4850.807099] PM: Preparing system for mem sleep
[ 4850.807889] Freezing user space processes ... (elapsed 0.00 seconds)
done.
[ 4850.809209] Freezing remaining freezable tasks ... (elapsed 0.00
seconds) done.
[ 4850.809267] PM: Entering mem sleep
[ 4850.809269] Suspending console(s) (use no_console_suspend to debug)
[ 4850.810103] pci 0000:00:02.0: PCI INT A disabled
[ 4850.840117] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4850.841348] sd 0:0:0:0: [sda] Stopping disk
[ 4851.624246] ahci 0000:02:00.0: PCI INT A disabled
[ 4851.640274] ata_piix 0000:00:1f.2: PCI INT B disabled
[ 4851.656184] ata2: port disabled. ignoring.
[ 4851.656256] ata_piix 0000:00:1f.1: PCI INT A disabled
[ 4851.656403] ehci_hcd 0000:00:1d.7: PCI INT A disabled
[ 4851.672153] uhci_hcd 0000:00:1d.2: PCI INT C disabled
[ 4851.672199] uhci_hcd 0000:00:1d.1: PCI INT B disabled
[ 4851.672247] uhci_hcd 0000:00:1d.0: PCI INT A disabled
[ 4851.672427] HDA Intel 0000:00:1b.0: PCI INT A disabled
[ 4851.688174] ehci_hcd 0000:00:1a.7: PCI INT C disabled
[ 4851.704149] uhci_hcd 0000:00:1a.1: PCI INT B disabled
[ 4851.704195] uhci_hcd 0000:00:1a.0: PCI INT A disabled
[ 4851.704303] PM: suspend devices took 0.896 seconds
[ 4851.704811] ACPI: Preparing to enter system sleep state S3
[ 4854.704064] Disabling non-boot CPUs ...
[ 4854.808026] CPU 1 is now offline
[ 4854.808030] SMP alternatives: switching to UP code
[ 4854.818707] CPU0 attaching NULL sched-domain.
[ 4854.818709] CPU1 attaching NULL sched-domain.
[ 4854.818749] CPU0 attaching sched-domain:
[ 4854.818751] domain 0: span 0 level CPU
[ 4854.818753] groups: 0
[ 4854.818967] CPU1 is down
[ 4854.819074] Extended CMOS year: 2000
[ 4854.819074] Back to C!
[ 4854.819074] Extended CMOS year: 2000
[ 4854.819074] Enabling non-boot CPUs ...
[ 4854.819074] SMP alternatives: switching to SMP code
[ 4854.830470] Booting processor 1/1 ip 6000
[ 4854.708190] Initializing CPU#1
[ 4854.708190] Calibrating delay using timer specific routine.. 3591.05
BogoMIPS (lpj=7182110)
[ 4854.708190] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 4854.708190] CPU: L2 cache: 4096K
[ 4854.708190] CPU: Physical Processor ID: 0
[ 4854.708190] CPU: Processor Core ID: 1
[ 4854.920714] CPU1: Intel(R) Core(TM)2 Duo CPU P7700 @ 1.80GHz
stepping 0b
[ 4854.920759] CPU0 attaching NULL sched-domain.
[ 4854.924752] Switched to high resolution mode on CPU 1
[ 4854.928021] CPU0 attaching sched-domain:
[ 4854.928024] domain 0: span 0-1 level MC
[ 4854.928026] groups: 0 1
[ 4854.928029] domain 1: span 0-1 level CPU
[ 4854.928031] groups: 0-1
[ 4854.928034] CPU1 attachi...

PhilT (phil-electricvisions) wrote :

After suspending by closing the lid then resuming by opening it again I see the login screen:

PhilT (phil-electricvisions) wrote :

Then after I login I see the logout dialog.

If there are any other logs or something I can look at let me know.

PhilT (phil-electricvisions) wrote :

I've done some more digging and found what I think could be the reason I'm seeing this behavior.

I did an lshal -m then closed the lid waited a minute and opened it again. This is what came back:

14:56:06.058: computer property power_management.is_powersave_set = true
14:56:11.080: computer_logicaldev_input_2 property button.state.value = true
14:56:11.081: computer_logicaldev_input_2 condition ButtonPressed = lid
*** I OPENED THE LID ***
14:57:23.281: computer_power_supply_battery_BAT0 property battery.remaining_time = 19027 (0x4a53) (new)
14:57:23.284: computer_power_supply_battery_BAT0 property battery.charge_level.rate = 6149 (0x1805)
14:57:23.285: computer_power_supply_battery_BAT0 property battery.reporting.rate = 6149 (0x1805)
14:57:23.285: computer_power_supply_battery_BAT0 property battery.voltage.current = 12444 (0x309c)
14:57:23.286: computer_logicaldev_input_1 condition ButtonPressed = power
14:57:23.286: computer_logicaldev_input_2 property button.state.value = false
14:57:23.286: computer_logicaldev_input_2 condition ButtonPressed = lid
14:57:23.423: usb_device_4f2_b036_SN0001_if0_video4linux removed
14:57:23.424: usb_device_4f2_b036_SN0001_if0_logicaldev_input removed
14:57:23.466: usb_device_4f2_b036_SN0001_if0_video4linux added
14:57:23.737: usb_device_4f2_b036_SN0001_if0_logicaldev_input added

Here is another output from lshal this time I selected Suspend from the UserSwitcher menu. To resume I just pressed the spacebar. Here is what came back:

****** I PRESSED THE SPACEBAR ********
15:27:22.200: computer_power_supply_battery_BAT0 property battery.voltage.current = 12522 (0x30ea)
15:27:22.227: computer_logicaldev_input_1 condition ButtonPressed = power
15:27:22.227: usb_device_4f2_b036_SN0001_if0_video4linux removed
15:27:22.227: usb_device_4f2_b036_SN0001_if0_logicaldev_input removed
15:27:22.271: usb_device_4f2_b036_SN0001_if0_video4linux added
15:27:22.002: usb_device_4f2_b036_SN0001_if0_logicaldev_input added

So I guess the question is: should there be a power button event when resuming? Is there a way I can ignore this event?

Scott Howard (showard314) wrote :

Thanks for the report and the detective work. Does this bug still exist in Jaunty?

The report demonstrates the power button event and this bug is described in the description of bug #44058, so I'm marking it confirmed.

The description of bug #44058: "When manually choosing for suspend (through System -> Logout), this works fine (although I keep getting the logout window when I resume, but that might be a different bug)."

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Confirmed

Yes it's still happening in Jaunty. Tested it just now. This is on an
upgrade however rather than a clean install. As a workaround I went into the
gconf-editor and under gnome-power-manager in apps changed the power button
to nothing. There doesn't seem a way to select this option in power
management preferences.

2009/5/22 Scott Howard <email address hidden>

> Thanks for the report and the detective work. Does this bug still exist
> in Jaunty?
>
> The report demonstrates the power button event and this bug is described
> in the description of bug #44058, so I'm marking it confirmed.
>
> The description of bug #44058: "When manually choosing for suspend
> (through System -> Logout), this works fine (although I keep getting the
> logout window when I resume, but that might be a different bug)."
>
> ** Changed in: gnome-power-manager (Ubuntu)
> Status: Incomplete => Confirmed
>
> --
> Resuming from Suspend cause power button action to be called
> https://bugs.launchpad.net/bugs/272587
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gnome-power-manager” source package in Ubuntu: Confirmed
>
> Bug description:
> I've just installed Alpha 6 of Intrepid and tested it on my system. I
> noticed that when resuming from suspend the power button action is called.
> The default power button action is set to "Ask Me" so on resume (and once
> password is entered) the "Log Out of the Session" dialog is displayed. If I
> change the action (in Preferences->Power Management->General) to say
> Shutdown my laptop briefly comes on (I see the desktop for a fraction of a
> second but don't enter my password) then proceeds to shutdown. I have a HP
> Voodoo Envy 133 with Intel GS965 chipset.
>

Scott Howard (showard314) wrote :

Thanks for checking the bug in Jaunty. I'm marking the GPM bug as invalid since GPM is "properly" acting on a "ButtonPressed = power power-button event", and am assigning this bug as confirmed as acpi and acpi-support.

Changed in gnome-power-manager (Ubuntu):
status: Confirmed → Invalid
Changed in acpi-support (Ubuntu):
status: New → Confirmed
Changed in acpi (Ubuntu):
status: New → Confirmed
Steve Langasek (vorlon) wrote :

This is not a bug in 'acpi', which is an unrelated Ubuntu package. Marking invalid.

Changed in acpi (Ubuntu):
status: Confirmed → Invalid
Steve Langasek (vorlon) wrote :

PhilT,

If you stop acpid ('sudo service acpid stop'), does this problem persist?

I suspect that this is a linux kernel bug, not a bug in acpi-support.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers