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='net.reactivated.Fprint' (using servicehelper)

Dec 31 21:59:50 lx120e dbus-daemon[981]: Launching FprintObject
Dec 31 21:59:50 lx120e dbus-daemon[981]: dbus[981]: [system]
Successfully activated service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus[981]: [system] Successfully activated
service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint

Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: entering main loop

What is Fprint and why is it getting reactivated?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

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 lx120e dbus[981]: [system] Activating service
name='net.reactivated.Fprint' (using servicehelper)
Dec 31 21:59:50 lx120e dbus-daemon[981]: Launching FprintObject
Dec 31 21:59:50 lx120e dbus-daemon[981]: dbus[981]: [system]
Successfully activated service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus[981]: [system] Successfully activated
service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint
Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: entering main loop

What is Fprint and why is it getting reactivated?


It's the fingerprint reader driver.
Why it's being reactivated I don't know.
This page should help you figure out how to turn it off if you don't
need it: http://fedoraproject.org/wiki/Systemd


--
Claude Jones
Brunswick, MD, USA
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

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 fairly certain the
"net.reactivated" portion stores the D-Bus interface name - usually the
reverse of the domain name for the project's own website.

For example, most of GNOME's D-Bus stuff is under the interface
"org.gnome", and there are also utilities (such as the Telepathy
messaging stack) hosted on FreeDesktop.org which use the interface
"org.freedesktop".

I imagine Fprint is using the "net.reactivated" interface name because
"reactivated.net" is the website of its primary author, Daniel Drake.

Hope that helps a bit, and Happy New Year to all.
--
Peter Gordon (codergeek42) <peter@thecodergeek.com>
Who am I? :: http://thecodergeek.com/about-me

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

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:

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='net.reactivated.Fprint' (using servicehelper)
Dec 31 21:59:50 lx120e dbus-daemon[981]: Launching FprintObject
Dec 31 21:59:50 lx120e dbus-daemon[981]: dbus[981]: [system]
Successfully activated service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus[981]: [system] Successfully activated
service 'net.reactivated.Fprint'
Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint
Dec 31 21:59:50 lx120e dbus-daemon[981]: ** Message: entering main loop

What is Fprint and why is it getting reactivated?


It's the fingerprint reader driver.
Why it's being reactivated I don't know.
This page should help you figure out how to turn it off if you don't
need it: http://fedoraproject.org/wiki/Systemd


Well systemctl does NOT list Fprint.

I did find the following files:

/etc/dbus-1/system.d/net.reactivated.Fprint.conf
/usr/share/dbus-1/system-services/net.reactivated.Fprint.service

[root@lx120e ~]# cat /etc/dbus-1/system.d/net.reactivated.Fprint.conf
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

<!-- Only root can own the service -->
<policy user="root">
<allow own="net.reactivated.Fprint"/>
</policy>

<!-- Anyone can talk to the service -->
<policy context="default">
<allow send_destination="net.reactivated.Fprint"/>
<allow send_interface="net.reactivated.Fprint"/>
</policy>

</busconfig>
[root@lx120e ~]# cat
/usr/share/dbus-1/system-services/net.reactivated.Fprint.service

[D-BUS Service]
Name=net.reactivated.Fprint
Exec=/usr/libexec/fprintd
User=root

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?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

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 authentication - I found the program by simply typing it in the
search field of KDE application launcher. From a command prompt as root,
you can alternatively run system-config-authentication. There, in the
advanced tab you can check to see if fingerprint reader is turned on.


--
Claude Jones Brunswick, MD, USA
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org