I THINK I GOT IT
I installed Seahorse and now I do not get prompted for passwords when I
open Evolution! I guess my keyring got messed up from changing DE's so
now everything is working fine! YAY
Thank ya'll
Chris
--
Thanks,
Chris
ch...@cwm030.com
On Sun, 2021-01-17 at 20:44 +0100, Ángel wrote:
> On 2021-01-17 at 10:46 -0600, Christopher Marlow wrote:
> > (evolution:1590): e-data-server-ui-WARNING **: 10:40:33.428:
> > credentials_prompter_store_credentials_cb: Failed to store source
> > credentials: No such interface “org.freedesktop.Secret
> Did you already mention how you start your user session? Are you
> using
> a display manger at all?
>
>
To answer your question by clicking on that link for Arch Linux
LXQT uses SDDM like KDE does.
"The Simple Desktop Display Manager (SDDM) a display manager. It is the
recommended display m
On Sun, 2021-01-17 at 23:32 +0100, Ralf Mardorf via evolution-list
wrote:
> >
> I'm not a LXDE user, but an openbox (no DE at all) user.
>
> https://wiki.archlinux.org/index.php/GNOME/Keyring
LXQT you mean. LXDE is dead.
>
>
> Did you already mention how you start your user session? Are you
PS:
On Sun, 17 Jan 2021 23:32:29 +0100, Ralf Mardorf wrote:
>https://wiki.archlinux.org/index.php/GNOME/Keyring
Since you are using SUSE, just ignore that this link mentions Arch
Linux. Consider to read it. It's not the answer to everything,
but it provides several pointers.
_
>On Sun, 2021-01-17 at 20:44 +0100, Ángel wrote:
>> Albeit hopefully redundant, I would recommend a reboot afterwards,
>> to ensure that if it is set to run on login by your distro
>> configuration, it does indeed start
There are some exceptions when a reboot is useful. Actually it's
usually possi
On Sun, 2021-01-17 at 20:44 +0100, Ángel wrote:
> (Albeit hopefully redundant, I would recommend a reboot afterwards,
> to
> ensure that if it is set to run on login by your distro
> configuration,
> it does indeed start)
It wont... I will have to manually add it to the LXQT start up list.
What c
On 2021-01-17 at 10:46 -0600, Christopher Marlow wrote:
> (evolution:1590): e-data-server-ui-WARNING **: 10:40:33.428:
> credentials_prompter_store_credentials_cb: Failed to store source
> credentials: No such interface “org.freedesktop.Secret.Collection” on
> object at path /org/freedesktop/secret
On Fri, 2021-01-15 at 08:48 +0100, Milan Crha via evolution-list wrote:
> On Thu, 2021-01-14 at 18:20 -0600, Christopher Marlow wrote:
> > How do I reenable gnome keyring and whats the next step?
>
> Hi,
> restart the machine and it'll start as usual.
>
> I mentioned it several times here a
On Fri, 2021-01-15 at 11:15 +, Patrick O'Callaghan wrote:
> On Thu, 2021-01-14 at 18:20 -0600, Christopher Marlow wrote:
> > chris@localhost:~> sudo pkill -TERM gnome-keyring-daemon
>
> 'sudo' should not be necessary. All the Evolution processes run under
> your own user. If that's not the cas
On Thu, 2021-01-14 at 18:20 -0600, Christopher Marlow wrote:
> chris@localhost:~> sudo pkill -TERM gnome-keyring-daemon
'sudo' should not be necessary. All the Evolution processes run under
your own user. If that's not the case, then something else is wrong.
poc
_
On Fri, 2021-01-15 at 08:48 +0100, Milan Crha via evolution-list wrote:
> On Thu, 2021-01-14 at 18:20 -0600, Christopher Marlow wrote:
> > How do I reenable gnome keyring and whats the next step?
Hi again,
another user reported this into the GitLab instance and gave steps how
to make it wo
On Thu, 2021-01-14 at 18:20 -0600, Christopher Marlow wrote:
> How do I reenable gnome keyring and whats the next step?
Hi,
restart the machine and it'll start as usual.
I mentioned it several times here and you seem to not care of it, but
do use seahorse application to check what the key
On 1/14/21 1:58 AM, Milan Crha via evolution-list wrote:
On Wed, 2021-01-13 at 12:13 -0600, Christopher Marlow wrote:
I do not know gnome-keyring internals at all. Maybe get rid of the
~/.local/share/keyrings/
directory (when the gnome-keyring-daemon is off),
How do you stop it and restart it
On Wed, 2021-01-13 at 12:13 -0600, Christopher Marlow wrote:
> > I do not know gnome-keyring internals at all. Maybe get rid of the
> > ~/.local/share/keyrings/
> > directory (when the gnome-keyring-daemon is off),
>
> How do you stop it and restart it?
Hi,
like anything else, basically:
On Wed, 2021-01-13 at 12:13 -0600, Christopher Marlow wrote:
>
> On 1/13/21 10:33 AM, Milan Crha via evolution-list wrote:
>
> > I do not know how you start the gnome-keyring-daemon, but for me it
> > has
> > added arguments: --daemonize --login
> > I suppose the --login is the important argument.
Milan
I just tried the unlock command and nothing happened. My terminal is
just sitting there.
chris@localhost:~> gnome-keyring-daemon -help
gnome-keyring-daemon: insufficient process capabilities, insecure memory
might get used
Usage:
gnome-keyring-daemon [OPTION…] - The Gnome Keyring D
On 1/13/21 10:33 AM, Milan Crha via evolution-list wrote:
I do not know how you start the gnome-keyring-daemon, but for me it has
added arguments: --daemonize --login
I suppose the --login is the important argument.
chris@localhost:~> gnome-keyring --daemonize --login
usage: gnome-keyring c
On Wed, 2021-01-13 at 09:20 -0600, Christopher Marlow wrote:
> evolution:23408): e-data-server-ui-WARNING **: 09:19:28.470:
> credentials_prompter_store_credentials_cb: Failed to store source
> credentials: Cannot create an item in a locked collection
Hi,
okay. I decipher that error mess
On 1/13/21 2:03 AM, Milan Crha via evolution-list wrote:
On Tue, 2021-01-12 at 12:46 -0600, Christopher Marlow wrote:
I don't understand this part.
Hi,
okay, in steps:
a) close Evolution
b) open terminal, run: evolution --force-shutdown
c) run in the terminal:
$ /usr/lib/evolutio
On Tue, 2021-01-12 at 12:46 -0600, Christopher Marlow wrote:
> I don't understand this part.
Hi,
okay, in steps:
a) close Evolution
b) open terminal, run: evolution --force-shutdown
c) run in the terminal:
$ /usr/lib/evolution-data-server/evolution-source-registry
Alternatively, yo
On Tue, 2021-01-12 at 12:46 -0600, Christopher Marlow wrote:
> I don't understand this part.
Then please explain what's unclear.
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
evolution-list mailing list
evolution-list@
On 1/12/21 11:29 AM, Milan Crha via evolution-list wrote:
O
Hi,
as I said, the actual path can differ in your distribution. I do not
know where they save it. Maybe try:
$ ps ax | grep evolution
When it's running it shows also the path to the file. If not running,
then start evolution and c
On Tue, 2021-01-12 at 11:25 -0600, Christopher Marlow wrote:
> On 1/12/21 10:57 AM, Milan Crha via evolution-list wrote:
> > (the actual path can differ in your distribution)
>
> chris@localhost:~> /usr/libexec/evolution-source-registry
> bash: /usr/libexec/evolution-source-registry: No such file
On 1/12/21 10:57 AM, Milan Crha via evolution-list wrote:
You can run the source registry from a terminal:
$ /usr/libexec/evolution-source-registry
(the actual path can differ in your distribution)
I am running Open Suse 15.2
chris@localhost:~> /usr/libexec/evolution-source-registry
ba
On Tue, 2021-01-12 at 10:39 -0600, Christopher Marlow wrote:
> I did not notice anything that says seahorse when I ran that command.
Hi,
Seahorse is a separate application. Shown here as "Passwords and Keys"
in the applications list.
> ...
> got auth type 'LOGIN'
> got auth type 'PLAIN'
>
On 1/12/21 3:17 AM, Milan Crha via evolution-list wrote:
evolution --force-shutdown
Chris@localhost:~> evolution --force-shutdown
Could not find Evolution's process ID
chris@localhost:~>
"when you confirmed the gnome-keyring is running? Did you see in the
Seahorse the keyring is unlocked
On Mon, 2021-01-11 at 12:47 -0600, Christopher Marlow wrote:
> I just restarted SUSE and EVO is still asking me for the password at
> start.
Hi,
did you try:
$ evolution --force-shutdown
$ evolution
when you confirmed the gnome-keyring is running? Did you see in the
Seahorse the k
On 1/11/21 11:33 AM, Christopher Marlow wrote:
On 1/11/21 2:40 AM, Milan Crha via evolution-list wrote:
ps ax | grep keyring
I just restarted SUSE and EVO is still asking me for the password at
start. :(
Chris
___
evolution-list mailing lis
On 1/11/21 2:40 AM, Milan Crha via evolution-list wrote:
On Sun, 2021-01-10 at 13:49 -0600, Christopher Marlow wrote:
Yes I restarted.
Hi,
you can check whether it is running when you run:
$ ps ax | grep keyring
I edited all 3 files and added to the line:
OnlyShowIn=GNOME;Uni
On 1/11/21 2:40 AM, Milan Crha via evolution-list wrote:
ps ax | grep keyring
This is what I get:
chris@localhost:~> ps ax | grep keyring
15250 ? Sl 0:00 /usr/bin/gnome-keyring-daemon
17187 pts/0 S+ 0:00 grep --color=auto keyring
chris@localhost:~>
And to answer Angel...
On Sun, 2021-01-10 at 13:49 -0600, Christopher Marlow wrote:
> Yes I restarted.
Hi,
you can check whether it is running when you run:
$ ps ax | grep keyring
When I run it here I see as one of the lines:
1289 ?SLl0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
On Sun, 2021-01-10 at 13:49 -0600, Christopher Marlow wrote:
> On 1/10/21 1:34 PM, Andre Klapper via evolution-list wrote:
> > On Sun, 2021-01-10 at 11:07 -0600, Christopher Marlow wrote:
> > > I just tried editing that line in sudo nano
> > > /etc/xdg/autostart/gnome-
> > > keyring-*.desktop and
On 2021-01-10 at 13:49 -0600, Christopher Marlow wrote:
> > On Sun, 2021-01-10 at 11:07 -0600, Christopher Marlow wrote:
> > > I just tried editing that line in sudo nano
> > > /etc/xdg/autostart/gnome-
> > > keyring-*.desktop and evo is still asking me for the password on
> > > start.
> >
> I w
On 1/10/21 1:34 PM, Andre Klapper via evolution-list wrote:
On Sun, 2021-01-10 at 11:07 -0600, Christopher Marlow wrote:
I just tried editing that line in sudo nano
/etc/xdg/autostart/gnome-
keyring-*.desktop and evo is still asking me for the password on
start.
Please be specific. Which exac
On Sun, 2021-01-10 at 11:07 -0600, Christopher Marlow wrote:
> I just tried editing that line in sudo nano
> /etc/xdg/autostart/gnome-
> keyring-*.desktop and evo is still asking me for the password on
> start.
Please be specific. Which exact file did you edit? Which line did you
change to what e
I just tried editing that line in sudo nano /etc/xdg/autostart/gnome-
keyring-*.desktop and evo is still asking me for the password on start.
It has only started this since switching to LXQT.
I tried to open your last reply to me after editing that file and I get
this error:
Unable to retrieve
On Sat, 2021-01-09 at 10:56 -0600, Christopher Marlow wrote:
> How do I go about setting up the daemon if that is what my problem
> is?
https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/71 might be
related, if I understand correctly. You could try edit the files
»/etc/xdg/autostart/gnome-keyr
On Sat, 2021-01-09 at 11:26 +0100, Andre Klapper via evolution-list
> >
> Password for what exactly? "Constantly" means what? Every other
> minute
> while running Evolution? When it starts? Something else?
> Please don't make us guess and leave no room for interpretation.
Everytime I open evo I
On Fri, 2021-01-08 at 20:41 -0600, Christopher Marlow wrote:
> I know I havent asked this before because I keep all questions i've
> asked in a folder and this question isnt in there.
>
> Anyways Evolution is asking for my password constantly again.
Password for what exactly? "Constantly" means wh
On Fri, 2021-01-08 at 20:41 -0600, Christopher Marlow wrote:
> I know I havent asked this before because I keep all questions i've
> asked in a folder and this question isnt in there.
>
> Anyways Evolution is asking for my password constantly again. I dont
> know if I have uninstalled something o
I know I havent asked this before because I keep all questions i've
asked in a folder and this question isnt in there.
Anyways Evolution is asking for my password constantly again. I dont
know if I have uninstalled something or what. I typed into my terminal
sudo zypper gnome-keyring and it says
42 matches
Mail list logo
