BTW, I just checked upower installed on my system. It seems that the methods remains the same and only the name of interface and object path were changed. Just replacing DeviceKit-Power with UPower seems to be enough.
On Tue, Mar 9, 2010 at 12:05 AM, Marty Jack <[email protected]> wrote: > It is known that DeviceKit-power would do this when you ask it to Suspend or > Hibernate. Apparently it does not send a reply. I did not fix it because it > is difficult for me to test the power stuff, it is only a warning, and the > DeviceKit support is not production quality and not meant to be enabled in a > released product. I would have fixed everything up properly when we finish > up the UPower support. > > If it is something else, I am receptive to a bug report. > > I do have a checkin ready to go that removes the wait for the reply and the > warning, but I can't test it very well on this system. > > On 03/08/2010 10:58 AM, PCMan wrote: >> try do do "env | grep DBUS" and give us the output. >> Maybe dbus is not running correctly. >> >> On Mon, Mar 8, 2010 at 9:52 PM, Andrea Florio <[email protected]> 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 Florio >>> QSI International School of Brindisi Sys Admin >>> CISCO CCNA Certified >>> openSUSE-Education Administrator >>> openSUSE Official Member (anubisg1) >>> Email: [email protected] >>> Packman Packaging Team >>> Email: [email protected] >>> Web: http://packman.links2linux.org/ >>> Cell: +39-328-7365667 >>> ------------------------------------------ >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >> >> ------------------------------------------------------------------------------ >> 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 >> > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
