On 1/2/2012 5:56 PM, Robert Moskowitz wrote:
So I tried:
systemctl status net.reactivated.Fprint
and got:
Failed to issue method call: Unit name net.reactivated.Fprint is not valid.
Now what?
due to messed up reply, this response only went to OP - the following
fixed the issue:
Run aut
Why oh why is it now so complicated chkconfig was usable by the
average skilled user; systemctl is NOT!
On 01/01/2012 08:03 AM, Claude Jones wrote:
On 12/31/2011 10:15 PM, Robert Moskowitz wrote:
With the resent talk about dbus problems, I did a grep of messages for
dbus and found FREQUENT
On Sun, 2012-01-01 at 08:03 -0500, Claude Jones wrote:
> On 12/31/2011 10:15 PM, Robert Moskowitz wrote:
> > What is Fprint and why is it getting reactivated?
>
> It's the fingerprint reader driver.
> Why it's being reactivated I don't know.
While I don't understand the specific details, I'm fair
On 12/31/2011 10:15 PM, Robert Moskowitz wrote:
With the resent talk about dbus problems, I did a grep of messages for
dbus and found FREQUENT:
Dec 31 21:59:50 lx120e dbus-daemon[981]: dbus[981]: [system] Activating
service name='net.reactivated.Fprint' (using servicehelper)
Dec 31 21:59:50 lx12
With the resent talk about dbus problems, I did a grep of messages for
dbus and found FREQUENT:
Dec 31 21:59:50 lx120e dbus-daemon[981]: dbus[981]: [system] Activating
service name='net.reactivated.Fprint' (using servicehelper)
Dec 31 21:59:50 lx120e dbus[981]: [system] Activating service
name
