{"id":2731,"date":"2013-01-17T14:49:49","date_gmt":"2013-01-17T07:49:49","guid":{"rendered":"http:\/\/www.jfdesignnet.com\/?p=2731"},"modified":"2013-01-17T14:49:49","modified_gmt":"2013-01-17T07:49:49","slug":"gnome-keyring-module-not-loaded","status":"publish","type":"post","link":"https:\/\/www.jfdesignnet.com\/?p=2731","title":{"rendered":"gnome-keyring module not loaded on KDE"},"content":{"rendered":"

I usually doing repo sync cm gerrit on my server (which on debian squeeze) and build there via ssh, and never had a single problem whatsoever. Today, I have to move to other house and sleep there for several days and i want to build grouper branch from cm-10.1-MR1 on my notebook (no laugh please) since i’m not to satisfied with my last build. Further, i also want to try including this patch<\/a> internally to increase the jvm performance on my nexus 7. Unquestionable, have to do repo sync again on my notebook, quickly init the environment and do a repo sync … but everytime i begin to sync, there are some nagging error message :<\/p>\n

{code}WARNING: gnome-keyring:: couldn’t connect to: \/tmp\/keyring pkcs11: No such file or directory{\/code}<\/p>\n

Cancel the progress and investigate the problem, … checking my gpg key using seahorse and kgpg, it returns valid and i can do sync to my local svn repo and even to launchpad repo … hmmm what’s wrong with this gnome-keyring key? After a long long time narrowing the problem, suddenly i check the gnome-keyring-pkcs11 module wheather is loaded on memory or not using ps aux. Dang !!! yes !!! it isn’t loaded on memory for some reason. In short, it turns out the gnome-keyring-pkcs11.so module isn’t loaded because I’m on KDE desktop, and that’s why it doesn’t throws errors on my debian server.<\/p>\n

For you experience the same problem with me, here is the fix :<\/p>\n

Edit the \/etc\/xdg\/autostart\/gnome-keyring-pkcs11.desktop :<\/p>\n

[Desktop Entry]<\/strong>
\n Type=Application<\/strong>
\n Name=Certificate and Key Storage<\/strong>
\n Comment=GNOME Keyring: PKCS#11 Component<\/strong>
\n Exec=\/usr\/bin\/gnome-keyring-daemon –start –components=pkcs11<\/strong>
\n OnlyShowIn=GNOME;Unity;MATE;KDE<\/span><\/strong>
\n X-GNOME-Autostart-Phase=Initialization<\/strong>
\n X-GNOME-AutoRestart=false<\/strong>
\n X-GNOME-Autostart-Notify=true<\/strong>
\n X-GNOME-Bugzilla-Bugzilla=GNOME<\/strong>
\n X-GNOME-Bugzilla-Product=gnome-keyring<\/strong>
\n X-GNOME-Bugzilla-Component=general<\/strong>
\n X-GNOME-Bugzilla-Version=3.6.1<\/strong>
\n NoDisplay=true<\/strong>
\n X-Ubuntu-Gettext-Domain=gnome-keyring<\/strong><\/p>\n

You may also add LXDE on the list if you’re using one, then save it and reboot. After reboot, the gnome-keyring-pkcs11 module was perfectly loaded without problem :<\/p>\n

{code}(jfdesign@jfklixs-ubuntu64:~)$ ps aux | grep gnome-keyring
\njfdesign\u00a0 1967\u00a0 0.0\u00a0 0.1 378736\u00a0 4240 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Sl\u00a0\u00a0 09:43\u00a0\u00a0 0:00 \/usr\/bin\/gnome-keyring-daemon –daemonize –login
\njfdesign\u00a0 2789\u00a0 0.0\u00a0 0.0\u00a0 56356\u00a0 2216 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 S\u00a0\u00a0\u00a0 09:44\u00a0\u00a0 0:00 \/usr\/bin\/gnome-keyring-daemon –start –foreground –components=secrets
\njfdesign\u00a0 6252\u00a0 0.0\u00a0 0.0\u00a0 13584\u00a0\u00a0 940 pts\/2\u00a0\u00a0\u00a0 S+\u00a0\u00a0 11:12\u00a0\u00a0 0:00 grep –color=auto gnome-keyring
\n(jfdesign@jfklixs-ubuntu64:~)${\/code}<\/p>\n

Now i can repo sync without errors.<\/p>\n

\"repo-sync-cm\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I usually doing repo sync cm gerrit on my server (which on debian squeeze) and build there via ssh, and never had a single problem whatsoever. Today, I have to move to other house and sleep there for several days and i want to build grouper branch from cm-10.1-MR1 on my notebook (no laugh please) […]<\/p>\n","protected":false},"author":1,"featured_media":2758,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,9,14],"tags":[101,196],"_links":{"self":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/2731"}],"collection":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2731"}],"version-history":[{"count":0,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/2731\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/media\/2758"}],"wp:attachment":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2731"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2731"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2731"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}