Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50612 - [gnome-online-accounts] empathy can't connect to goa-daemon
Attached to Project:
Arch Linux
Opened by Johannes Rohr (jro) - Wednesday, 31 August 2016, 10:51 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 31 August 2016, 12:40 GMT
Opened by Johannes Rohr (jro) - Wednesday, 31 August 2016, 10:51 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 31 August 2016, 12:40 GMT
|
DetailsDescription:
Fortunately, issue #50589 has been fixed, reducing the memory usage of goa-daemon considerably, however this seems to have cause issues with empathy. Firing up empathy I see that all chat accounts are gone and an alert shows the message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Comment by Johannes Rohr (jro) -
Wednesday, 31 August 2016, 11:45 GMT
seems to have been a transient issue. After a reboot, things have been working fine.