[From nobody Tue Apr 7 08:03:55 2026 Received: (at submit) by bugs.debian.org; 30 Mar 2012 22:55:17 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.1-bugs.debian.org_2005_01_02 (2010-03-16) on busoni.debian.org X-Spam-Level: X-Spam-Status: No, score=-6.1 required=4.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FOURLA,FREEMAIL_FROM,HAS_PACKAGE,IMPRONONCABLE_1, IMPRONONCABLE_2, MONEY, MURPHY_WRONG_WORD2, RCVD_IN_DNSWL_LOW, SPF_PASS, STOCKLIKE autolearn=ham version=3.3.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 22; hammy, 150; neutral, 186; spammy, 1. spammytokens:1.000-4--metho hammytokens:0.000-+--sk:gnomes, 0.000-+--sk:gnome-s, 0.000-+--PREEMPT, 0.000-+--wheezy, 0.000-+--sk:gnomep Return-path: <alxgomz@gmail.com> Received: from mail-wg0-f42.google.com ([74.125.82.42]) by busoni.debian.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <alxgomz@gmail.com>) id 1SDkiz-00050c-4a for submit@bugs.debian.org; Fri, 30 Mar 2012 22:55:17 +0000 Received: by wgbds11 with SMTP id ds11so1077813wgb.5 for <submit@bugs.debian.org>; Fri, 30 Mar 2012 15:55:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:content-transfer-encoding:from:to:subject :message-id:date; bh=HqJ49g1tPEhK46dJ1IofTTJWxhkeSpCmc/u09korWhg=; b=uTZwDq/onsUWFmvBcbCf3hbQLtbHYsS5U6n43xvHdMfP7LXH0K4Rz7k0EougX8D6pM 7iOzAi9OOyeZOWWrMbBUghhG/VOedSX6bD54YubDJa7zvYMCbpw8X46NaU+5pzN06g8P 1Qk9r0FeMq+S/5yES8jE0qJpODUT+BhpbG2sY1fzQpXJWUys6aAHYjE2e1TbJZ+mDbyq JHEHNmfF8d9uZv+PQQelbFMw3CTlM11zGf+MeZD+enog2TvA41cUcIG3mLcYJauHBdZA HAPhTgkBujUPXmpBdB4FRvZlaxCMPS/iO6MTBhGjCU4JOSx9Ef21NDawwRQJFHsV0MIM nwvA== Received: by 10.180.104.137 with SMTP id ge9mr661900wib.20.1333148110390; Fri, 30 Mar 2012 15:55:10 -0700 (PDT) Received: from elronde.middle.earth (143.161.200.77.rev.sfr.net. [77.200.161.143]) by mx.google.com with ESMTPS id bx13sm10231725wib.10.2012.03.30.15.55.08 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 30 Mar 2012 15:55:09 -0700 (PDT) Received: from root by elronde.middle.earth with local (Exim 4.77) (envelope-from <alxgomz@gmail.com>) id 1SDkio-0002no-Jp; Sat, 31 Mar 2012 00:55:06 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexandre Chapellon <alxgomz@gmail.com> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: gnome-screensaver: can't unlock screen because of invalid password (while valid) Message-Id: <E1SDkio-0002no-Jp@elronde.middle.earth> Date: Sat, 31 Mar 2012 00:55:06 +0200 Delivered-To: submit@bugs.debian.org Package: gnome-screensaver Version: 3.2.2-1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** * What led up to the situation? Install gnome-shell on wheezy * What exactly did you do (or not do) that was effective (or ineffective)? removed in pam module for gnome-screensaver: include common-auth and replaced it with: auth sufficient pam-unix.so * What was the outcome of this action? works as expected: can't unlock with invalid password and unlock correctly with valid passwd. Maybe this action have side effects I don't imagine. However, I first tried to use the required metho instead of sufficient and it didn't helped. Sufficient works but auth.log still contains auth failure message for the gnome-screensaver service: Mar 31 00:29:17 elronde unix_chkpwd[10017]: check pass; user unknown Mar 31 00:29:22 elronde unix_chkpwd[10019]: check pass; user unknown Mar 31 00:29:22 elronde unix_chkpwd[10019]: password check failed for user (alxgomz) Mar 31 00:29:22 elronde gnome-screensaver-dialog: pam_unix(gnome- screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=alxgomz Mar 31 00:29:22 elronde gnome-screensaver-dialog: gkr-pam: unlocked login keyring Mar 31 00:29:22 elronde unix_chkpwd[10020]: could not obtain user info (alxgomz) * What outcome did you expect instead? I expected the required or requisite method to work for gnome-screensaver module (and so do the include common-auth), or and the sufficient method not to log auth failures. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-screensaver depends on: ii dbus-x11 1.4.18-1 ii dpkg 1.16.2 ii gnome-icon-theme 3.2.1.2-1 ii gnome-session-bin 3.2.1-1 ii gsettings-desktop-schemas 3.2.0-2 ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libdbus-1-3 1.4.18-1 ii libdbus-glib-1-2 0.98-1 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-0 2.30.2-6 ii libgnome-desktop-3-2 3.2.1-3 ii libgnomekbd7 3.2.0-1 ii libgtk-3-0 3.2.3-1 ii libpam0g 1.1.3-7 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxklavier16 5.2.1-1 ii libxxf86vm1 1:1.1.1-2 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.2.1-2 ii libpam-gnome-keyring 3.2.2-2 gnome-screensaver suggests no packages. -- Configuration Files: /etc/pam.d/gnome-screensaver changed: @include common-auth auth optional pam_gnome_keyring.so -- no debconf information ]