Evolution gets D-Bus error when trying to send from alias account

The name of the pictureThe name of the pictureThe name of the pictureClash 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.










share|improve this question























  • Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
    – slm♦
    Aug 24 at 1:34














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.










share|improve this question























  • Sounds related - bugzilla.redhat.com/show_bug.cgi?id=1382879. Specifically the bit about the keyring daemon.
    – slm♦
    Aug 24 at 1:34












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.










share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








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
















  • 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










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.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    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






























    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.






    share|improve this answer
























      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.






      share|improve this answer






















        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.






        share|improve 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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 26 at 3:00









        Matthew Cline

        1,24011021




        1,24011021



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            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













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?