That's the good news.
The bad news is:
$ sudo dnf erase NetworkManager-wifi Dependencies resolved. =============================================================================== Package Arch Version Repository Size =============================================================================== Removing: NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21 @System 112 k kde-plasma-nm x86_64 0.9.3.5-3.fc21 @System 3.4 M kde-plasma-nm-openvpn x86_64 0.9.3.5-3.fc21 @System 418 k kde-plasma-nm-pptp x86_64 0.9.3.5-3.fc21 @System 154 k kde-plasma-nm-vpnc x86_64 0.9.3.5-3.fc21 @System 283 k
Transaction Summary =============================================================================== Remove 5 Packages
My desktop machine doesn't have any Wifi adapter. But I *do* use a VPN all the time.
This looks like a bad dependency, no?
It's not all bad. I at least got to remove some cruft:
$ sudo dnf erase NetworkManager-adsl NetworkManager-bluetooth Dependencies resolved. =============================================================================== Package Arch Version Repository Size =============================================================================== Removing: NetworkManager-adsl x86_64 1:0.9.10.0-14.git20140704.fc21 @System 27 k NetworkManager-bluetooth x86_64 1:0.9.10.0-14.git20140704.fc21 @System 92 k Transaction Summary =============================================================================== Remove 2 Packages
Garry T. Williams wrote:
The bad news is:
$ sudo dnf erase NetworkManager-wifi Dependencies resolved.
===============================================================================
Package Arch Version Repository Size
===============================================================================
Removing: NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21 @System 112 k
On the other hand, is there any other bad implications, other than a whopping 112k of wasted disk space?
-- Rex
On 12/16/2014 11:00 AM, Rex Dieter wrote:
Garry T. Williams wrote:
The bad news is:
$ sudo dnf erase NetworkManager-wifi Dependencies resolved.
===============================================================================
Package Arch Version Repository Size
===============================================================================
Removing: NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21 @System 112 k
On the other hand, is there any other bad implications, other than a whopping 112k of wasted disk space?
-- Rex
You might then also be able to remove wpa_supplicant:
Removing: wpa_supplicant x86_64 1:2.0-12.fc21 @fedora-21-everything-x86_64 3.1 M Removing for dependencies: NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21
@fedora-21-updates-x86_64 112 k kde-plasma-nm x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 3.3 M kde-plasma-nm-l2tp x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 187 k kde-plasma-nm-openconnect x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 180 k kde-plasma-nm-openswan x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 99 k kde-plasma-nm-openvpn x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 402 k kde-plasma-nm-pptp x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 150 k kde-plasma-nm-vpnc x86_64 0.9.3.4-16.fc21 @fedora-21-everything-x86_64 272 k
On 12-16-14 12:00:51 Rex Dieter wrote:
Garry T. Williams wrote:
Removing: NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21 @System 112 k
On the other hand, is there any other bad implications, other than a whopping 112k of wasted disk space?
Yeah, it's no big deal. I used to be irritated by NM running useless stuff, but it does seem much better behaved these days. So, no.
I do like to remove packages I don't have any use for, though.
Completely unrelated, I see that after a fresh install of the KDE spin that that silly finger print reader again spams my journal. So I will have to research how to turn it off again.
On 12/17/14 12:26, Garry T. Williams wrote:
Completely unrelated, I see that after a fresh install of the KDE spin that that silly finger print reader again spams my journal. So I will have to research how to turn it off again.
systemctl mask fprintd.service
On 12/16/2014 10:18 PM, Ed Greshko wrote:
On 12/17/14 12:26, Garry T. Williams wrote:
Completely unrelated, I see that after a fresh install of the KDE spin that that silly finger print reader again spams my journal. So I will have to research how to turn it off again.
systemctl mask fprintd.service
Or:
yum remove fprintd
On Wed, Dec 17, 2014 at 12:18 AM, Ed Greshko ed.greshko@greshko.com wrote:
On 12/17/14 12:26, Garry T. Williams wrote:
Completely unrelated, I see that after a fresh install of the KDE spin that that silly finger print reader again spams my journal. So I will have to research how to turn it off again.
systemctl mask fprintd.service
Yeah, that was what I first did:
dbus[518]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' dbus[518]: [system] Activation via systemd failed for unit 'fprintd.service': Unit fprintd.service is masked.
Then I just erased the package fprintd, but:
kcheckpass[10724]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory kcheckpass[10724]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
So there's something that still thinks that this authentication should still be run.
This has been broken like this for as long as fprintd has been included in Fedora.
Of course, this isn't in any way related to KDE. :-)
On 12/18/2014 08:00 AM, Garry Williams wrote:
On Wed, Dec 17, 2014 at 12:18 AM, Ed Greshko ed.greshko@greshko.com wrote:
On 12/17/14 12:26, Garry T. Williams wrote:
Completely unrelated, I see that after a fresh install of the KDE spin that that silly finger print reader again spams my journal. So I will have to research how to turn it off again.
systemctl mask fprintd.service
Yeah, that was what I first did:
dbus[518]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' dbus[518]: [system] Activation via systemd failed for unit 'fprintd.service': Unit fprintd.service is masked.
Then I just erased the package fprintd, but:
kcheckpass[10724]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory kcheckpass[10724]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
So there's something that still thinks that this authentication should still be run.
Try running:
authconfig --update
to update the config.
This has been broken like this for as long as fprintd has been included in Fedora.
Of course, this isn't in any way related to KDE. :-)
Indeed :)
On Thu, Dec 18, 2014 at 10:32 AM, Orion Poplawski orion@cora.nwra.com wrote:
On 12/18/2014 08:00 AM, Garry Williams wrote:
kcheckpass[10724]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory kcheckpass[10724]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
So there's something that still thinks that this authentication should still be run.
Try running:
authconfig --update
to update the config.
Well, I did something close to that:
sudo mv /etc/pam.d/system-auth /tmp sudo dnf reinstall pam
That did the trick, too.
I got there from here: https://bugzilla.redhat.com/show_bug.cgi?id=505266
Perhaps removing fprintd should trigger the call to authconfig(8)?
On 12/18/2014 11:57 AM, Garry Williams wrote:
On Thu, Dec 18, 2014 at 10:32 AM, Orion Poplawski orion@cora.nwra.com wrote:
On 12/18/2014 08:00 AM, Garry Williams wrote:
kcheckpass[10724]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory kcheckpass[10724]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
So there's something that still thinks that this authentication should still be run.
Try running:
authconfig --update
to update the config.
Well, I did something close to that:
sudo mv /etc/pam.d/system-auth /tmp sudo dnf reinstall pam
That did the trick, too.
I got there from here: https://bugzilla.redhat.com/show_bug.cgi?id=505266
Perhaps removing fprintd should trigger the call to authconfig(8)?
I don't think so. It could wipe out local modifications unexpectedly.
On 18 December 2014 at 18:57, Garry Williams gtwilliams@gmail.com wrote:
On Thu, Dec 18, 2014 at 10:32 AM, Orion Poplawski orion@cora.nwra.com wrote:
On 12/18/2014 08:00 AM, Garry Williams wrote:
kcheckpass[10724]: PAM unable to
dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory
kcheckpass[10724]: PAM adding faulty module:
/usr/lib64/security/pam_fprintd.so
So there's something that still thinks that this authentication should still be run.
Try running:
authconfig --update
to update the config.
Well, I did something close to that:
sudo mv /etc/pam.d/system-auth /tmp sudo dnf reinstall pam
That did the trick, too.
I got there from here: https://bugzilla.redhat.com/show_bug.cgi?id=505266
Perhaps removing fprintd should trigger the call to authconfig(8)?
after removing all fprint related rpms I then edit system-auth by adding
"-" which tell pam to ignore the missing module.
-auth sufficient pam_fprintd.so
...dex
-
dexter -
Ed Greshko -
Garry Williams -
Orion Poplawski -
Rex Dieter