K, this will be fixed in the next release. I just fixed it in the branch.
I just saw your change here: https://github.com/openmv/qt-creator/blob/openmv/bin/openmvide.sh
You should explicitly specify /bin/bash as the shell to be use. /bin/sh is a symlink in most distribution and in Debian-based ones, it’s pointing to /bin/dash.
dash doesn’t use ~/.bashrc.
Since you are using ~/.bashrc in here: https://github.com/openmv/openmv-ide/blob/master/make.py#L169, it won’t work.
Most shells will use ~/.profile as the login source file. It’s actually the file that sources ~/.bashrc but only when /bin/bash is used:
root@raspberrypi:~# cat .profile
# ~/.profile: executed by Bourne-compatible login shells.
if [ "$BASH" ]; then
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
fi
mesg n || true
root@raspberrypi:~# echo $BASH
/bin/bash
root@raspberrypi:~# /bin/sh
# echo $BASH
#
If you want to make sure the export QT_QPA_PLATFORM=xcb is always ran, you should append it to ~/.profile instead of ~/.bashrc.
But, since in your context, bash should be used, forcing #/bin/bash -i as the shebang of the openmvide.sh shall be preferred.
Explanation: command line - Why .profile (and not .bashrc) appends ~/bin to path? - Ask Ubuntu
Okay, updated that. Please send a PR for any more fixes you think would be good. Thanks for your help.
In my case, turning off the Overscan in Raspberry Pi Display Configuration solved the problem.