Evolution gets D-Bus error when trying to send from alias account
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
In Evolution I set up a second account which only sends email, to create a alias using the GMail "+" trick. That is, my main Evolution account is something like john.doe@gmail.com
and the alias account is like john.doe+FOOBAR@gmail.com
. Upon creating the alias account Evolution sent me to GMail to log in for an OAuth token, I tested the account and it worked just fine.
However, now that I've logged out of my desktop and back in again, every attempt to send from the alias account gets the error. The full error from the log journal is:
evolution-sourc[2880]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.734 was not provided by any .service files
I can send emails just fine with my original/default Evolution account.
I'm using Fedora 28 and KDE.
EDIT: Looks like it might be due to this gnome keyring bug. Unfortunately there's no suggested workarounds. I tried replacing the gnome keyring daemon with gnome-keyring-daemon --replace --blah --blah
, but that didn't help.
fedora kde gnome-keyring evolution
add a comment |Â
up vote
0
down vote
favorite
In Evolution I set up a second account which only sends email, to create a alias using the GMail "+" trick. That is, my main Evolution account is something like john.doe@gmail.com
and the alias account is like john.doe+FOOBAR@gmail.com
. Upon creating the alias account Evolution sent me to GMail to log in for an OAuth token, I tested the account and it worked just fine.
However, now that I've logged out of my desktop and back in again, every attempt to send from the alias account gets the error. The full error from the log journal is:
evolution-sourc[2880]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.734 was not provided by any .service files
I can send emails just fine with my original/default Evolution account.
I'm using Fedora 28 and KDE.
EDIT: Looks like it might be due to this gnome keyring bug. Unfortunately there's no suggested workarounds. I tried replacing the gnome keyring daemon with gnome-keyring-daemon --replace --blah --blah
, but that didn't help.
fedora kde gnome-keyring evolution
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In Evolution I set up a second account which only sends email, to create a alias using the GMail "+" trick. That is, my main Evolution account is something like john.doe@gmail.com
and the alias account is like john.doe+FOOBAR@gmail.com
. Upon creating the alias account Evolution sent me to GMail to log in for an OAuth token, I tested the account and it worked just fine.
However, now that I've logged out of my desktop and back in again, every attempt to send from the alias account gets the error. The full error from the log journal is:
evolution-sourc[2880]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.734 was not provided by any .service files
I can send emails just fine with my original/default Evolution account.
I'm using Fedora 28 and KDE.
EDIT: Looks like it might be due to this gnome keyring bug. Unfortunately there's no suggested workarounds. I tried replacing the gnome keyring daemon with gnome-keyring-daemon --replace --blah --blah
, but that didn't help.
fedora kde gnome-keyring evolution
In Evolution I set up a second account which only sends email, to create a alias using the GMail "+" trick. That is, my main Evolution account is something like john.doe@gmail.com
and the alias account is like john.doe+FOOBAR@gmail.com
. Upon creating the alias account Evolution sent me to GMail to log in for an OAuth token, I tested the account and it worked just fine.
However, now that I've logged out of my desktop and back in again, every attempt to send from the alias account gets the error. The full error from the log journal is:
evolution-sourc[2880]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.734 was not provided by any .service files
I can send emails just fine with my original/default Evolution account.
I'm using Fedora 28 and KDE.
EDIT: Looks like it might be due to this gnome keyring bug. Unfortunately there's no suggested workarounds. I tried replacing the gnome keyring daemon with gnome-keyring-daemon --replace --blah --blah
, but that didn't help.
fedora kde gnome-keyring evolution
fedora kde gnome-keyring evolution
edited Aug 24 at 3:03
asked Aug 24 at 0:05
Matthew Cline
1,24011021
1,24011021
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34
add a comment |Â
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Looks like the problem is that some user session daemon isn't quitting when the session is over. Since I use SDDM I fixed the problem by editing /etc/sddm/Xstop
to run the following command when the X server stops:
killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry
evolution-calendar-factory-subprocess evolution-addressbook-factory
evolution-addressbook-factory-subprocess at-spi2-registryd
at-spi-bus-launcher
I'm not sure which of the processes is responsible, since all of them still exist when Xstop
runs. If I narrow things down I'll update this answer.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Looks like the problem is that some user session daemon isn't quitting when the session is over. Since I use SDDM I fixed the problem by editing /etc/sddm/Xstop
to run the following command when the X server stops:
killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry
evolution-calendar-factory-subprocess evolution-addressbook-factory
evolution-addressbook-factory-subprocess at-spi2-registryd
at-spi-bus-launcher
I'm not sure which of the processes is responsible, since all of them still exist when Xstop
runs. If I narrow things down I'll update this answer.
add a comment |Â
up vote
0
down vote
accepted
Looks like the problem is that some user session daemon isn't quitting when the session is over. Since I use SDDM I fixed the problem by editing /etc/sddm/Xstop
to run the following command when the X server stops:
killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry
evolution-calendar-factory-subprocess evolution-addressbook-factory
evolution-addressbook-factory-subprocess at-spi2-registryd
at-spi-bus-launcher
I'm not sure which of the processes is responsible, since all of them still exist when Xstop
runs. If I narrow things down I'll update this answer.
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Looks like the problem is that some user session daemon isn't quitting when the session is over. Since I use SDDM I fixed the problem by editing /etc/sddm/Xstop
to run the following command when the X server stops:
killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry
evolution-calendar-factory-subprocess evolution-addressbook-factory
evolution-addressbook-factory-subprocess at-spi2-registryd
at-spi-bus-launcher
I'm not sure which of the processes is responsible, since all of them still exist when Xstop
runs. If I narrow things down I'll update this answer.
Looks like the problem is that some user session daemon isn't quitting when the session is over. Since I use SDDM I fixed the problem by editing /etc/sddm/Xstop
to run the following command when the X server stops:
killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry
evolution-calendar-factory-subprocess evolution-addressbook-factory
evolution-addressbook-factory-subprocess at-spi2-registryd
at-spi-bus-launcher
I'm not sure which of the processes is responsible, since all of them still exist when Xstop
runs. If I narrow things down I'll update this answer.
answered Aug 26 at 3:00
Matthew Cline
1,24011021
1,24011021
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f464535%2fevolution-gets-d-bus-error-when-trying-to-send-from-alias-account%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
â slmâ¦
Aug 24 at 1:34