On Wed, 2020-02-12 at 17:11 +, Patrick O'Callaghan wrote:
> On Wed, 2020-02-12 at 14:37 +0100, Milan Crha via evolution-list wrote:
> > Using `loginctl list-sessions` and being logged in as a root in a text
> > terminal I see that there are two sessions, one for the root and one
> > for the log
On Wed, 2020-02-12 at 14:37 +0100, Milan Crha via evolution-list wrote:
> Using `loginctl list-sessions` and being logged in as a root in a text
> terminal I see that there are two sessions, one for the root and one
> for the logged used in the KDE desktop. When I log out of the KDE,
> there are le
On Wed, 2020-02-12 at 12:12 +0100, Patrick O'Callaghan wrote:
> Simply logging out and in again (BTW we
> need a word for "logging out and in again" :-) doesn't seem to do it,
> the reason being that g-k-r is already running. However, if I log
> out, kill g-k-r and log in again, the errors pop up.
On Tue, 2020-02-11 at 17:31 +, Pete Biggs wrote:
> > ksecretservice is definitely not running. In fact I don't think it's
> > even installed on my system. However kwalletd, which is the standard
> > KDE daemon, is running as well as gnome-keyring. If that's the source
> > of the trouble I don't
> ksecretservice is definitely not running. In fact I don't think it's
> even installed on my system. However kwalletd, which is the standard
> KDE daemon, is running as well as gnome-keyring. If that's the source
> of the trouble I don't see why killing Evo and restarting it would make
> a diffe
On Tue, 2020-02-11 at 17:34 +0100, Milan Crha via evolution-list wrote:
> you can search /usr/share/dbus-1/ for files containing
> org.freedesktop.secrets . That would be the place where the service
> should be properly advertised [*]. My installation contains only a
> single file, referencing gnom
On Tue, 2020-02-11 at 15:50 +, Pete Biggs wrote:
> > that would probably work, if evolution (and especially evolution-
> > source-registry) talks to the gnome-keyring-daemon directly. It's not
> > the case, evolution(-data-server) uses libsecret and what libsecret
> > does in the background is
On Tue, 2020-02-11 at 16:24 +0100, Milan Crha via evolution-list wrote:
> I guess, and only guess, that the gnome-keyring-daemon had been
> killed/stopped somewhere after step c), keeping libsecret without its
> counterpart.
>
> What is the error message when you face this, please?
Evo complains
On Tue, 2020-02-11 at 17:20 +0100, Pete Biggs wrote:
> Other posts I've seen have said that ksecretservice has died and that
> there are no other applications that provide the same functionality
> in KDE. So probably a theoretical issue, not a real-life one.
Hi,
you can search /usr/share/d
>
> > Is it possible that that under KDE it is trying to use
> > ksecretservice because that happens to have already been started by
> > KDE?
>
> Only if it provides the D-Bus service. I've been told, not so long ago,
> that KDE still doesn't have org.freedesktop.secrets implementation. It
> ca
Hi,
On Tue, 2020-02-11 at 16:50 +0100, Pete Biggs wrote:
> Am I right in thinking that libsecret doesn't specifically use gnome-
> keyring?
As far as I know, libsecret talks to org.freedesktop.secrets D-Bus
service. It doesn't talk to a specific process, it uses whatever
implements it.
>
> that would probably work, if evolution (and especially evolution-
> source-registry) talks to the gnome-keyring-daemon directly. It's not
> the case, evolution(-data-server) uses libsecret and what libsecret
> does in the background is up to it. The libsecret used to have issues
> to work prope
On Tue, 2020-02-11 at 13:19 +0100, Patrick O'Callaghan wrote:
> Why should the user have to do this, or even know that it needs to be
> done? If Evo depends on g-k-r for correct functioning, shouldn't it
> take care of this itself?
Hi,
that would probably work, if evolution (and especially
I use Evolution (currently 3.34.3 but this issue has been around for a
while) on KDE rather than Gnome. When I log in, there's a non-zero
probability that Evo won't start correctly because gnome-keyring isn't
running, i.e. Evo has started before g-k-r. The quick solution is to
kill all Evo processe
14 matches
Mail list logo
