Disable gnome-keyring-daemon
up vote
7
down vote
favorite
Methods I have tried:
- https://wiki.gnupg.org/GnomeKeyring
- https://blog.josefsson.org/tag/keyring/
- Removing the GNOME Keyring applications from Startup Applications
- http://lechnology.com/software/keeagent/installation/#disable-ssh-component-of-gnome-keyring
None of these stop this process from being started when I log in:
me 1865 0.0 0.0 281816 7104 ? Sl 10:50 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
This stops my Thunderbird from decrypting emails properly. When I kill the process, I can decrypt emails as expected but I don't want to have to do that every time I log in.
OS Information: Debian GNU/Linux 8.3 (jessie)
Can anyone help?
debian gpg thunderbird gnome-keyring enigmail
asked Mar 23 '16 at 11:02
Proletariat
307520
add a comment |
up vote
7
down vote
favorite
Methods I have tried:
- https://wiki.gnupg.org/GnomeKeyring
- https://blog.josefsson.org/tag/keyring/
- Removing the GNOME Keyring applications from Startup Applications
- http://lechnology.com/software/keeagent/installation/#disable-ssh-component-of-gnome-keyring
None of these stop this process from being started when I log in:
me 1865 0.0 0.0 281816 7104 ? Sl 10:50 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
This stops my Thunderbird from decrypting emails properly. When I kill the process, I can decrypt emails as expected but I don't want to have to do that every time I log in.
OS Information: Debian GNU/Linux 8.3 (jessie)
Can anyone help?
debian gpg thunderbird gnome-keyring enigmail
asked Mar 23 '16 at 11:02
Proletariat
307520
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
Methods I have tried:
- https://wiki.gnupg.org/GnomeKeyring
- https://blog.josefsson.org/tag/keyring/
- Removing the GNOME Keyring applications from Startup Applications
- http://lechnology.com/software/keeagent/installation/#disable-ssh-component-of-gnome-keyring
None of these stop this process from being started when I log in:
me 1865 0.0 0.0 281816 7104 ? Sl 10:50 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
This stops my Thunderbird from decrypting emails properly. When I kill the process, I can decrypt emails as expected but I don't want to have to do that every time I log in.
OS Information: Debian GNU/Linux 8.3 (jessie)
Can anyone help?
debian gpg thunderbird gnome-keyring enigmail
asked Mar 23 '16 at 11:02
Proletariat
307520
Methods I have tried:
- https://wiki.gnupg.org/GnomeKeyring
- https://blog.josefsson.org/tag/keyring/
- Removing the GNOME Keyring applications from Startup Applications
- http://lechnology.com/software/keeagent/installation/#disable-ssh-component-of-gnome-keyring
None of these stop this process from being started when I log in:
me 1865 0.0 0.0 281816 7104 ? Sl 10:50 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
This stops my Thunderbird from decrypting emails properly. When I kill the process, I can decrypt emails as expected but I don't want to have to do that every time I log in.
OS Information: Debian GNU/Linux 8.3 (jessie)
Can anyone help?
debian gpg thunderbird gnome-keyring enigmail
debian gpg thunderbird gnome-keyring enigmail
asked Mar 23 '16 at 11:02
Proletariat
307520
asked Mar 23 '16 at 11:02
Proletariat
307520
asked Mar 23 '16 at 11:02
Proletariat
307520
asked Mar 23 '16 at 11:02
Proletariat
307520
asked Mar 23 '16 at 11:02
Proletariat
307520
307520
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
up vote
2
down vote
For simple disabling (rather than removing), how about removing execute permission? (You will need appropriate permissions, so you may need to prefix sudo)
chmod -x $(type -p gnome-keyring-daemon)
You could also kill the process if its currently running:
pkill gnome-keyring-daemon
answered Jul 28 '16 at 15:34
user1093043
414
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
add a comment |
up vote
2
down vote
Actually the gnome-keyring-daemon in several cases is started via X login using the PAM (Plugabble Authentication Modules) files, but there is other ways like autostart files too GnomeKeyring/RunningDaemon. You can look in detail about the integration of PAM on official documentation. But in general you just need to detect which desktop manager are you using and delete the entries on your /etc/pam.d/<desktop_manager>.
In my case, I use the lightdm. So I have a PAM file called /etc/pam.d/lightdm which has that contents:
❯ cat /etc/pam.d/lightdm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
account include system-login
password include system-login
session include system-login
-session optional pam_gnome_keyring.so auto_start
Deleting or comment the entries which call the pam_gnome_keyring.so module, located on /lib/security, you can accomplish the full disable of the daemon on login. To be sure, look to /etc/xdg/autostart and ~/.config/autostart for files with the pattern gnome-keyring-*.desktop and append Hidden=true on each file to disable that componentes as well.
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
add a comment |
up vote
0
down vote
You could try removing the gnome-keyring package.
answered Mar 23 '16 at 15:32
MagicFab
1635
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove thegnome-keyringpackage will also remove thegnomepackage and numerous others. (In an ideal world, removing thegnome-keyringpackage would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)
– sampablokuper
Jan 22 at 7:18
add a comment |
up vote
0
down vote
Open System Monitor, in processes tab scroll down and select gnome-keyring-daemon. and click end process.
I am using Kali GNU/Linux Rolling and it worked for me.
answered Mar 12 at 6:01
Smshrimant
144
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
For simple disabling (rather than removing), how about removing execute permission? (You will need appropriate permissions, so you may need to prefix sudo)
chmod -x $(type -p gnome-keyring-daemon)
You could also kill the process if its currently running:
pkill gnome-keyring-daemon
answered Jul 28 '16 at 15:34
user1093043
414
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
add a comment |
up vote
2
down vote
For simple disabling (rather than removing), how about removing execute permission? (You will need appropriate permissions, so you may need to prefix sudo)
chmod -x $(type -p gnome-keyring-daemon)
You could also kill the process if its currently running:
pkill gnome-keyring-daemon
answered Jul 28 '16 at 15:34
user1093043
414
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
add a comment |
up vote
2
down vote
up vote
2
down vote
For simple disabling (rather than removing), how about removing execute permission? (You will need appropriate permissions, so you may need to prefix sudo)
chmod -x $(type -p gnome-keyring-daemon)
You could also kill the process if its currently running:
pkill gnome-keyring-daemon
answered Jul 28 '16 at 15:34
user1093043
414
For simple disabling (rather than removing), how about removing execute permission? (You will need appropriate permissions, so you may need to prefix sudo)
chmod -x $(type -p gnome-keyring-daemon)
You could also kill the process if its currently running:
pkill gnome-keyring-daemon
answered Jul 28 '16 at 15:34
user1093043
414
edited Jul 28 '16 at 15:52
answered Jul 28 '16 at 15:34
user1093043
414
answered Jul 28 '16 at 15:34
user1093043
414
answered Jul 28 '16 at 15:34
user1093043
414
414
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
add a comment |
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
1
1
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Technically that is correct, but pretty horrible. You will end with errors poping up in journalctl and/or syslog. Also, you need root to perform those commands (that would be wise to mention in the answer)
– grochmal
Jul 28 '16 at 15:46
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
Very fair point. However I would add that there will only be a few log lines---not enough to cause problems by drowning out real logged events---so you may be willing to accept this cost at least until a more elegant solution is found. (edited answer to reflect need for permissions)
– user1093043
Jul 28 '16 at 16:00
add a comment |
up vote
2
down vote
Actually the gnome-keyring-daemon in several cases is started via X login using the PAM (Plugabble Authentication Modules) files, but there is other ways like autostart files too GnomeKeyring/RunningDaemon. You can look in detail about the integration of PAM on official documentation. But in general you just need to detect which desktop manager are you using and delete the entries on your /etc/pam.d/<desktop_manager>.
In my case, I use the lightdm. So I have a PAM file called /etc/pam.d/lightdm which has that contents:
❯ cat /etc/pam.d/lightdm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
account include system-login
password include system-login
session include system-login
-session optional pam_gnome_keyring.so auto_start
Deleting or comment the entries which call the pam_gnome_keyring.so module, located on /lib/security, you can accomplish the full disable of the daemon on login. To be sure, look to /etc/xdg/autostart and ~/.config/autostart for files with the pattern gnome-keyring-*.desktop and append Hidden=true on each file to disable that componentes as well.
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
add a comment |
up vote
2
down vote
Actually the gnome-keyring-daemon in several cases is started via X login using the PAM (Plugabble Authentication Modules) files, but there is other ways like autostart files too GnomeKeyring/RunningDaemon. You can look in detail about the integration of PAM on official documentation. But in general you just need to detect which desktop manager are you using and delete the entries on your /etc/pam.d/<desktop_manager>.
In my case, I use the lightdm. So I have a PAM file called /etc/pam.d/lightdm which has that contents:
❯ cat /etc/pam.d/lightdm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
account include system-login
password include system-login
session include system-login
-session optional pam_gnome_keyring.so auto_start
Deleting or comment the entries which call the pam_gnome_keyring.so module, located on /lib/security, you can accomplish the full disable of the daemon on login. To be sure, look to /etc/xdg/autostart and ~/.config/autostart for files with the pattern gnome-keyring-*.desktop and append Hidden=true on each file to disable that componentes as well.
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
add a comment |
up vote
2
down vote
up vote
2
down vote
Actually the gnome-keyring-daemon in several cases is started via X login using the PAM (Plugabble Authentication Modules) files, but there is other ways like autostart files too GnomeKeyring/RunningDaemon. You can look in detail about the integration of PAM on official documentation. But in general you just need to detect which desktop manager are you using and delete the entries on your /etc/pam.d/<desktop_manager>.
In my case, I use the lightdm. So I have a PAM file called /etc/pam.d/lightdm which has that contents:
❯ cat /etc/pam.d/lightdm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
account include system-login
password include system-login
session include system-login
-session optional pam_gnome_keyring.so auto_start
Deleting or comment the entries which call the pam_gnome_keyring.so module, located on /lib/security, you can accomplish the full disable of the daemon on login. To be sure, look to /etc/xdg/autostart and ~/.config/autostart for files with the pattern gnome-keyring-*.desktop and append Hidden=true on each file to disable that componentes as well.
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
Actually the gnome-keyring-daemon in several cases is started via X login using the PAM (Plugabble Authentication Modules) files, but there is other ways like autostart files too GnomeKeyring/RunningDaemon. You can look in detail about the integration of PAM on official documentation. But in general you just need to detect which desktop manager are you using and delete the entries on your /etc/pam.d/<desktop_manager>.
In my case, I use the lightdm. So I have a PAM file called /etc/pam.d/lightdm which has that contents:
❯ cat /etc/pam.d/lightdm
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
account include system-login
password include system-login
session include system-login
-session optional pam_gnome_keyring.so auto_start
Deleting or comment the entries which call the pam_gnome_keyring.so module, located on /lib/security, you can accomplish the full disable of the daemon on login. To be sure, look to /etc/xdg/autostart and ~/.config/autostart for files with the pattern gnome-keyring-*.desktop and append Hidden=true on each file to disable that componentes as well.
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
edited Nov 30 at 18:10
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
answered Oct 12 '17 at 8:17
Manoel Vilela
1317
1317
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
add a comment |
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
1
1
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
It should be the accepted answer. Thanks. I use so I've commented the lines in the files /etc/pam.d/gdm-*
– Kevin Lemaire
Jun 1 at 10:31
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
Great to know that works for you too, @KevinLemaire!
– Manoel Vilela
Jun 2 at 17:25
add a comment |
up vote
0
down vote
You could try removing the gnome-keyring package.
answered Mar 23 '16 at 15:32
MagicFab
1635
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove thegnome-keyringpackage will also remove thegnomepackage and numerous others. (In an ideal world, removing thegnome-keyringpackage would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)
– sampablokuper
Jan 22 at 7:18
add a comment |
up vote
0
down vote
You could try removing the gnome-keyring package.
answered Mar 23 '16 at 15:32
MagicFab
1635
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove thegnome-keyringpackage will also remove thegnomepackage and numerous others. (In an ideal world, removing thegnome-keyringpackage would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)
– sampablokuper
Jan 22 at 7:18
add a comment |
up vote
0
down vote
up vote
0
down vote
You could try removing the gnome-keyring package.
answered Mar 23 '16 at 15:32
MagicFab
1635
You could try removing the gnome-keyring package.
answered Mar 23 '16 at 15:32
MagicFab
1635
answered Mar 23 '16 at 15:32
MagicFab
1635
answered Mar 23 '16 at 15:32
MagicFab
1635
answered Mar 23 '16 at 15:32
MagicFab
1635
1635
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove thegnome-keyringpackage will also remove thegnomepackage and numerous others. (In an ideal world, removing thegnome-keyringpackage would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)
– sampablokuper
Jan 22 at 7:18
add a comment |
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove thegnome-keyringpackage will also remove thegnomepackage and numerous others. (In an ideal world, removing thegnome-keyringpackage would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)
– sampablokuper
Jan 22 at 7:18
1
1
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove the
gnome-keyring package will also remove the gnome package and numerous others. (In an ideal world, removing the gnome-keyring package would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)– sampablokuper
Jan 22 at 7:18
This is dangerous advice. Unfortunately, on many GNU/Linux distributions, using your package manager to remove the
gnome-keyring package will also remove the gnome package and numerous others. (In an ideal world, removing the gnome-keyring package would indeed be the right answer, but in the real world, unless you want to uninstall your whole desktop environment, you should evaluate other solutions.)– sampablokuper
Jan 22 at 7:18
add a comment |
up vote
0
down vote
Open System Monitor, in processes tab scroll down and select gnome-keyring-daemon. and click end process.
I am using Kali GNU/Linux Rolling and it worked for me.
answered Mar 12 at 6:01
Smshrimant
144
add a comment |
up vote
0
down vote
Open System Monitor, in processes tab scroll down and select gnome-keyring-daemon. and click end process.
I am using Kali GNU/Linux Rolling and it worked for me.
answered Mar 12 at 6:01
Smshrimant
144
add a comment |
up vote
0
down vote
up vote
0
down vote
Open System Monitor, in processes tab scroll down and select gnome-keyring-daemon. and click end process.
I am using Kali GNU/Linux Rolling and it worked for me.
answered Mar 12 at 6:01
Smshrimant
144
Open System Monitor, in processes tab scroll down and select gnome-keyring-daemon. and click end process.
I am using Kali GNU/Linux Rolling and it worked for me.
answered Mar 12 at 6:01
Smshrimant
144
answered Mar 12 at 6:01
Smshrimant
144
answered Mar 12 at 6:01
Smshrimant
144
answered Mar 12 at 6:01
Smshrimant
144
144
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f271661%2fdisable-gnome-keyring-daemon%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
