sometimes power button shuts down without asking

[aexl]

Current Kubuntu Feisty: pressing power button brings up the confirmation dialog in most cases. sometimes it just shuts down the system (very fast...).

[aexl (aexl)]

systemlog just tells me everyone received "TERM", no "bower button pressed".

[Rich Johnson (nixternal)]

Well, I don't know what to do with this one...

Desktop 1: Pressing the power button doesn't do anything unless I hold it down, could be a BIOS issue though with this junky mobo.

Desktop 2: It brings up the confirmation dialog. I only shutdown a couple of times, but I normally hit cancel, wait a minute and do it again. After the 20th time I gave up.

Laptop: exactly as Desktop 2.

So I can't confirm this as an issue with Kubuntu, but I am not saying this isn't possible. Seeing as Guidance controls the power, I am going to go ahead and change from kubuntu-meta to guidance. Thanks for your report.

[Luka Renko (lure)]

Is it possible that you pressed button for a bit longer?
On my HP nw8240 laptop, I need to do a short press in order to get logout dialog, otherwise the laptop just powers down. I think this is done in HW (or at least in kernel) therefore it cannot be controlled by HAL and Guidance power manager.

[SimSQ (daniel-ssq89)]

I can confirm this. Very irritating. I'm running Ubuntu+KDE on an Intel iMac, Core Duo.

But yes, need more info to know what's going on. Somebody give some instructions...

[SimSQ (daniel-ssq89)]

[Tue Jun 19 11:44:01 2007] client connected from 5581[0:0]
[Tue Jun 19 11:44:01 2007] 1 client rule loaded
[Tue Jun 19 16:12:37 2007] received event "button/power PWRF 00000080 00000001"
[Tue Jun 19 16:12:37 2007] notifying client 5478[108:108]
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] client has disconnected
[Tue Jun 19 16:12:37 2007] notifying client 5581[0:0]
[Tue Jun 19 16:12:37 2007] executing action "/etc/acpi/powerbtn.sh"
[Tue Jun 19 16:12:37 2007] BEGIN HANDLER MESSAGES
ERROR: Couldn't attach to DCOP server!
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
ERROR: Couldn't attach to DCOP server!
[Tue Jun 19 16:12:42 2007] END HANDLER MESSAGES
[Tue Jun 19 16:12:42 2007] action exited with status 0
[Tue Jun 19 16:12:42 2007] completed event "button/power PWRF 00000080 00000001"
[Tue Jun 19 16:12:52 2007] exiting
[Tue Jun 19 16:14:18 2007] starting up

[aexl (aexl)]

I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down all of them.

this (extra dcopserver) may come from a second kde session, but also (as in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives on!).

i think the named behaviour is wrong. powerbtn.sh should either
- ask the user in the currently active session
- or just hibernate without destroying anything

best aexl
ps: remarkable fact that bugtracking helped trigger the bug in this case ;-)

from /etc/acpi/powerbtn.sh:

    KDESES=`pidof dcopserver | wc -w`
    if [ $KDESES -eq 1 ] ; then
        # single KDE session -> ask user
        /usr/bin/dcop --all-sessions --all-users ksmserver ksmserver logout 1 2 0
        exit 0
    else
        # more than one KDE session - just send shutdown signal to all of them
        /usr/bin/dcop --all-sessions --all-users ksmserver ksmserver logout 0 2 0 && exit 0
    fi

[aexl (aexl)]

Now i am not so sure anymore if said was the reason. Fact is, killing second dcopserver solved the problem at first.
Power button now has no effect at all.
This looks like a different bug, but might be related, see: bug 121891

[Justin Payne (neolithium82)]

NOTE - Swtiching to linux-source issue as per ACPI debugging procedures

Hi there,
We nearly have enough, I believe to confirm this bug, although would anyone be able to bring along some additoinal information that could help diagnose this issue, such as:

Output of 'uname -a'
Output of 'sudo lspci -vv'
Output of 'sudo lspci -vvn'
Output of 'sudo dmidecode'

Thanks,
Justin

[aexl (aexl)]

...coming here as script output

[Justin Payne (neolithium82)]

I think that we have enough to confirm this bug, thank you all for taking the time to help provide information and add on to this report.

Regards,
Justin

[mlaverdiere (mlaverdiere)]

Same problem here with Kubuntu Feisty + KDE 3.5.7.

Thanks

[Thomas R. (pumbaa80)]

Let me add that analyzing the process list with grep is a rather poor hack, so the line

if ps -Af | grep -q '[k]desktop' && pidof dcopserver > /dev/null && test -x /usr/bin/dcop ; then

in /etc/acpi/powerbtn.sh might yield false positive results (such as "kate kdesktop" etc.)

The sophisticated way to do it is

if ps -C kdesktop > /dev/null [...]
or
if pidof kdesktop > /dev/null [...]

Kind regards,
  Thomas

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Stefan Bader (smb)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.