Bug 977973

Created attachment 765210 [details]
screenshot

Created attachment 765211 [details]
console output

Thanks for a bug report. I see most of the processes idle, the only working is evolution (asking for a password of your ews account), the other one is the calendar factory, asking for a password of a CalDAV calendar. None of these is shown in the source registry process.

From the console output, it seems you get an Unauthorised response from the server, your stored password is probably wrong. I would reenter the password in Online Accounts, to make it work again. The error is:

> ** (evolution:2676): WARNING **: Failed to obtain an access token for
> 'user': GDBus.Error:org.gnome.OnlineAccounts.Error.NotAuthorized:
> Invalid password with username `user' (goa-error-quark, 0): Code:
> 401 - Unexpected response from server

Though it's for your GMail account. The EWS account seems to suffer of a connection issue, at least according to:
> No response: Connection terminated unexpectedly

I suppose once the server will start responding properly, can be cause by any server between you and the destination exchange server, then the issue will be fixed on its own.

GMail account not work because Online Accounts not support 2 step authentication for Google accounts. I filled bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=971607

But not any answer :(

Created attachment 767211 [details]
yet another backtrace of evolution when it stuck again

Backtraces show exactly the same thing as before (from comment #3):
> I see most of the processes idle, the only working
> is evolution (asking for a password of your ews account), the other one is
> the calendar factory, asking for a password of a CalDAV calendar. None of
> these is shown in the source registry process.

*** Bug 980248 has been marked as a duplicate of this bug. ***

Created attachment 772404 [details]
yet another backtrace of evolution when it stuck again

Still the same issue. I think there is no reproducer except of two-factor authentication for Google in use? Could you disable the Google account in Gnome Online Accounts, if you do not have yet, please?

I am has disabled the Google account in Gnome Online Accounts. But today evolution hang again. Seems this is relate with network problems.

Created attachment 778341 [details]
new backtraces of evolution when it stuck again

The evolution and evolution-alarm-notify "backtraces" claim that the executable was deleted, from which I suppose you updated the package(s). I would try to restart the machine, to get all the new packages in action.

Created attachment 781411 [details]
new backtraces of evolution when it stuck again

$ evolution
Created new window in existing browser session.

(evolution:2402): evolution-mail-WARNING **: Failed to refresh folder 'm.gavrilov: Inbox': The specified object was not found in the store.
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
DWPBase: /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin
Created new window in existing browser session.
Created new window in existing browser session.

(evolution:2402): evolution-mail-WARNING **: Failed to refresh folder 'm.gavrilov: Inbox': No response: Connection terminated unexpectedly

(In reply to Mikhail from comment #13)
> Created attachment 781411 [details]
> new backtraces of evolution when it stuck again

The content is almost the same as in comment #11. Is it possible you didn't restart the machine since you updated evolution packages the last time? The machine restart it better to make sure all the updated binaries will reload their newer versions.

(In reply to Mikhail from comment #14)
> $ evolution
> Created new window in existing browser session.
>
>...
>
> DWPBase:
> /home/mikhail/.config/libreoffice/4/user/uno_packages/cache/uno_packages/
> luq0mqw6.tmp_/orfo4ooo-linux.oxt/base/../base/DWPBase.bin

The above are new to me, I didn't see it myself yet. Could they come from libreoffice, which you've run on the same terminal? Or maybe a browser plugin from libreoffice is printing this, and is loaded together with Webkit in evolution.

> (evolution:2402): evolution-mail-WARNING **: Failed to refresh folder
> 'm.gavrilov: Inbox': The specified object was not found in the
> store.
> 
> ...
>
> (evolution:2402): evolution-mail-WARNING **: Failed to refresh folder
> 'm.gavrilov: Inbox': No response: Connection terminated
> unexpectedly

I guess the second is caused by the first. I guess there was some issues with connection to your server. Maybe your IT were updating it or something.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.