4:37 p.m.
Hi,
because of previous incompatibility with xfce4-power-manager-settings
and /etc/systemd/logind.conf, I've disabled every action in logind.conf
by setting things to ignore.
Yesterday, I've finally managed to comment that out and set things
properly in xfce4-power-manager-settings as desired.
Here is what I want and what I have set in the
xfce4-power-manager-settings (except using slock, because there is no
option for used screen lock):
- When I am not connected to AC and I close the lid, lock the screen
(with slock), but do not suspend/hibernate/whatever. When I am
connected, do not lock.
- When pressed any of the buttons poweroff/suspend/hibernate, ask for
action.
- When suspending/hibernate, lock the screen with slock.
Here is, what really happens:
- Closing lid and using slock to lock the screen (only without AC) works
as expected.
- When I press poweroff or suspend button, I am only asked sometimes,
sometimes nothing happens. (When I change the action from Ask to
Suspend, it works the same, only goes to suspend sometimes, sometimes
nothing happens)
- When going to suspend and wake up, screen is unlocked.
- When I open the lid when suspended, PC wakes up (as expected), but
goes to suspend immediately again, but when I wake up for the second
time, it's not going again to suspend, it's not an infinite loop.
Basicaly, I have to wake up twice (open the lid, wake up, suspend, press
power on, wake up).
I'm using Fedora 18 64bit on Lenovo Thinpad X230. I have no idea, what's
wrong, or whom to report this.
Thanks for any help.
--
Miro Hrončok
--
Phone: +420777974800
Jabber: miro(a)hroncok.cz
7:42 p.m.
Same goes on HP. I tried to find out possibly loosing the state of the lid.
But no. Simply when wake up, shuts down immediatelly the machine, and when
I wake it up again, xfce screensaver daemon is on, but when I give the
password, the system behind is not. No wifi, no net, so drivers hasn't wake
up. I have to shut down the machine, to get back alive.....and this is
since F18 exists at all.
Thanks,
Z
2013/5/13 Miro Hrončok <mhroncok(a)redhat.com>
Hi,
because of previous incompatibility with xfce4-power-manager-settings and
/etc/systemd/logind.conf, I've disabled every action in logind.conf by
setting things to ignore.
Yesterday, I've finally managed to comment that out and set things
properly in xfce4-power-manager-settings as desired.
Here is what I want and what I have set in the
xfce4-power-manager-settings (except using slock, because there is no
option for used screen lock):
- When I am not connected to AC and I close the lid, lock the screen (with
slock), but do not suspend/hibernate/whatever. When I am connected, do not
lock.
- When pressed any of the buttons poweroff/suspend/hibernate, ask for
action.
- When suspending/hibernate, lock the screen with slock.
Here is, what really happens:
- Closing lid and using slock to lock the screen (only without AC) works
as expected.
- When I press poweroff or suspend button, I am only asked sometimes,
sometimes nothing happens. (When I change the action from Ask to Suspend,
it works the same, only goes to suspend sometimes, sometimes nothing
happens)
- When going to suspend and wake up, screen is unlocked.
- When I open the lid when suspended, PC wakes up (as expected), but goes
to suspend immediately again, but when I wake up for the second time, it's
not going again to suspend, it's not an infinite loop. Basicaly, I have to
wake up twice (open the lid, wake up, suspend, press power on, wake up).
I'm using Fedora 18 64bit on Lenovo Thinpad X230. I have no idea, what's
wrong, or whom to report this.
Thanks for any help.
--
Miro Hrončok
--
Phone: +420777974800
Jabber: miro(a)hroncok.cz
______________________________**_________________
xfce mailing list
xfce(a)lists.fedoraproject.org
https://admin.fedoraproject.**org/mailman/listinfo/xfce<https://admin....
--
PGP: 06853DF7
12:32 p.m.
On Mon, 13 May 2013 23:37:27 +0200
Miro Hrončok <mhroncok(a)redhat.com> wrote:
...snip...
I'm using Fedora 18 64bit on Lenovo Thinpad X230. I have no
idea,
what's wrong, or whom to report this.
Thanks for any help.
yeah, this whole area has been a mess of late. ;( Sorry.
I really hope we have it all a lot better in f19.
The f18 double suspend was something I saw here from time to time, but
could never track down. Some folks mentioned it was a systemd bug, but
I never could nail it down enough to report it. ;(
So, all the issues you note I think are in xfce4-power-manager and
systemd interaction. In f18, xfce4-power-manager didn't know anything
about systemd or talk to it really in any way, so if systemd was set to
handle those events, it just did and xfce4-power-manager didn't do
anything. Since you have told it not to do that, xfce4-power-manager
should be handling them, so it sounds like a bug there.
In f19 xfce4-power-manager now queries systemd correctly, so it can ask
systemd to suspend, or whatever. There's no longer any need to tweak
systemd settings, xfce4-power-manager inhibits where it needs to. Also
in f18 xfce4-power-manager used upower to do the suspend/hibernate, but
it no longer does that in f19, so it uses systemd instead.
So, I guess short term I can try and figure out whats going wrong with
xfce4-power-manager in f18... and perhaps you could try a f19 live
media and see if the problems persist there?
kevin
2:21 a.m.
Report from F19. Nothing changed. Haven't got double wakeup yet, but
screen is not locked after suspend and power button does nothing.
So 18. květen 2013, 19:32:23 CEST, Kevin Fenzi napsal:
On Mon, 13 May 2013 23:37:27 +0200
Miro Hrončok <mhroncok(a)redhat.com> wrote:
...snip...
> I'm using Fedora 18 64bit on Lenovo Thinpad X230. I have no idea,
> what's wrong, or whom to report this.
>
> Thanks for any help.
yeah, this whole area has been a mess of late. ;( Sorry.
I really hope we have it all a lot better in f19.
The f18 double suspend was something I saw here from time to time, but
could never track down. Some folks mentioned it was a systemd bug, but
I never could nail it down enough to report it. ;(
So, all the issues you note I think are in xfce4-power-manager and
systemd interaction. In f18, xfce4-power-manager didn't know anything
about systemd or talk to it really in any way, so if systemd was set to
handle those events, it just did and xfce4-power-manager didn't do
anything. Since you have told it not to do that, xfce4-power-manager
should be handling them, so it sounds like a bug there.
In f19 xfce4-power-manager now queries systemd correctly, so it can ask
systemd to suspend, or whatever. There's no longer any need to tweak
systemd settings, xfce4-power-manager inhibits where it needs to. Also
in f18 xfce4-power-manager used upower to do the suspend/hibernate, but
it no longer does that in f19, so it uses systemd instead.
So, I guess short term I can try and figure out whats going wrong with
xfce4-power-manager in f18... and perhaps you could try a f19 live
media and see if the problems persist there?
kevin
_______________________________________________
xfce mailing list
xfce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xfce
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4:41 a.m.
Finally, double wakeup. Result: Nothing has changed.
St 3. červenec 2013, 09:21:31 CEST, Miro Hrončok napsal:
Report from F19. Nothing changed. Haven't got double wakeup yet,
but
screen is not locked after suspend and power button does nothing.
So 18. květen 2013, 19:32:23 CEST, Kevin Fenzi napsal:
> On Mon, 13 May 2013 23:37:27 +0200
> Miro Hrončok <mhroncok(a)redhat.com> wrote:
>
> ...snip...
>
>> I'm using Fedora 18 64bit on Lenovo Thinpad X230. I have no idea,
>> what's wrong, or whom to report this.
>>
>> Thanks for any help.
>
> yeah, this whole area has been a mess of late. ;( Sorry.
>
> I really hope we have it all a lot better in f19.
>
> The f18 double suspend was something I saw here from time to time, but
> could never track down. Some folks mentioned it was a systemd bug, but
> I never could nail it down enough to report it. ;(
>
> So, all the issues you note I think are in xfce4-power-manager and
> systemd interaction. In f18, xfce4-power-manager didn't know anything
> about systemd or talk to it really in any way, so if systemd was set to
> handle those events, it just did and xfce4-power-manager didn't do
> anything. Since you have told it not to do that, xfce4-power-manager
> should be handling them, so it sounds like a bug there.
>
> In f19 xfce4-power-manager now queries systemd correctly, so it can ask
> systemd to suspend, or whatever. There's no longer any need to tweak
> systemd settings, xfce4-power-manager inhibits where it needs to. Also
> in f18 xfce4-power-manager used upower to do the suspend/hibernate, but
> it no longer does that in f19, so it uses systemd instead.
>
> So, I guess short term I can try and figure out whats going wrong with
> xfce4-power-manager in f18... and perhaps you could try a f19 live
> media and see if the problems persist there?
>
> kevin
>
>
> _______________________________________________
> xfce mailing list
> xfce(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xfce
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
xfce mailing list
xfce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xfce
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
11:34 a.m.
On Wed, 03 Jul 2013 11:41:32 +0200
Miro Hrončok <mhroncok(a)redhat.com> wrote:
Finally, double wakeup. Result: Nothing has changed.
This is on the same machine upgraded to f19 or a fresh install?
Perhaps there's something strange going on in your user settings?
Can you try making a new user, login as them and see if the problem
persists?
kevin
12:57 p.m.
Hi Miro,
hi Kevin,
I can at least confirm a doubled suspending or standby when I close the
lid while the system's writing to swap / disk before switching off.
Maybe systemd interferes vs. the desktop power manager (using XFPM
here). Difficult to reproduce and not relevant to me for daily usage.
Maybe my information helps to reproduce or it is another bug. Not sure.
Regards,
Raphael
On Wed, 03 Jul 2013 11:41:32 +0200
Miro Hrončok <mhroncok at redhat.com> wrote:
> Finally, double wakeup. Result: Nothing has changed.
This is on the same machine upgraded to f19 or a fresh install?
Perhaps there's something strange going on in your user settings?
Can you try making a new user, login as them and see if the problem
persists?
kevin
3948
days inactive
3999
days old
6 comments
4 participants
participants (4)
-
Kevin Fenzi -
Miro Hrončok -
Raphael Groner -
Zoltan Hoppar