modifying PAM configuration could break gksu
Nominated for Karmic by jedioetzi
Binary package hint: gksu
If you modify PAM configuration to act differently, gksu could become unusable.
For example, see https:/
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
With this configuration, Login in console, GDM and su will work perfectly and ask you either for your password or your fingerprint.
Unfortunatly, gksu will become "invisible". In fact, the sentence "enter your password or swipe your finger" will appear in the console from which you are launching gksu. As, most of the time, you are not launching gksu from a console but from an icon, you will see nothing and your application will not start. Anyway, it is still working because if you know it and swipe your finger, your application will eventually appear. So gksu is still listenning. It is just "invisible".
|Changed in gksu:|
|importance:||Undecided → Medium|
|Changed in gksu (Ubuntu):|
|status:||Confirmed → Triaged|