From owner-freebsd-gnome@FreeBSD.ORG Mon Apr 7 10:00:22 2008 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1120E106566B for ; Mon, 7 Apr 2008 10:00:22 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from qsrv02ps.mx.bigpond.com (qsrv02ps.mx.bigpond.com [144.140.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9B86F8FC1F for ; Mon, 7 Apr 2008 10:00:21 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntotgx03p.mx.bigpond.com ([124.188.162.219]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20080407063707.FGZS649.nskntmtas02p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com> for ; Mon, 7 Apr 2008 06:37:07 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nskntotgx03p.mx.bigpond.com with ESMTP id <20080407063707.MLBC9173.nskntotgx03p.mx.bigpond.com@areilly.bpa.nu> for ; Mon, 7 Apr 2008 06:37:07 +0000 Received: (qmail 98891 invoked by uid 501); 7 Apr 2008 06:36:51 -0000 Date: Mon, 7 Apr 2008 16:36:51 +1000 From: Andrew Reilly To: Joe Marcus Clarke Message-ID: <20080407063651.GB97699@duncan.reilly.home> References: <87d4p3xome.fsf@chateau.d.lf> <1207495285.21780.1.camel@shumai.marcuscom.com> <87y77qg9zd.fsf@chateau.d.lf> <1207504273.22879.4.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1207504273.22879.4.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.3i Cc: gnome@freebsd.org, FreeBSD Ports Mailing List , Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksg==?= , Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksg==?= Subject: Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password. X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2008 10:00:22 -0000 On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: > On Sun, 2008-04-06 at 23:07 +0530, Ashish Shukla आशीष शुक्ल wrote: > > >>>>> Joe Marcus Clarke writes: > > Joe> On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: > > >> Hi, > > >> > > >> Whenever I try to unlock my screen, locked using gnome-screensaver, it > > >> doesn't accept my password, rejects with "Incorrect password". I'm > > >> running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? > > >> And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. > > >> > > >> During password verification, there is some non-uniform delay > > >> (sometime more, sometimes less) . > > >> > > >> Is there anyone else experiencing this issue, hmm...? > > > > Joe> This is typically the case when one builds gnome-screensaver with PAM > > Joe> support, but they are currently using a PAM module which requires the > > Joe> executable be setuid root (e.g. pam_unix). The only workaround is to > > Joe> rebuild gnome-screensaver without PAM support, or use a different PAM > > Joe> module which does not require root privileges. > > > > I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but > > also thats of no use. Any ideas, why is that not working inspite of > > /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? > > PAM and gnome-screensaver do not work together if you are using > pam_unix. Rebuild gnome-screensaver without PAM support, and it will > instead read /etc/master.passwd directly to authenticate the user. That > will work. So, is there a scenario where PAM and gnome-screensaver *do* work? If not, then why is PAM an option? I admit that I don't fully understand PAM, but have noticed that there's a whole bunch of PAM stuff in recent FreeBSD configurations, even at the non-ports level, so I have it in gnome-screensaver, too. I thought that was just how it was supposed to be done. Therefore, whenever I mistakenly allow the screen to be locked, I have to log-in from another machine and kill the screen saver... My FreeBSD system is physically secure, so I don't have it lock automatically when the screen saver comes on, so this only happens when I mis-mouse in the GNOME System menu. So it hasn't bothered me enough to really try debugging it, up to now. (Although I did try to remove the "lock screen" menu item, but the menu-editing facility did not facilitate that...) Cheers, -- Andrew