Package: gnome-keyring Version: 3.4.1-5 Severity: normal Dear Maintainer,
I was uncertain whether to file this as an evolution issue or a gnome-keyring one. Googling the problem suggests the latter, or that it may be more of a system level thing involving e.g the order of startup of dBus and the keyring. Unfortunately it's hard to find specific mentions of evolution-over-ssh problems amongst all the other reports of more conventional usage (which has always worked just fine for me). The issue appeared on transitioning my LAN machines from Squeeze to Wheezy. Anyway, I have a machine called basecamp where I run evolution and pull mail from various POP3 accounts. If I login to a (classic) gnome session at the machine, evolution works as expected, apparently storing passwords... well actually I don't know where it stores them (I assume the gnome keyring). If I VNC to a tightvncserver hosted gnome-session-fallback on basecamp (using the same ID, while not logged in on the console), that works fine too. There is an initial password prompt to unlock the keyring, (expected, as the gnome-session is not spawned from gdm3) and then evolution seems to be able to find all the passwords it needs. (Actually, there is a bit of a story with this one with needing to enable GLX within VNC as evolution has moved to a clutter OpenGL backend on Wheezy, but that's nothing to do with this I think). However, if (from another machine on the LAN) I ssh -X to basecamp and run evolution, then I am prompted for passwords for the various IMAP and POP servers I access from evolution (apart from that, it works fine). Until recently, when all my LAN's machines were Squeeze, all the above ways of running evolution worked fine. It's only since they were upgraded to Wheezy that the evolution over ssh+X11 forwarding has developed this password prompting behaviour. Here's the output from the point at which I start evolution in the ssh session, to the point just after it's prompted me to supply the first password. ----- timday@basecamp:~$ evolution & [1] 8331 timday@basecamp:~$ ** (evolution:8331): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-HL0yCubDyW: Connection refused (evolution:8331): evolution-network-manager-WARNING **: network_manager_query_state: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.580" (uid=1001 pid=8331 comm="evolution ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=3427 comm="/usr/sbin/NetworkManager ") (evolution:8331): filter-CRITICAL **: e_filter_option_add: assertion `find_option (option, value) == NULL' failed ...<above line repeated a dozen times; this is normal for evolution run anyhow>... (evolution:8331): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: Error communicating with gnome-keyring-daemon) (evolution:8331): e-data-server-ui-WARNING **: Unable to create password in keyring (Keyring reports: Error communicating with gnome-keyring-daemon) ----- To be honest, I'm not sure how this managed to work previously under Squeeze, or even which machine it is/should be trying to access a keyring on! But certainly the previously nice behaviour has regressed with the move to Wheezy. (Hmmm I'm half wondering now if the previous behaviour of Squeeze's evolution was just to cache passwords in home directory files somewhere - which would have just worked for any invokation of evolution on that machine - and it's this whole keyring thing is new. I seem to remember the first runs of the updated evolution under Wheezy prompting for passwords, which might have been it populating the keyring). -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-keyring depends on: ii dbus-x11 1.6.8-1 ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii gcr 3.4.1-3 ii libc6 2.13-38 ii libcap-ng0 0.6.6-2 ii libcap2-bin 1:2.22-1.2 ii libdbus-1-3 1.6.8-1 ii libgck-1-0 3.4.1-3 ii libgcr-3-1 3.4.1-3 ii libgcrypt11 1.5.0-5 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk-3-0 3.4.2-6 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.4.1-5 gnome-keyring suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
