[Bug 268734] Re: immediate shutdown after pressing shutdown button
Bug Watch Updater
268734 at bugs.launchpad.net
Fri Oct 27 14:49:45 UTC 2017
Launchpad has imported 20 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=483417.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2009-02-01T01:24:10+00:00 l wrote:
Description of problem: the file /etc/acpi/actions/power.sh should be
modified to check if KDE's power-management applet (plasmoid) is
running.
Version-Release number of selected component (if applicable): acpid-1.0.6-9.fc10
Actual results: if the power-button is pressed while running KDE's
power-management applet, the system shuts down
Expected results: instead of shutting down, the system should present the standard logout/poweroff/restart dialog
Additional info: I don't have the skills to fix this so I changed my /etc/acpi/actions/power.sh like so, starting at line 19:
# Check that there is a power manager, otherwise shut down.
[ "$uid_session" ] || shutdown -h now
#[ "$uid_session" ] &&
#ps axo uid,cmd | \
#awk '
# $1 == '$uid_session' &&
# ($2 ~ /gnome-power-manager/ || $2 ~ /kpowersave/) \
# { found = 1; exit }
# END { exit !found }
#' ||
# shutdown -h now
In this way, if there's an X11 session running, pushing the power button
does not shutdown the system and KDE's power-management plasmoid takes
control.
I don't have kpowersave installed as this is not the default in KDE
4.2.0.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/15
------------------------------------------------------------------------
On 2009-02-01T01:25:10+00:00 l wrote:
By the way, this is similar to bug 169476
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/16
------------------------------------------------------------------------
On 2009-02-01T03:07:12+00:00 Rex wrote:
Also consider guidance-power-manager, which is the F-10/kde default.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/17
------------------------------------------------------------------------
On 2009-02-03T10:52:34+00:00 Jaroslav wrote:
For guidance it's easy:
# ($2 ~ /gnome-power-manager/ || $2 ~ /kpowersave/ || $3 ~ /guidance-power-manager/) \
Question is how to determine PowerDevil status? It's KDED module, so
does not appear in list of processes. Some distributions only tests if
kded4 process is running - it should be enough assume that some power
manager is running but... Another approach is to use DBUS -
org.kde.powerdevilsystem.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/18
------------------------------------------------------------------------
On 2009-02-03T11:07:06+00:00 Zdenek wrote:
I vote for kded4 check only. This test should be enough these days.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/19
------------------------------------------------------------------------
On 2009-02-03T13:05:35+00:00 Rex wrote:
removing from kde42 blocker, it's not a regression or kde42 specific.
the dbus idea looks sounds interesting, but checking for a KDE session, ie, not processing
if "${KDE_FULL_SESSION}" == "true"
is agreeable too.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/20
------------------------------------------------------------------------
On 2009-02-03T13:19:56+00:00 Jaroslav wrote:
I think it's KDE 4 regression - users expect dialog not direct shutdown
and it's KDE 4.2 specific too - PowerDevil is new feature and we have to
check if it's running. So for me it's blocker :)
This check sounds pretty easy but again we have to believe that some
power management is running on top of KDE, haven't we? I hope it's 99.9%
sure...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/21
------------------------------------------------------------------------
On 2009-02-03T13:38:13+00:00 Rex wrote:
It's a regression since F-8 true... :0 but blocking the 4.2 update for
this? No.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/22
------------------------------------------------------------------------
On 2009-02-03T15:53:11+00:00 Kevin wrote:
Will KDE_FULL_SESSION be set at that point? It's only set for processes
started from within the session.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/24
------------------------------------------------------------------------
On 2009-02-03T16:03:49+00:00 Rex wrote:
You're right, nevermind. dbus queries may be the way to go.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/25
------------------------------------------------------------------------
On 2009-02-03T19:43:15+00:00 Rex wrote:
The compromise idea from the kde-sig meeting earlier today was to simply
add a check for a "kded4" process (which is what opensuse apparently
does here too), so
# ($2 ~ /gnome-power-manager/ || $2 ~ /kded4/) \
should do the trick.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/26
------------------------------------------------------------------------
On 2009-02-04T06:46:16+00:00 Zdenek wrote:
I agree with rdieter at math.unl.edu. I'm going to add two more checks.
First one for guidance-power-manager and second one for kded4.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/27
------------------------------------------------------------------------
On 2009-02-05T02:17:34+00:00 Fedora wrote:
acpid-1.0.6-10.fc10 has been pushed to the Fedora 10 stable repository.
If problems still persist, please make note of it in this bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/28
------------------------------------------------------------------------
On 2009-02-08T11:29:04+00:00 l wrote:
All swell now. Thanks a million!!!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/29
------------------------------------------------------------------------
On 2009-02-11T14:11:15+00:00 Lukáš wrote:
As a followup, here's a quick method (Qt-way), to check for PowerDevil's
presence:
QDBusInterface kdedInterface("org.kde.kded", "/kded", "org.kde.kded");
QDBusReply<QStringList> reply = kdedInterface.call("loadedModules");
if (reply.isValid() && reply.value().contains("powerdevil"))
{
// we are alive
}
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/30
------------------------------------------------------------------------
On 2009-02-11T16:28:53+00:00 Kevin wrote:
But that only works within a session, as it needs to connect to the
D-Bus session bus.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/31
------------------------------------------------------------------------
On 2009-02-18T03:18:09+00:00 Sergio wrote:
(In reply to comment #0)
>
> In this way, if there's an X11 session running, pushing the power button does
> not shutdown the system and KDE's power-management plasmoid takes control.
>
> I don't have kpowersave installed as this is not the default in KDE 4.2.0.
Hi, have you something else that substitute kpowersave , to change
CPU Frequency Policy and active schema of power management ?
thanks,
BTW: kpowersave seems not obey to power manager profiles on system
settings
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/32
------------------------------------------------------------------------
On 2009-02-18T03:33:36+00:00 Kevin wrote:
Add a battery plasmoid to the panel. That plasmoid integrates with
PowerDevil, which is also what the settings in System Settings are for.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/33
------------------------------------------------------------------------
On 2009-02-18T04:06:35+00:00 Sergio wrote:
Are you talking about Battery Monitor v1.0 ?
Doesn't have nothing but batt status
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/34
------------------------------------------------------------------------
On 2009-02-18T04:08:33+00:00 Kevin wrote:
I'm talking about the applet/widget/plasmoid which comes with KDE 4.2.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/comments/35
** Changed in: acpid (Fedora)
Importance: Unknown => Low
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to acpid in Ubuntu.
https://bugs.launchpad.net/bugs/268734
Title:
immediate shutdown after pressing shutdown button
Status in acpid package in Ubuntu:
Fix Released
Status in acpi-support package in Debian:
Fix Released
Status in acpid package in Fedora:
Fix Released
Bug description:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu intrepid (development branch)
Release: 8.10
(kubuntu alpha5 with latest updates)
2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
no specific package
3) What you expected to happen
pressing the shutdown button should start a dialog where the user can choose whether to shutdown or not. when working on the tty1 the button should be hit twice or something like that
4) What happened instead
the system began shutdown without user confirmation immediate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/268734/+subscriptions
More information about the foundations-bugs
mailing list