Your message dated Mon, 02 Nov 2009 12:21:42 +0100
with message-id <1257160902.23221.441.ca...@shizuru>
and subject line Re: Bug#553312: gnome-keyring breaks svn commit
has caused the Debian Bug report #553312,
regarding gnome-keyring breaks svn commit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
553312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553312
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 2.28.1-1
Severity: critical
Justification: breaks unrelated software

so now that I have gnome-keyring auto started it seems that it
*really* hoses svn.

        $ svn commit -m"some commit msg"
        Password for 'login' GNOME keyring:<ENTER>
        svn: Commit failed (details follow):
        svn: GNOME Keyring is locked and we are non-interactive
        $

What the f*** is going on???

That is a svn server which I access via the
        svn://[email protected]/...
method.

Why on earth does gnome-keyring play around here????


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-rc5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-keyring depends on:
ii  dbus-x11                      1.2.16-2   simple interprocess messaging syst
ii  gconf2                        2.28.0-1   GNOME configuration database syste
ii  libc6                         2.10.1-3   GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.16-2   simple interprocess messaging syst
ii  libgconf2-4                   2.28.0-1   GNOME configuration database syste
ii  libgcr0                       2.28.1-1   Library for Crypto UI related task
ii  libgcrypt11                   1.4.4-4    LGPL Crypto library - runtime libr
ii  libglib2.0-0                  2.22.2-2   The GLib library of C routines
ii  libgp11-0                     2.28.1-1   Glib wrapper library for PKCS#11 -
ii  libgtk2.0-0                   2.18.3-1   The GTK+ graphical user interface 
ii  libpango1.0-0                 1.26.0-1   Layout and rendering of internatio
ii  libtasn1-3                    2.3-1      Manage ASN.1 structures (runtime)

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring          2.28.1-1   PAM module to unlock the GNOME key

gnome-keyring suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Le samedi 31 octobre 2009 à 04:53 +0100, Norbert Preining a écrit : 
> Some explanation: I switched to fingerprint authentication for normal
> user, and it seems that using that does not unlock the login
> keyring for gnome-keyring.
> 
> As soon as I disable fingerprint login (changing /etc/pam.d/gdm to its 
> previous state it works.
> 
> The point is that there is NO way gnome-keyring should interfere with
> subversion, and I don't see why it is doing that.

The keyring daemon serves as a SSH agent by default. See README.Debian
for how to disable it.

Cheers, 
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée


--- End Message ---

Reply via email to