Description of problem:

While starting gdm usually the gnome-keyring-daemon asks for the masterpassword and stays on as long as the user needs to enter the password.

With Fedora 23 this no longer works out, as the process opens as usual, but gets stopped/fails/crashes after a few secs.

No chance to enter the password.

Infos:

System was upgraded by yum from F21 to F23. Besides the obviosly problems like :
- huge desktopicons, noone seems to care for ( not fedora nor gnome devs ),
- installing kernels without modules ( args! ) and
- deactivated most usefull gnome-shell-extensions, 

this seems to be the only major bug i encountered so far after upgrading to F23.

Version-Release number of selected component (if applicable):

gnome-keyring    3.18.3-1
libgnome-keyring 3.12.0-5



How reproducible:

always

Actual results:

Keyring-daemon exists without getting the password entered


Expected results:

has to be open until the password gets entered.

Additional info:

WORKAROUND FOR NOW:

For users of ssh sessions, they can rebuild the entire process by adding this to the useraccounts .bashrc : 

++++++++++++++++++++++++++++++++++++++++++++++++++++
# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
	. /etc/bashrc
fi

# User specific aliases and functions


RC=`pidof gnome-keyring-daemon`
if [ "$RC" == "" ]; then 
	export `gnome-keyring-daemon`
else 
 	export SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
fi
++++++++++++++++++++++++++++++++++++++++++++++++++++

where 1000 is the accounts userid . You get the entire export string "SSH_AUTH_SOCK=/run/user/1000/keyring/ssh" if you start the gnome-keyring-daemon by hand as output, just copy & paste it there.

You just have to ensure, that there is only one gnome-keyring-daemon process with your users id, which in desktop systems is usually the case. 

obviosly you can rebuild this process in /etc/bashrc for all users, just have to watch for the correct uid of the processes and filepathes.