From owner-freebsd-gnome@FreeBSD.ORG Sat Aug 22 05:51:27 2009 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 C880B106568C; Sat, 22 Aug 2009 05:51:27 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail4.es.net [IPv6:2001:400:6000:6::2]) by mx1.freebsd.org (Postfix) with ESMTP id 69D8D8FC08; Sat, 22 Aug 2009 05:51:27 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n7M5pMBX031308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Aug 2009 22:51:24 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id AE6671CC09; Fri, 21 Aug 2009 22:51:21 -0700 (PDT) To: Joe Marcus Clarke In-reply-to: Your message of "Fri, 21 Aug 2009 20:15:59 EDT." <1250900159.99362.2.camel@shumai.marcuscom.com> Date: Fri, 21 Aug 2009 22:51:21 -0700 From: "Kevin Oberman" Message-Id: <20090822055121.AE6671CC09@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-08-21_10:2009-08-11, 2009-08-21, 2009-08-21 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908210118 Cc: gnome@FreeBSD.org Subject: Re: screensaver still broken... 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: Sat, 22 Aug 2009 05:51:27 -0000 > From: Joe Marcus Clarke > Date: Fri, 21 Aug 2009 20:15:59 -0400 > > On Fri, 2009-08-21 at 15:25 -0700, Kevin Oberman wrote: > > > Date: Fri, 21 Aug 2009 16:43:45 -0400 > > > From: Joe Marcus Clarke > > > Sender: owner-freebsd-gnome@freebsd.org > > > > > > Mike Harding wrote: > > > > I still have issues where a screen lock won't let me type in my > > > > password, have to kill it from a console. Also, the LCD backlight for > > > > my desktop machine doesn't turn off... something in GNOME turns off > > > > the power saving in X. > > > > > > > > Does these lines in ~/.xsession-errors about org.gnome.ScreenSaver > > > > mean anything? > > > > > > No. Everyone sees them. I cannot reproduce the gnome-screensaver > > > problems on any of my machines. And I don't have a machine with fully > > > working power management to test backlight stuff. I don't have any > > > suggestions, either because I have not seen these problems. Maybe some > > > of the upstream GNOME people have some ideas of things to try. > > > > > > Joe > > > > > > > > > > > ... > > > > GNOME_KEYRING_SOCKET=/var/tmp/keyring-nSCzz5/socket > > > > SSH_AUTH_SOCK=/var/tmp/keyring-nSCzz5/socket.ssh > > > > Window manager warning: Failed to read saved session file /home/mvh/.config/metacity/sessions/10de59714e160f9b21125086698531955500000022920015.ms: Failed to open file '/home/mvh/.config/metacity/sessions/10de59714e160f9b21125086698531955500000022920015.ms': No such file or directory > > > > ** (gnome-volume-control-applet:2341): DEBUG: Disabling debugging > > > > > > > > ** (gnome-power-manager:2339): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name > > > > ** (gnome-power-manager:2339): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running? > > > > > > > > ** (gnome-power-manager:2339): WARNING **: This machine is not identified as a laptop.system.formfactor is desktop. > > > > > > > > ** (gnome-power-manager:2339): WARNING **: This machine is not identified as a laptop.system.formfactor is desktop. > > > > ** (gnome-power-manager:2339): DEBUG: This machine is not identified as a laptop.system.formfactor is desktop. > > > > ** (gnome-power-manager:2339): DEBUG: We are not a laptop, so not even trying > > > > Unable to open desktop file /usr/local/share/gnome/applications/gnome-terminal.desktop for panel launcher: No such file or directory > > > > system-config-printer-applet: failed to start NewPrinterNotification service > > > > Initializing nautilus-open-terminal extension > > > > > > > > ... > > > > _______________________________________________ > > > > freebsd-gnome@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > > > > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" > > > > > > > > I've grabbed a ktrace of it and I see a bunch of read errors. That would > > make some sense as it looks like the screensaver get to the point of > > accepting input when it dies. > > One thing that is absolutely required is that /usr/local/bin/pam_helper > exists, and setuid root. If you run this command manually as: > > /usr/local/bin/pam_helper gnome-screensaver USERNAME > > Where USERNAME is your username, then type in your password, and hit > Control+D, you should get back an exit status of 0 (i.e. $? = 0 or > $status = 0). If this tool isn't working, then unlocking will not be > possible. Well, that explains one of the three systems...the laptop that never seemed to work. pam_helper was not installed. That is now fixed and that system (my laptop) works, for now. It was present on both other systems, so it was no just that, but I won't have my hands on either of those systems until Monday. My ktrace was on the laptop. I'll try grabbing another Monday on a system that has shown the problem even though they have a working pam_helper. Thanks, Joe! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751