Bug 887459 - conflict in handling of power management events between xfce-power-manager and systemd
Summary: conflict in handling of power management events between xfce-power-manager an...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-power-manager
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-15 14:03 UTC by Maciek Borzecki
Modified: 2014-02-05 13:54 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:54:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Xfce 9326 0 None None None Never
Xfce 9335 0 None None None Never

Description Maciek Borzecki 2012-12-15 14:03:50 UTC
Description of problem:
systemd can handle power management events. Desktop environment can opt-out and setup inhibing of this functionality at systemd through systemd's dbus API. It seems that gnome and kde have already figured this out. Proper support is still missing under Xfce. 
Because of this conflict, it's possible that certain systems (ex. laptops) may suspend twice when suspend event is tigerred by ACPI (lid close, suspend button). First systemd handles the event, thus suspending the system and later after resume, xfce4-power-manager receives the event and suspends the system again.

Version-Release number of selected component (if applicable):
xfce4-power-manager-1.2.0-2.fc18.x86_64
systemd-libs-195-10.fc18.i686
systemd-libs-195-10.fc18.x86_64
systemd-analyze-195-10.fc18.x86_64
systemd-195-10.fc18.x86_64

How reproducible:
Alawys

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
https://bugzilla.xfce.org/show_bug.cgi?id=9335
https://bugzilla.xfce.org/show_bug.cgi?id=9326

Comment 1 Paul DeStefano 2013-02-12 06:03:22 UTC
See Bug 906978?

Comment 2 Fedora End Of Life 2013-12-21 09:55:16 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Paul DeStefano 2013-12-23 07:11:37 UTC
Hmm, so, this still doesn't work in F19, AFAIK.  It would be nice to know how this is supposed to work.  For everyone who upgraded and had to make tweaks, there has been no communication regarding how to put the pieces back together.  What is the proper configuration to handle these "power" related events?  Which system ought to be in control for Xfce users?

Comment 4 Paul DeStefano 2013-12-31 17:27:39 UTC
After upgrading to F20, I no longer have the symptom that bothered me.  Screensaver lock would not occur before suspend, despite the configuration option to do so.  That no longer occurs with F20.

In addition, systemd seems to have been reset to defaults.  I thought I had made a change to /etc/systemd/logind.conf to work around the reported bug.  But, that's gone.

So, perhaps this bug has been fully fixed?

Comment 5 Fedora End Of Life 2014-02-05 13:54:45 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.