[Lubuntu] XFCE Power Manager conflicts with Apcupsd?

[John Hupp]

I have not had cause to try to probe how well xfce4-power-manager does its job in general (apart from my APC UPS problem), but there was a perhaps-interesting bit of info posted to my bug report at xfce.org, saying that it depends on hal (which is not installed in Lubuntu).

But checking xfce4-power-manager Properties in Synaptic, I don't find any listed dependencies that refer to hal, so I don't know if the report of hal dependence has any weight or bearing on the problem.

That comment from the bug report:
  
  --- Comment #2 from Stephen Haffly<hafflys at earthlink.net>  ---
I believe that this is because xfce4-power-manager still depends on hal for
functionality (at least according to the web page for the utility). However,
hal has been deprecated since Fedora 16 and is no longer available. I did have
it working, but it finally seems to have been broken when Fedora 17 did an
upgrade to kernel 3.6.1 a few days ago.

I have been going around circles trying to get apcupsd running properly. It
turns out also that for some reason, having a USB keyboard plugged in was
interfering with being able to run apctest. It also seems to have been causing
problems with apcupsd, but the error message had to do with "network thread
busy," which did not make sense as I had tried several diffferent settings for
the NISIP entry in apcupsd.conf.

Still, the problem here is not apcupsd's problems, but xfce4-power-manager's
problems. I would appreciate it being fixed as it seemed to work quite well
when it was running.

On 10/2/2012 11:36 AM, John Hupp wrote:
> Since I find the same behavior on another Lubuntu 12.04 PC without 
> apcupsd installed, it's clearly not a question of a conflict between 
> xfce4-power-manager and apcupsd.
>
> I have filed a bug report against xfce4-power-manager at 
> https://bugzilla.xfce.org/show_bug.cgi?id=9345
>
> On 9/28/2012 1:13 PM, John Hupp wrote:
>> Exploring this some more, I find that XFCE Power Manager just has 0.0 
>> for all the properties it monitors for an APC Back-UPS ES 350.  And 
>> this is the case whether apcupsd is installed or not.
>>
>> So XPM is perhaps not communicating properly with whatever backend it 
>> uses to get information about the UPS, or the backend is not 
>> monitoring the UPS effectively.
>>
>> Does anyone know what XPM uses for its UPS backend?  Can it be 
>> configured to use apcupsd as its backend?  I seems that apcupsd is 
>> generating correct values for the various UPS properties.
>>
>> I'll look next at putting these questions to someone at xfce.org, but 
>> does anyone here know enough to make further progress on resolving 
>> these problems?
>>
>> On 9/27/2012 6:36 PM, John Hupp wrote:
>>> I have some initial success getting apcupsd installed to monitor and 
>>> manage the APC Back-UPS ES 350 I'm using with one of my test networks.
>>>
>>> Running "apcaccess status" gives me healthy-looking output.
>>>
>>> But pulling the usb cable that connects to the UPS should cause 
>>> apcupsd to generate an event entry in a log and also provide a 
>>> notification message.  It does neither as far as I can tell.
>>>
>>> I observe that XFCE Power Manager, which is installed by default on 
>>> Lubuntu, is also monitoring the APC and aiming to provide various 
>>> management features.
>>>
>>> Does anyone know if they can co-exist, or if they will conflict with 
>>> each other as regards the UPS?
>>>
>>> One might think of trying to use just XFCE Power Manager as an 
>>> alternative to apcupsd, but in the above test where I pulled the usb 
>>> plug, X.P.M responded by closing its indicator icon and providing no 
>>> notifications.
>>>
>>>
>>>
>>
>>
>>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-users/attachments/20121016/fbb4a76f/attachment.html>