https://bugs.freedesktop.org/show_bug.cgi?id=60333
Patrick Ohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Patrick Ohly <[email protected]> --- Included in master branch. This took a bit longer than expected, because I had to modify the nightly testing to start activesyncd for the configure operation (wasn't necessary before). Error reporting in core SyncEvolution was insufficient, so I enhanced that: commit e05454d56334eef225fbff02f382adf9cbdc30fd Author: Patrick Ohly <[email protected]> Date: Wed Feb 27 06:10:22 2013 -0800 command line: show backend error when listing databases fails The command line swallowed errors thrown by the backend while listing databases. Instead it just showed "<backend name>: backend failed". The goal was to not distract users who accidentally access a non-functional backend. But the result is that operations like --configure or --print-databases could fail without giving the user any hint about the root cause of the issue. Now the error explanation in all its gory details is included. For example, not having activesyncd running leads to: INFO] eas_contact: backend failed: fetching folder list: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.meego.activesyncd was not provided by any .service files And running activesyncd without the necessary gconf keys shows up as: [INFO] eas_contact: backend failed: fetching folder list: GDBus.Error:org.meego.activesyncd.Error.AccountNotFound: Failed to find account [[email protected]] Both of these happened when trying to use the "list database" ActiveSync patches in the nightly test setup... -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
