<div dir="ltr">On Sat, Jan 14, 2012 at 19:32, Brandon Allbery <span dir="ltr"><<a href="mailto:allbery.b@gmail.com">allbery.b@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">On Sat, Jan 14, 2012 at 18:27, Jacek Generowicz <span dir="ltr"><<a href="mailto:jacek.generowicz@cern.ch" target="_blank">jacek.generowicz@cern.ch</a>></span> wrote:<br></div><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="im">Brandon Allbery wrote:<br>
> On Sat, Jan 14, 2012 at 16:58, Jacek Generowicz <<a href="mailto:jacek.generowicz@cern.ch" target="_blank">jacek.generowicz@cern.ch</a>>wrote:<br></div><div class="im">> although you may need to run xmonad under ck-start-session.</div>
</div><div class="im"><div>
<br>
</div>Hmm, ck-start-session is news to me, and inital searches didn't make<br>
me all that much wiser.<br></div></blockquote><div><br></div><div>It's part of ConsoleKit, which NetworkManager / nm-applet uses to authenticate the console user as being permitted to control wifi.</div></div></div></blockquote>
<div><br></div><div>...and to answer the question I *should* have answered: in ~/.xsession, replace "exec xmonad" with "exec ck-launch-session xmonad". </div></div><div><br></div>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>
wandering unix systems administrator (available) (412) 475-9364 vm/sms<br><br>
</div>