On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
On my system the man page for dconf is missing and "dconf help" isn't very helpful. Is there something that explains how we are supposed to use it?
Fred
-----Original Message----- From: test-bounces@lists.fedoraproject.org [mailto:test- bounces@lists.fedoraproject.org] On Behalf Of Adam Williamson Sent: Tuesday, October 25, 2011 3:41 AM To: test@lists.fedoraproject.org Subject: Power button in f16?
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
On Tue, 2011-10-25 at 08:06 +0300, Frederick William New wrote:
On my system the man page for dconf is missing and "dconf help" isn't very helpful. Is there something that explains how we are supposed to use it?
dconf-editor
Am Montag, den 24.10.2011, 17:41 -0700 schrieb Adam Williamson:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Yes, https://bugzilla.redhat.com/show_bug.cgi?id=746982
Regards, Christoph
On Tue, 2011-10-25 at 09:23 +0200, Christoph Wickert wrote:
Am Montag, den 24.10.2011, 17:41 -0700 schrieb Adam Williamson:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Thanks. That points to https://bugzilla.redhat.com/show_bug.cgi?id=722325 , which seems to be the cause for me: for GNOME it tests for gnome-power-manager, but since 3.1.x that doesn't exist any more, all the PM stuff moved to gnome-settings-daemon.
On Tue, 2011-10-25 at 11:07 -0700, Adam Williamson wrote:
On Tue, 2011-10-25 at 09:23 +0200, Christoph Wickert wrote:
Am Montag, den 24.10.2011, 17:41 -0700 schrieb Adam Williamson:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Thanks. That points to https://bugzilla.redhat.com/show_bug.cgi?id=722325 , which seems to be the cause for me: for GNOME it tests for gnome-power-manager, but since 3.1.x that doesn't exist any more, all the PM stuff moved to gnome-settings-daemon.
acpid is not part of the desktop spin, at least. And hacks like the one that is mentioned there seem a good reason to keep it off other spins as well...
On Tue, 2011-10-25 at 20:59 -0400, Matthias Clasen wrote:
On Tue, 2011-10-25 at 11:07 -0700, Adam Williamson wrote:
On Tue, 2011-10-25 at 09:23 +0200, Christoph Wickert wrote:
Am Montag, den 24.10.2011, 17:41 -0700 schrieb Adam Williamson:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Thanks. That points to https://bugzilla.redhat.com/show_bug.cgi?id=722325 , which seems to be the cause for me: for GNOME it tests for gnome-power-manager, but since 3.1.x that doesn't exist any more, all the PM stuff moved to gnome-settings-daemon.
acpid is not part of the desktop spin, at least. And hacks like the one that is mentioned there seem a good reason to keep it off other spins as well...
It is default in comps, though. So you get it if you do a default DVD install.
On Tue, 2011-10-25 at 18:04 -0700, Adam Williamson wrote:
acpid is not part of the desktop spin, at least. And hacks like the one that is mentioned there seem a good reason to keep it off other spins as well...
It is default in comps, though. So you get it if you do a default DVD install.
I would recommend to change that.
On Tue, 2011-10-25 at 20:59 -0400, Matthias Clasen wrote:
On Tue, 2011-10-25 at 11:07 -0700, Adam Williamson wrote:
On Tue, 2011-10-25 at 09:23 +0200, Christoph Wickert wrote:
Am Montag, den 24.10.2011, 17:41 -0700 schrieb Adam Williamson:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Thanks. That points to https://bugzilla.redhat.com/show_bug.cgi?id=722325 , which seems to be the cause for me: for GNOME it tests for gnome-power-manager, but since 3.1.x that doesn't exist any more, all the PM stuff moved to gnome-settings-daemon.
acpid is not part of the desktop spin, at least. And hacks like the one that is mentioned there seem a good reason to keep it off other spins as well...
Note that someone who I think is involved with acpid replied to say acpid shouldn't have to hack around desktops at all, and desktops should work around acpid. Not that I'm saying I agree or I don't, but it's certainly an alternative perspective.
On Tue, 2011-10-25 at 18:04 -0700, Adam Williamson wrote:
Note that someone who I think is involved with acpid replied to say acpid shouldn't have to hack around desktops at all, and desktops should work around acpid. Not that I'm saying I agree or I don't, but it's certainly an alternative perspective.
For the desktop spin, that is what we do. We work around it by not installing it...
On Tue, Oct 25, 2011 at 06:04:52PM -0700, Adam Williamson wrote:
Note that someone who I think is involved with acpid replied to say acpid shouldn't have to hack around desktops at all, and desktops should work around acpid. Not that I'm saying I agree or I don't, but it's certainly an alternative perspective.
Somewhat late to this, but:
acpid should certainly not be installed by default. The fact that it imposes systemwide policy for something that's inherently a user preference is an obvious issue, and it needs to go away.
On Tue, Oct 25, 2011 at 1:41 AM, Adam Williamson awilliam@redhat.com wrote:
On my laptop, pressing the 'power' button in current f16 causes the system to shut down, not suspend - even though the dconf preference says suspend.
Anyone else noticed this lately?
Yes, on my Dell e6410. I thought it use to suspend or prompt. I've got so use to using the menu as shutting the lid never did anything I can't be sure when it changed though.
Peter