isync reports "Success" error but doesn't sync files

Bug #1895356 reported by Aaron Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
isync (Ubuntu)
New
Undecided
Unassigned

Bug Description

On Ubuntu 20.04.1 LTS, running 'mbsync work' with the attached skeleton .mbsyncrc file returns the output:

C: 0/1 B: 0/0 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0
Socket error: secure connect to outlook.office365.com (52.96.79.2:993): Success
C: 1/1 B: 0/0 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0

The output I am expecting, and the output I get under Ubuntu 18.04.5 LTS is,

C: 0/1 B: 0/0 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0 Skipping account work-remote, no user C: 1/1 B: 0/0 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0

If I replace the skeleton .mbsyncrc file with a full version that has username and password information, then on 20.04 I get the same output as above and no files are transferred, whereas on 18.04 it successfully transfers the files.

Package version:

abw35@surface:~$ apt-cache policy isync isync: Installed: 1.3.0-2 Candidate: 1.3.0-2 Version table: *** 1.3.0-2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status

FWIW, I am running both 20.04 and 18.04 under WSL. I originally submitted a bug report to WSL, but the response was that this was unlikely to be related to WSL itself.

Revision history for this message
Aaron Wagner (baron77) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.