Summary: | mail-client/evolution-3.18.3 asks for password every time | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | imese |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info evolution |
Description
imese
2016-01-21 17:20:50 UTC
It's not the case for me... Please provide "emerge --info evolution", also, try manually running "seahorse" and unlocking the keyrings also please try with 3.18.4 Created attachment 424265 [details]
emerge --info evolution
seahorse shows no local keyrings. Tried to emerge 3.18.4: root@go:~# emerge evolution ... configure: error: Package requirements (camel-1.2 >= 3.18.4 ... root@go:~# emerge -s camel [ Results for search key : camel ] Searching... * dev-haskell/cipher-camellia Latest version available: 0.0.2 Latest version installed: [ Not Installed ] Size of files: 7 KiB Homepage: https://github.com/vincenthz/hs-crypto-cipher Description: Camellia block cipher primitives License: BSD [ Applications found : 1 ] emerged 3.18.4. This however failed until I emerge evolution-data-server-3.18.4 which was not a requirement of evolution-3.18.4. Problem persists. Password required for every attempt to fetch mail. Maybe you are hitting https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-18&id=8e3a4841a39dc5022c832c5d80c2296315b9cbe0 ... but that bug should only appear when running gnupg1 and 2... and that is not possible on Gentoo I think it is something else: Feb 01 15:48:50 go gnome-keyring-daemon[551]: The Secret Service was already initialized Feb 01 15:48:50 go org.freedesktop.secrets[592]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Feb 01 15:50:26 go evolution.desktop[1590]: (evolution:1590): e-data-server-ui-WARNING **: credentials_prompter_store_credentials_cb: Failed to store source credentials: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached Feb 01 15:50:33 go evolution.desktop[1590]: (evolution:1590): e-data-server-ui-WARNING **: credentials_prompter_store_credentials_cb: Failed to store source credentials: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached Feb 01 15:50:57 go gnome-keyring-daemon[551]: The Secret Service was already initialized Feb 01 15:50:57 go org.freedesktop.secrets[592]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Feb 01 15:51:22 go evolution.desktop[1590]: (evolution:1590): e-data-server-ui-WARNING **: credentials_prompter_store_credentials_cb: Failed to store source credentials: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached Feb 01 15:51:58 go evolution.desktop[1590]: (evolution:1590): e-data-server-ui-WARNING **: credentials_prompter_store_credentials_cb: Failed to store source credentials: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached This kind of fits. Whenever checking or sending email there is a 1-2 minute delay before the password dialog. I opened seahorse on another gentoo machine. In the left panel there was a 'Passwords' category but not on my original machine. So the problem is probably not evolution at all but the keyring manager. What could this be? Thanks I know gnome-keyring had a race condition that could cause activation problems for 3.18.0... but that was fixed for 3.18.3, then, if you are running that 3.18.3 gnome-keyring version the problem should be other :/ What is the output of: $ ls -l /usr/bin/gnome-keyring-daemon -rwx--x--x 1 root root 944440 oct 21 13:24 /usr/bin/gnome-keyring-daemon ? It should be something like that, if it has a setuid bit this would be like bug 513870 root@go:/usr/bin# ls -l gnome-keyring-daemon -rwx--x--x 1 root root 1018296 Dec 3 10:20 gnome-keyring-daemon I still think it is gnome-keyring that is fubar. There is no password category in seahorse on this machine but is on the other. If there were some good docs for gkr maybe I could figure it out. Thanks There is a new 3.18.5.2 version. Also try with dbus-1.10.8-r1 with user-session USE flag *disabled* and after rebooting with it |