[Solved³] Gnome Keyring - Do I need it?

Sector11 · 2012-05-11 04:08:32

When I start a conky I get:

  01:01:32 ~
         $ WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-ExatjX/pkcs11: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3800001)
Conky: drawing to double buffer
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    16    0    16    0     0     11      0 --:--:--  0:00:01 --:--:--    50

Do I really need this gnome-keyring? I don't recall having it before.

Does anyone know why it is interfering with conky like this?

Last edited by Sector11 (2012-10-16 02:53:53)

falldown · 2012-05-11 14:57:26

S11
I am looking for an answer to this as well.
I get the same error from conky... although it doesn't seem to hurt anything other then the start time of conky.

Last edited by falldown (2012-05-11 15:29:02)

falldown · 2012-05-11 15:28:48

S11
It seems that it is a bug in Wheezy..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011

Sector11 · 2012-05-11 15:35:00

I don't know what it does and don't recall ever having it before.

According to this:
https://live.gnome.org/GnomeKeyring

I see no reason for me to have it. I have no 'secret storage' or ssh stuff.

I wonder if it can delete it safely ... and what other programs are installed that can go with it.

I have a simple home computer. No state secrets, nothing I don't want my wife to see. and no need to encrypt anything - never have.

Any help out there?

Last edited by Sector11 (2012-05-11 15:37:54)

machinebacon · 2012-05-11 15:38:27

S11:

apt-cache rdepends gnome-keyring 
gnome-keyring
Reverse Depends:
  virt-manager
  ubuntu-sso-client
  sugar-emulator-0.90
  sucrose-0.90
  seahorse
  screenlets
  osc
  mysql-workbench
  gnome-core
  libgnome-keyring0
  libgnome-keyring0
  gvfs-backends
  gtkvncviewer
  gnome-session-fallback
  gnome-session
  python-gnomekeyring
  libpam-gnome-keyring
  gksu
  gajim

Sector11 · 2012-05-11 16:19:51

falldown wrote:

S11
It seems that it is a bug in Wheezy..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011

OK and I did:

  13:06:44 ~
         $ ps aux | grep keyring
sector11 18892  0.0  0.0   7800   852 pts/0    S+   13:06   0:00 grep keyring

  13:06:46 ~
         $

... which means nothing to me. (noob)

I see near the bottom someone commented out:

module: gnome-keyring-pkcs11.so

... tried that, started a conky ... same problem.
maybe a reboot needed/or logout... but I un-commented it just to be safe.

machinebacon wrote:

S11:

apt-cache rdepends gnome-keyring 
gnome-keyring
Reverse Depends:
  virt-manager
  ubuntu-sso-client
  sugar-emulator-0.90
{snip}
  libpam-gnome-keyring
  gksu
  gajim

I really do need to learn more about apt.

Thanks MB, but I'm left with the same problem. Can it be deleted safely?

* https://live.gnome.org/GnomeKeyring
* http://developer.gnome.org/gnome-keyring/3.2/

Do I really need it on a home computer that has no state secrets, no personal secrets and no encryption?

Which brings up another though - for another thread if I can't find an answer.

Last edited by Sector11 (2012-05-11 16:20:15)

ivanovnegro · 2012-05-11 21:51:21

I removed it because it was bothering me and also deleted it from my home folder, look here:

http://crunchbanglinux.org/forums/topic … se-solved/

and here:

http://crunchbanglinux.org/forums/post/194552/#p194552

Milozzy · 2012-05-11 21:54:52

ivanovnegro wrote:

I removed it because it was bothering me and also deleted it from my home folder, look here:
http://crunchbanglinux.org/forums/topic … se-solved/
and here:
http://crunchbanglinux.org/forums/post/194552/#p194552

But this way you have to type your WPA/WEP key every time you connect, right?

ivanovnegro · 2012-05-11 22:16:15

^ Nope, not here. Ok, I do not use NM.

Sector11 · 2012-05-11 23:12:07

ivanovnegro wrote:

I removed it because it was bothering me and also deleted it from my home folder, look here:
http://crunchbanglinux.org/forums/topic … se-solved/
and here:
http://crunchbanglinux.org/forums/post/194552/#p194552

Super - colour that sucker GONE!!!!!

Hava java on me -

Good for one #! Coffee

Sector11 · 2012-05-11 23:49:47

ivanovnegro wrote:

^ Nope, not here. Ok, I do not use NM.

Me neither.

ivanovnegro · 2012-05-11 23:50:38

@Coffee 11: Oh, my second coffee from @S11. I am honored. big_smile
I think, now I am the record champion.

Edit: Help S11 and win coffees. big_smile

Last edited by ivanovnegro (2012-05-11 23:52:49)

Sector11 · 2012-05-11 23:55:58

ivanovnegro wrote:

@Coffee 11: Oh, my second coffee from @S11. I am honored.
I think, now I am the record champion.
Edit: Help S11 and win coffees.

Hahahahahahahahahah big_smile

And don't forget "The sound of Coffee!" a lot shorter than "The Sound of Music!"

Milozzy · 2012-05-12 08:14:52

Oh I understand now wink
Without NM, gnome-keyring is pretty much useless.
On one of my machine I use plain wpa_supplicant (+wpa_gui in certain situation) and I got rid of gnome-keyring too.

Sector11 · 2012-05-13 14:13:40

This is annoying ah all get out....

I do not have Network Manager - I dump 'gnome-keyring' and now I get:

  11:02:28 ~
         $ conky
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: forked to background, pid is 16377

What is going on? Conky never had these problems before.
What is causing this?
What 'shared object file'

I am not on a private network and conky shouldn't be concerned with a shared object file.

Does anyone have any idea what else I can get rid of?

machinebacon · 2012-05-13 14:16:46

^ Maybe conky uses the keyring for something like CPU% or whatnot, so that it doesn't need to be root? No idea!

Unia · 2012-05-13 14:33:12

Maybe try with another config file? That way you can determine whether it's conky in general or one of your configs

Sector11 · 2012-05-13 15:00:49

I have been running these configs for a LONG time, along with a few thousand test conkies. The ones that start with "test-xxx.conky" are now at /home/sector11/conky/test232.conky. The number of sub-directories in ~/conky = 106 the total number of conkys in ~/conky = 512 I'd estimate more than a couple of thousand conkys here with another 47 directories directly off ~/ involving conky. It's what I do. In any other aspect of Linux I'm a noob.

Trust me, nothing 'root' is involved. This is new, unexpected and annoying to say the least. sad

I just started 'MY' 10 conkys in a terminal - and at the end I added the #! default conky:

different directory ~/Conky:

  11:36:02 ~
         $ conky -c ~/Conky/S11_Cal_br.conky &
[1] 21951

  11:36:05 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - override
Conky: drawing to created window (0x1200001)
Conky: drawing to double buffer


  11:36:09 ~
         $ conky -c ~/Conky/VO_Radiotray.conky &
[2] 21970

  11:36:30 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x1c00001)
Conky: drawing to double buffer


  11:36:43 ~
         $ conky -c ~/Conky/S11_UT2.conky &
[3] 21984

  11:36:51 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - override
Conky: drawing to created window (0x1e00001)
Conky: drawing to double buffer


  11:37:03 ~
         $ conky -c ~/Conky/S11_v9_R.conky &
[4] 22017

  11:37:08 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - override
Conky: drawing to created window (0x2000001)
Conky: drawing to double buffer
gathering data with curl
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--: 31 67927   31 21308    0     0  20566      0  0:00:03  0:00:01  0:00:100 67927  100 67927    0     0  52625      0  0:00:01  0:00:01 --:--:-- 73914
not checking for alerts
processing complete


  11:37:23 ~
         $ (sleep 1s && wmctrl -s 2 && conky -c ~/Conky/S11_Rem_Cal.conky) &
[5] 22052

  11:37:29 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x2800001)
Conky: drawing to double buffer


  11:37:37 ~
         $ (sleep 2s && wmctrl -s 2 && conky -c ~/Conky/S11_Dates.conky) &
[6] 22082

  11:37:54 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x2a00001)
Conky: drawing to double buffer
Conky: Unable to load image '/home/sector11/Conky/images/cyan-1.png'


  11:38:04 ~
         $ (sleep 3s && wmctrl -s 2 && conky -c ~/Conky/S11_v9_SM.conky) &
[7] 22177

  11:38:18 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x2c00001)
Conky: drawing to double buffer
gathering data with curl
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--: 14 67927   14  9628    0     0  11155      0  0:00:06 --:--:--  0:00:100 67927  100 67927    0     0  35253      0  0:00:01  0:00:01 --:--:100 67927  100 67927    0     0  35251      0  0:00:01  0:00:01 --:--:-- 40098
not checking for alerts
processing complete


  11:38:35 ~
         $ (sleep 4s && wmctrl -s 2 && conky -c ~/Conky/S11_VNS.conky) &
[8] 22219

  11:39:02 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x2e00001)
Conky: drawing to double buffer


  11:39:21 ~
         $ (sleep 5s && wmctrl -s 1 && conky -c ~/Conky/S11_v9_H.conky) &
[9] 22316

  11:39:39 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3000001)
Conky: drawing to double buffer
gathering data with curl
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:  1 67927    1   868    0     0   1463      0  0:00:46 --:--:--  0:00:100 67927  100 67927    0     0  55283      0  0:00:01  0:00:01 --:--:-- 79914
not checking for alerts
processing complete


  11:39:53 ~
         $ (sleep 6s && wmctrl -s 0 && conky -c ~/Conky/S11_24_white.conky) &
[10] 22339

  11:40:08 ~
         $ p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3800001)
Conky: drawing to double buffer


  11:40:22 ~
         $ conky
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: forked to background, pid is 22374

  11:40:38 ~
         $ 
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3a00001)
Conky: drawing to double buffer
         $

Like I said, Any help appreciated. Do not want to go back to Statler and bring it up to testing again. This started with Waldorf.

