Sorry, I had discarded my reply and started another one and forgot to
include the opensuse list (DOH!).
I will uninstall kpowersave, good idea.
Thanks alot for the advice.
Nick
On 5/9/07, Joachim Schrod <[EMAIL PROTECTED]> wrote:
>>>>> "NJ" == Nick Jones <[EMAIL PROTECTED]> writes:
>> Maybe the check for ac-power is wrong, or whatever.
NJ> It is a tower. This below here looks fishy. If either of those 1's
NJ> is the exit status of the function on_ac_power then HAL is screwed up
NJ> or something.
NJ> + test -x /usr/bin/on_ac_power
NJ> + on_ac_power -q
NJ> + '[' 1 = 1 ']'
NJ> + exit 0
NJ> + rm -rf /tmp/run-crons.lp9846
Well, that's the cause of your problems:
on_ac_power -q
returns with the exit code 1. If this is not a laptop in battery mode,
it should return with an exit code 0.
But now we're at the end of the stuff that I know -- it will be better
to send your last response to me again to the opensuse mailing list.
(In fact, it is always better to send responses to the list; so that
others in your situation can look up the answer in the archives as
well.) Perhaps somebody else on the list can tell you why
/usr/bin/on_ac_power returns with a wrong result.
Of course, as a quick workaround, you can use
chmod -x /usr/bin/on_ac_power
But this might break again if some update package appears for
powersave.
Or, if your system is not a laptop, you might want to remove the
package powersave (and kpowersave) and get rid of the whole problem. :-)
Best,
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
Nick Jones
University of Iowa
Dept of Neurology
Systems Analyst
319-356-0451
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
