LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Blogs > MadMaverick9's Blog
User Name
Password

Notices


Rate this Entry

How to stop the gnome-keyring on Slackware

Posted 11-24-2021 at 10:54 PM by MadMaverick9
Updated 11-24-2021 at 10:58 PM by MadMaverick9

I saw the same error messages in "/var/log/syslog" and "/var/log/secure" as somebody else posted here on unix.stackexchange.com.
Code:
Nov 23 00:00:00 darkstar gnome-keyring-daemon[1649]: couldn't create socket directory: /home/root/.cache/keyring-ZQHED1: Permission denied
Nov 23 00:00:00 darkstar gnome-keyring-daemon[1649]: couldn't bind to control socket: /home/root/.cache/keyring-ZQHED1/control: Permission denied
Nov 23 00:00:00 darkstar gnome-keyring-daemon[1686]: couldn't create socket directory: /home/root/.cache/keyring-IB8UC1: Permission denied
Nov 23 00:00:00 darkstar gnome-keyring-daemon[1686]: couldn't bind to control socket: /home/root/.cache/keyring-IB8UC1/control: Permission denied
Code:
Nov 23 00:00:00 darkstar sudo: gkr-pam: unable to locate daemon control file
Nov 23 00:00:00 darkstar sudo: gkr-pam: gnome-keyring-daemon started properly
The following change is what got rid of those messages:
Code:
bash $ diff -u a/etc/pam.d/system-auth b/etc/pam.d/system-auth
--- a/etc/pam.d/system-auth 2021-11-23 00:00:00.0 +0000
+++ b/etc/pam.d/system-auth 2021-11-23 00:00:00.0 +0000
@@ -11,7 +11,7 @@
 auth        required      pam_env.so
 auth        optional      pam_group.so
 auth        required      pam_unix.so likeauth nullok
--auth       optional      pam_gnome_keyring.so
+#-auth       optional      pam_gnome_keyring.so

 ##################
 # Account checks #
@@ -66,4 +66,4 @@
 session     required      pam_unix.so
 #session     required      pam_lastlog.so showfailed
 #session     optional      pam_mail.so standard
--session     optional      pam_gnome_keyring.so auto_start
+#-session     optional      pam_gnome_keyring.so auto_start
bash $
Why was I annoyed by these messages?
  • I do not use "gnome-keyring-daemon" or any other gnome stuff for that matter, so why is Slackware "-current" trying to start "gnome-keyring-daemon".
  • I was ssh-ing into this Slackware "-current" machine as a regular user, so why is "gnome-keyring-daemon" trying to create a file in "/home/root/.cache/".
Posted in Uncategorized
Views 803 Comments 0
« Prev     Main     Next »

  



All times are GMT -5. The time now is 11:47 AM.

Main Menu
Advertisement
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration