You may need to remove the i386 packages first:
sudo apt remove --purge `dpkg --get-selections | awk '/i386/{print $1}'`

Then remove the architecture
sudo dpkg --remove-architecture i386

The above process worked for me. I just tried it.

Don't hold you breath. I had a lot that after +20h of runtime got the mere default of 37.1 (31.7?) points, less than WUs running for 1.5-2.5h got...

Ralf

On further investigation it would seem that the memory requirements are higher, at least on Androids than they were on the previous non beta units. I was able to run 4 units with no problems on my 4 core Androids with 4gb of memory but now I can only run 2 or 3 at the most due to constant restarting of the units.

Pete

I run (and have run on a lot of devices) pure 64bit Debian for WCG machines and all work is 64bit for the same projects as you've outlined - I'm actually more surprised your device is requesting and running 32bit work units instead of 64bit ones. Obviously something within the BOINC ecosphere is requesting them, how else right? By any chance, do you accidentally have the 32bit version of `boinc-client` installed, not the 64bit one? Run "dpkg -l | grep boinc" and look at the 4th column, should be "amd64".

Anyways, you should have zero problems running without the 32bit subsystem installed. You'll probably see a slight performance increase in some places as it avoids some shims in the kernel (basically, a 32bit userland app running in 64bit kernel has to go through some processing, you're removing that need), but a slight increase in RAM usage in others (it's really dependent on the exact code and what data structures it uses). Google: "32 bit vs 64 bit memory consumption"

I'm glad you posted this, Doneske, as it likely explains why I can't see the graphics on my 64-bit Ubuntu machine. I had only vaguely wondered why as I'm not very interested. However, I do think that this justifies posting in its own thread or, better still, a tech note from the techs in the help area.