Re: apmd closes/crashes on lid close
On 2012-06-04, Robert Connolly wrote: > Sometimes apmd crashes from a system suspend, and sometimes it does not. > > Sometimes xidle runs xlock, and sometimes it does not. > > Sometimes xlock asks for a password, and sometimes it does not. > > Can anyone tell me whether they have all of these working consistently and > reliably? > > They were not working for me yesterday. This morning it all worked > perfectly. Hours later, none of it worked. > > I have these working consistently, but I don't call apm at suspend time as you were doing with your xlock command line. (note that xidle does not lock the screen if the screensaver is disabled, some video players etc do this, however it is consistent).
Re: apmd closes/crashes on lid close
dump "xset -q" and "wsconsctl -a", compare working/non-working states, check for possible race condition? -- p >"xset dpms 5 10 15" isn't doing anything either, nor "xset s 4". > >On Sun, Jun 3, 2012 at 11:40 PM, Robert Connolly < >robertconnolly1...@gmail.com> wrote: > >> Sometimes apmd crashes from a system suspend, and sometimes it does not. >> >> Sometimes xidle runs xlock, and sometimes it does not. >> >> Sometimes xlock asks for a password, and sometimes it does not. >> >> Can anyone tell me whether they have all of these working consistently and >> reliably? >> >> They were not working for me yesterday. This morning it all worked >> perfectly. Hours later, none of it worked.
Re: apmd closes/crashes on lid close
"xset dpms 5 10 15" isn't doing anything either, nor "xset s 4". On Sun, Jun 3, 2012 at 11:40 PM, Robert Connolly < robertconnolly1...@gmail.com> wrote: > Sometimes apmd crashes from a system suspend, and sometimes it does not. > > Sometimes xidle runs xlock, and sometimes it does not. > > Sometimes xlock asks for a password, and sometimes it does not. > > Can anyone tell me whether they have all of these working consistently and > reliably? > > They were not working for me yesterday. This morning it all worked > perfectly. Hours later, none of it worked.
Re: apmd closes/crashes on lid close
Sometimes apmd crashes from a system suspend, and sometimes it does not. Sometimes xidle runs xlock, and sometimes it does not. Sometimes xlock asks for a password, and sometimes it does not. Can anyone tell me whether they have all of these working consistently and reliably? They were not working for me yesterday. This morning it all worked perfectly. Hours later, none of it worked.
Re: apmd closes/crashes on lid close
On 2012-06-03, Jan Stary wrote: > On Jun 02 23:38:14, Robert Connolly wrote: >> Hello. >> >> I am running apmd without arguments from rc.conf. I am also running lid >> close suspend from sysctl.conf. When I close the lid, and open it again, >> apmd is gone from 'ps auxw'. >> >> In /etc/apm/suspend I am hitting xidle with a signal 30. > > Why are you hooking your suspend action to xidle? > What do you want to happen on a lid close, beside > the machine suspending, and why? > >> xidle is sparking >> xlock with a -startCmd apm -C, and an -endCmd apm -H. >> >> /var/log/messages and /var/log/daemon is not logging anything unusual from >> apmd. > > So you have to enter a password when the laptop comes back from suspend.
Re: apmd closes/crashes on lid close
On Sun, Jun 03, 2012 at 12:41:31AM -0700, Philip Guenther wrote:
> On Sat, Jun 2, 2012 at 11:38 PM, Robert Connolly
> wrote:
> > I am running apmd without arguments from rc.conf. I am also running lid
> > close suspend from sysctl.conf. When I close the lid, and open it again,
> > apmd is gone from 'ps auxw'.
>
> ktrace?
> run it under gdb (passing it the -d option to not go into the
> background) and see what signal kills it and where?
I'm pretty sure I ran into this same issue a while ago. I tried to use
/etc/apm/{powerup,powerdown} to switch between 'apm -C' and 'apm -A'
when undocking/docking my laptop. apmd didn't like being poked by apm
from those files. Just use apm in one of the related /etc/apm files to
reproduce.
[danh@t obj] $ cat /etc/apm/resume
apm -A
[danh@t obj] $ sudo gdb apmd
(gdb) set args '-d'
(gdb) run
Starting program: /usr/obj/usr.sbin/apmd/apmd '-d'
[New process 12159]
[... enter suspend, then resume here ...]
Terminated
Program received signal SIGPIPE, Broken pipe.
0x00020a543c6a in sendto () from /usr/lib/libc.so.64.1
(gdb) bt
#0 0x00020a543c6a in sendto () from /usr/lib/libc.so.64.1
#1 0x004020e9 in handle_client (sock_fd=Variable "sock_fd" is not
available.
) at /usr/src/usr.sbin/apmd/apmd.c:469
#2 0x004027cd in main (argc=Variable "argc" is not available.
) at /usr/src/usr.sbin/apmd/apmd.c:728
Re: apmd closes/crashes on lid close
On Jun 02 23:38:14, Robert Connolly wrote: > Hello. > > I am running apmd without arguments from rc.conf. I am also running lid > close suspend from sysctl.conf. When I close the lid, and open it again, > apmd is gone from 'ps auxw'. > > In /etc/apm/suspend I am hitting xidle with a signal 30. Why are you hooking your suspend action to xidle? What do you want to happen on a lid close, beside the machine suspending, and why? > xidle is sparking > xlock with a -startCmd apm -C, and an -endCmd apm -H. > > /var/log/messages and /var/log/daemon is not logging anything unusual from > apmd.
Re: apmd closes/crashes on lid close
On Sat, Jun 2, 2012 at 11:38 PM, Robert Connolly wrote: > I am running apmd without arguments from rc.conf. I am also running lid > close suspend from sysctl.conf. When I close the lid, and open it again, > apmd is gone from 'ps auxw'. ktrace? run it under gdb (passing it the -d option to not go into the background) and see what signal kills it and where? Philip Guenther
