How odd. I don't get that at all, it works perfectly with ConsoleKit, HAL, and DeviceKit, except for the issue with DeviceKit that I already mentioned. I suppose ssh in (you can't debug once it puts up the fullscreen window), step it in the debugger, and see what it is doing when it gets the error. Note it is the System D-Bus instance that you need running for this, not the Session.
On 03/08/2010 12:33 PM, Andrea Florio wrote: > Il 08/03/2010 15:11, Marty Jack ha scritto: >> What button did you press, or did this happen right away when you ran it? >> > > no buttons... i get this when i rn lxsession-logout manually from shell. > > i did it, because pressing the icon on lxpanel took several seconds > before show the logout screen. > > btw DBUS looks to working correctly: > > anu...@suse-netbook:~> env | grep DBUS > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ZQ0Ysv1xTi,guid=2423bdae98df2ae37860c5254b953333 > > actually i have dbus 1.2.16 > >> On 03/08/2010 08:52 AM, Andrea Florio wrote: >>> running lxsession-logout i receive that: >>> >>> ** (lxsession-logout:2513): WARNING **: dbus-interface.c:71: DBUS: Did >>> not receive a reply. Possible causes include: the remote application did >>> not send a reply, the message bus security policy blocked the reply, the >>> reply timeout expired, or the network connection was broken. >>> >>> what's wrong here? >>> >>> Andrea > > Andrea > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
