I realize that CentOS Linux is not a supported platform, but I’m wondering if you have any tips for debugging a completely blank white screen.
Basically on startup, the Everdo window is completely white, and none of the UI elements are drawn. I’ve tried initially, and with a blank ~/.config/everdo folder. This behavior does not happen in Chrome/Chromium.
Hey! Try sending me the log file located at ~./config/everdo/ after the white screen accident.
.log extension
Blank screen means a critical error at startup and it should appear in logs.
I have the same issue on Centos, but there is no log file in .config/everdo
I see. I’m gonna try it myself just need to make a CentOS VM.
Yep same thing happens when I try it. The cause:
/lib64/libstdc++.so.6: version 'GLIBCXX_3.4.21' not found
Couldn’t find a solution so far.
strings /usr/lib/libstdc++.so.6 | grep GLIBC
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBC_2.3
GLIBC_2.0
GLIBC_2.4
GLIBC_2.1
GLIBC_2.1.3
GLIBC_2.3.2
GLIBC_2.2
GLIBCXX_DEBUG_MESSAGE_LENGTH
I guess time to try a different build machine.
The bug is caused by using a “too new” version of GCC. For reference, see here: Desktop Linux Platform Issues · AppImage/AppImageKit Wiki · GitHub
Possible solutions are bundling the libstdc++.so of the build host and load it if needed (But which could cause security problems!) or building on a CentOS target. The latter is more or less equivalent to support CentOS / providing packages for it.
Hope this helps a bit 
This is very helpful, thank you! Building on CentOS does work.
Since today’s release, the AppImage and RPM packages are being built on a different machine, which should make this issue go away.
Thank you - works on here now on Centos 7 running MATE desktop.