openjdk team mailing list archive

[James Page <737603@xxxxxxxxxxxxxxxxxx>]

** Changed in: libjna-java (Ubuntu)
       Status: New => Triaged

** Changed in: libjna-java (Ubuntu)
   Importance: Undecided => High

** Changed in: libjna-java (Ubuntu)
     Assignee: (unassigned) => James Page (james-page)

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in Ubuntu.
https://bugs.launchpad.net/bugs/737603

Title:
  JNI unable to find libpam.so

Status in “libjna-java” package in Ubuntu:
  Triaged
Status in “openjdk-6” package in Ubuntu:
  Triaged

Bug description:
  I'm currently packaging Jenkins for Ubuntu; this application has
  native authentication integration through the use of PAM. This was
  working fine i.e. the java native interface dispatcher was able to
  find libpam.so in /lib and all was happy.

  I've just updated my test system and native authentication no longer
  works; the JNI dispatcher can't find the library.  I have done a bit
  of digging and it looks like libpam.so.* is installed to /lib/i386
  -linux-gnu instead of /lib (as on Maverick and possibly earlier Natty
  releases?).  This directory is not on the java.library.path by default
  which I suspect may be the issue (see below for default java library
  path):

  /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/jni:/lib:/usr/lib

  So I'm not sure whether this is a bug in pam or openjdk but I guess it
  could be either.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libpam0g 1.1.2-2ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-7.35-generic-pae 2.6.38
  Uname: Linux 2.6.38-7-generic-pae i686
  Architecture: i386
  Date: Fri Mar 18 14:54:45 2011
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Alpha i386 (20110301.4)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)