pressing power button in kde shuts down computer immediately

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

hm, this actually sounds like https://bugs.kde.org/show_bug.cgi?id=180734

Further discussion/debugging on IRC shows that this is probably a powerbtn.sh bug.

> Further discussion/debugging on IRC shows that this is probably a powerbtn.sh bug.

That's not much help if you don't say what the bug is. powerbtn.sh in lucid is already configured to be a no-op if it detects klaptopdaemon or powerdevil running, so what's the bug here?

Also, powerbtn.sh is from acpid, not acpi-support; reassigning.

I actually filed bug 508131 about this as I wasn't sure if it should be reassigned. I'll duplicate it. (You'll find the explenation of the bug there).

Sorry, was in a bit of a rush to get the comment posted. So that people don't have to travel to the dupe, the bug is in detecting whether or not any power manager at all is running. Since it uses getXconsole from /etc/acpi/powerbtn.sh without sourcing it, it always fails to find a power manager and will always fall back to the shutdown command. Here's a debdiff based of of Philip's work to fix this.

This bug was fixed in the package acpid - 1.0.10-5ubuntu2

---------------
acpid (1.0.10-5ubuntu2) lucid; urgency=low

  * Source /usr/share/acpi-support/power-funcs in powerbtn.sh (LP: #508073)
 -- Jonathan Thomas <email address hidden> Fri, 15 Jan 2010 19:59:47 -0500

Works for me after apcid upgrade. Cheers!

@Jonathan, Has this been forwarded to Debian?

I haven't forwarded the fix, personally. It should be noted that this fix requires adding a dependency on acpi-support too, if anybody wants to forward this fix.

I am still experiencing this symptom on a fully up to date (acpid 1.0.10-5ubuntu2.1) Lucid upgrade.

What's happening is the following line in /etc/acpi/powerbtn.sh is failing because "pidof kded4" is returning 2 PIDs:

        ( test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r /proc/$(pidof kded4)/environ && su - $XUSER -c "eval $(echo -n 'export '; cat /proc/$(pidof kded4)/environ |tr '\0' '\n'|grep DBUS_SESSION_BUS_ADDRESS); qdbus org.kde.kded" | grep -q powerdevil) ; then

This is not a regression in acpid 1.0.10-5ubuntu2.1. The test line in powerbtn.sh in both 1.0.10-5ubuntu2 & 1.0.10-5ubuntu2.1 are identical. This actually might be a symptom of another problem that I have not been able to fix yet. The reason I am getting 2 PIDs for kded4 is because 1 is defunct.

I am wondering if there is a better way to detect if KDE4 is running that is more robust than "pidof kded4". Pre-Lucid, Ubuntu was using "pidof ksmserver". I have also seen "ps -efww|grep kded4|grep $XUSER|grep -v grep|grep -v defunct" being suggested.

Tom, please file a separate bug report for this follow-on issue.

Looks like there already was another bug opened for my issue, thanks.
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/553557