dx-packages team mailing list archive

[Alex Botev <botevmg@xxxxxxxxx>]

So you just add it to the end of the line of an entry, of course monitor
the /var/log/auth.log, as this means you are passing it as an argument,
which might not be valid for all packages(its a common practice to be
tough, but who knows). For instance my /etc/pam.d/common-auth looks like
this:

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth	[success=2 default=ignore]	pam_fprintd.so max_tries=1 timeout=10  debug
auth	[success=1 default=ignore]	pam_unix.so nullok_secure try_first_pass debug
# here's the fallback if no module succeeds
auth	requisite			pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth	required			pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth	optional			pam_cap.so 
# end of pam-auth-update config

If you want full debug some packages (including fprintd) would require
to be compiled from source with a debug flag on. Even without that,
enabling debug can produce some usefull stuff in the auth.log

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1311316

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions