11 Jan 14 | 14:57:19 ~ $ conky -c /media/5/conky/test.conky &  3277 11 Jan 14 | 14:57:21 ~ $ Conky: forked to background, pid is 3290 Conky: desktop window (264) is root window Conky: window type - normal Conky: drawing to created window (0x3600001) Conky: drawing to double buffer
Last edited by Sector11 (2014-01-11 18:18:40)
sudo apt-get --purge remove libgnome-keyring-common libgnome-keyring0 libp11-kit0
Last edited by ew (2013-12-27 01:42:52)
- apt-mark hold account
I don't think there are any "real" gnome dependencies for gnome keyring. I imagine that if the keyring is not empty it would not be removed entirely - even if you "purge" it - at least I would hope there would be some sort of error message before removal. The keyring is the same as that found in the "keyctl" utility - or at least that's my understanding... the gnome keyring API is an interface to the keyctl utility - again, my understanding... I would recommend ensuring gnome keyring is installed completely rather than attempting to purge it - it's possible you have "active" keys/passwords/etc listed on under the "gnome keyring" keyring...
"keyctl show" is useful for beginning to probe deeper into keyrings...
Hopefully more learned "others" will correct my possible misunderstandings...
I have always removed gnome-keyring this is a fresh re-install if Waldorf as Debian SID died when my HDD died. I had #! installed on that drive as well without gnome-keyring so I'm not sure why this one won't go.
27 Dec 13 | 09:50:18 ~ $ remv libp11-kit0 [sudo] password for sector11: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcurl3-gnutls : Depends: libgnutls26 (>= 2.12.17-0) but it is not going to be installed Depends: libldap-2.4-2 (>= 2.4.7) but it is not going to be installed Depends: librtmp0 (>= 2.3) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. 27 Dec 13 | 09:50:30 ~ $
Well, it's not "held" packages:
27 Dec 13 | 09:50:30 ~ $ dpkg --get-selections | grep hold 27 Dec 13 | 09:52:09 ~ $
i don't use gnome-keyring either. i simply don't trust anything to store my passwords. and i wouldn't touch gnome with a barge pole either.
leaner code is cleaner code is more efficient code
27 Dec 13 | 12:38:36 ~ $ sremv libpam-gnome-keyring [sudo] password for sector11: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: crda dnsmasq-base iw libjim0debian2 libnetfilter-conntrack3 libnl-route-3-200 libnm-gtk-common libnm-gtk0 libpam-gnome-keyring mobile-broadband-provider-info modemmanager network-manager usb-modeswitch usb-modeswitch-data wireless-regdb 0 upgraded, 0 newly installed, 15 to remove and 0 not upgraded. Remv crda [1.1.2-1] Remv dnsmasq-base [2.62-3+deb7u1] Remv iw [3.4-1] Remv usb-modeswitch [1.2.3+repack0-1] Remv libjim0debian2 [0.73-3] Remv libnetfilter-conntrack3 [1.0.1-1] Remv network-manager [0.9.4.0-10] Remv libnl-route-3-200 [3.2.7-4] Remv libnm-gtk0 [0.9.4.1-5] Remv libnm-gtk-common [0.9.4.1-5] Remv libpam-gnome-keyring [3.4.1-5] Remv mobile-broadband-provider-info [20120708-1] Remv modemmanager [0.5.2.0-2] Remv usb-modeswitch-data [20120815-2] Remv wireless-regdb [2011.04.28-1] 27 Dec 13 | 12:38:59 ~ $ remv libpam-gnome-keyring Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: crda dnsmasq-base iw libjim0debian2 libnetfilter-conntrack3 libnl-route-3-200 libnm-gtk-common libnm-gtk0 libpam-gnome-keyring mobile-broadband-provider-info modemmanager network-manager usb-modeswitch usb-modeswitch-data wireless-regdb 0 upgraded, 0 newly installed, 15 to remove and 0 not upgraded. After this operation, 8,412 kB disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 99554 files and directories currently installed.) Removing crda ... Removing dnsmasq-base ... Removing iw ... Removing usb-modeswitch ... Removing libjim0debian2:amd64 ... Removing libnetfilter-conntrack3:amd64 ... Removing network-manager ... Stopping network connection manager: NetworkManager. Removing libnl-route-3-200:amd64 ... Removing libnm-gtk0 ... Removing libnm-gtk-common ... Removing libpam-gnome-keyring ... Removing mobile-broadband-provider-info ... Removing modemmanager ... Removing usb-modeswitch-data ... Removing wireless-regdb ... Processing triggers for man-db ... Processing triggers for hicolor-icon-theme ... 27 Dec 13 | 12:39:30 ~ $ conky -c /media/5/Conky/V9-hourly-data.conky &  15810 27 Dec 13 | 12:39:39 ~ $ WARNING: gnome-keyring:: couldn't connect to: /home/sector11/.cache/keyring-I4M2nb/pkcs11: No such file or directory Conky: forked to background, pid is 15815
ls -l /etc/xdg/autostart
might be useful to page through or edit --- but hopefully those entries would have been cleaned up with the "purge" ... maybe not though...
I have been fiddling with gnome-keyring (and with ssh-agent) for a few days ... I wanted to get rid of DM (Slim), and start my WM (pekwm) from startx. And I wanted just opposite of you: to get gnome-keyring running.
What I have learned/discovered so far is:
1) login processes (either with SLIM or plain console login; I do not know which one you have) establish some sort of 'keyring'. This is controlled by '/etc/pam.d/*' config files. I do not fully understand those config files, but it is instructive to see
$ more /etc/pam.d/slim
i.e. what slim does. Also what pure (console) logging in does:
$ more /etc/pam.d/login
So, as soon as you use PAM, there is an almost 100% chance that you are storing your password somehow in memory.
Conclusion: per default, #! with SLIM starts gnome-keyring. #! without slim seems to start some sort of 'ssh-agent'.
2) When SLIM starts openbox, it sources files in '/etc/X11/Xsession.d/'. See:
$ more /etc/X11/Xsession.d/90x11-common_ssh-agent
This file checks for already running 'key-agent' (any software taking care of storing login passwords in memory for future use). If none is present, then it starts 'ssh-agent' for just this purpose. I don't know if this is really necessary or not for normal system functioning. Normally, in vanilla #!, at this point, 'key-agent' software is already running, and this file does nothing.
Conclusion: even if you remove PAM, you will have to deal with this 'ssh-agent', is you are running X.
To avoid TL;DR, let my just say that for you it might be enough to remove (i.e. comment out) lines with
in '/etc/pam.d/*' config files. But, there is still chance that some other 'key-agent' stores passwords in memory.
PS. Be careful, read man, as you can render your system unusable.
This might be useful:
grep --color=auto -e gnome /etc/pam.d/*
11 Jan 14 | 11:48:26 ~ $ keyctl show bash: keyctl: command not found 11 Jan 14 | 11:49:29 ~ $ sudo keyctl show [sudo] password for sector11: sudo: keyctl: command not found 11 Jan 14 | 11:49:39 ~ $ ser keyctl 11 Jan 14 | 11:49:59 ~ $ sho keyctl E: Unable to locate package keyctl 11 Jan 14 | 11:50:05 ~ $
Last edited by hhh (2014-01-11 16:10:38)
$ apt-file search keyctl ... keyutils: /bin/keyctl ...
Last edited by porkpiehat (2014-01-11 16:02:41)