EDIT:
Conky: Unable to load image '/home/sector11/Conky/images/cyan-1.png' fixed

Last edited by Sector11 (2012-05-13 15:13:33)

xaos52 · 2012-05-13 16:27:57

(1) install the package 'strace' if you have not installed it yet.
(2) run the conky that gives the error message thus:

strace -o conky.strace conky ....

complete it with the arguments you use
After you see the error message in the terminal, you can stop the trace by entering
CTRL+C
Publish the content of file conky.strace on the forum, preferrably using PASTEBIN.

Hopefully that will make clear how/why you get those messages.

Sector11 · 2012-05-13 16:54:53

@ xaos52

Won't need pastebin for this. Did as you said and since ALL conkys get the same error I ran the default conky:

  13:44:58 ~
         $ strace -o conky.strace conky
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Conky: forked to background, pid is 9339

  13:45:03 ~
         $ 
Conky: desktop window (15d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3a00001)
Conky: drawing to double buffer
         $ ^C

  13:45:45 ~
         $

And there it is running beside one of mine:

xaos52 · 2012-05-13 18:06:29

Publish the content of file conky.strace on the forum, preferrably using PASTEBIN.

cat conky.strace

and post the output big_smile

Sector11 · 2012-05-13 18:23:00

xaos52 wrote:

Publish the content of file conky.strace on the forum, preferrably using PASTEBIN.
cat conky.strace
and post the output

Now it's best in pastebin. big_smile

And it looks like alphabet soup to me. I am envious of people that can read that.

xaos52 · 2012-05-13 19:32:15

The "error" reported is harmless:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645959 for the gory details.

You can avoid seeing the message by launching your conky thusly:

conky 2>/dev/null

I do not recommend this, as it conky then drops all error messages in the /dev/null bit bucket without leaving a trace.
If you can live with that, by all means, use it.

hth

Sector11 · 2012-05-13 20:04:29

xaos52 wrote:

The "error" reported is harmless:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645959 for the gory details.
You can avoid seeing the message by launching your conky thusly:
conky 2>/dev/null
I do not recommend this, as it conky then drops all error messages in the /dev/null bit bucket without leaving a trace.
If you can live with that, by all means, use it.
hth

Thank you xaos52, as I breath a sigh of relief.

I'll live with it. cool <<-- wearing shades so I don't see it.

Last edited by Sector11 (2012-05-30 14:35:13)

radiot · 2012-05-30 14:25:12

Been having that error message as well, I guess, I can live with it.:D

CrunchBang Linux

SEARCH

#1 2012-05-11 04:08:32

[Solved³] Gnome Keyring - Do I need it?

#2 2012-05-11 14:57:26

Re: [Solved³] Gnome Keyring - Do I need it?

#3 2012-05-11 15:28:48

Re: [Solved³] Gnome Keyring - Do I need it?

#4 2012-05-11 15:35:00

Re: [Solved³] Gnome Keyring - Do I need it?

#5 2012-05-11 15:38:27

Re: [Solved³] Gnome Keyring - Do I need it?

#6 2012-05-11 16:19:51

Re: [Solved³] Gnome Keyring - Do I need it?

#7 2012-05-11 21:51:21

Re: [Solved³] Gnome Keyring - Do I need it?

#8 2012-05-11 21:54:52

Re: [Solved³] Gnome Keyring - Do I need it?

#9 2012-05-11 22:16:15

Re: [Solved³] Gnome Keyring - Do I need it?

#10 2012-05-11 23:12:07

Re: [Solved³] Gnome Keyring - Do I need it?

#11 2012-05-11 23:49:47

Re: [Solved³] Gnome Keyring - Do I need it?

#12 2012-05-11 23:50:38

Re: [Solved³] Gnome Keyring - Do I need it?

#13 2012-05-11 23:55:58

Re: [Solved³] Gnome Keyring - Do I need it?

#14 2012-05-12 08:14:52

Re: [Solved³] Gnome Keyring - Do I need it?

#15 2012-05-13 14:13:40

Re: [Solved³] Gnome Keyring - Do I need it?

#16 2012-05-13 14:16:46

Re: [Solved³] Gnome Keyring - Do I need it?

#17 2012-05-13 14:33:12

Re: [Solved³] Gnome Keyring - Do I need it?

#18 2012-05-13 15:00:49

Re: [Solved³] Gnome Keyring - Do I need it?

#19 2012-05-13 16:27:57

Re: [Solved³] Gnome Keyring - Do I need it?

#20 2012-05-13 16:54:53

Re: [Solved³] Gnome Keyring - Do I need it?

#21 2012-05-13 18:06:29

Re: [Solved³] Gnome Keyring - Do I need it?

#22 2012-05-13 18:23:00

Re: [Solved³] Gnome Keyring - Do I need it?

#23 2012-05-13 19:32:15

Re: [Solved³] Gnome Keyring - Do I need it?

#24 2012-05-13 20:04:29

Re: [Solved³] Gnome Keyring - Do I need it?

#25 2012-05-30 14:25:12

Re: [Solved³] Gnome Keyring - Do I need it?

Board footer