@algorithman-de said in How to deactivate desktop opengl option:
This topic is quite old, but I think it needs more discussion, because as far as I can tell, the answers here don't work anymore.
The problem is that keyboards and SSH are deactivated by default (maybe that was different 2 years ago?), so without the graphics mode, BASH and raspi-config are inaccessible. You can't access the option to turn OpenGL off again, you can't install or activate a desktop. In other words, turning OpenGL on bricks the device.
you can turn on SSH without a keyboard/graphics. see step 3: https://www.raspberrypi.org/documentation/remote-access/ssh/
I tried mounting the SD-card in a PC card-reader, went to the boot-partition, edited the file config.txt and commented out the line
That at least brought back some graphics mode, but I only got an EmulationStation without background and a dysfunctional menu with only empty lines. Maybe someone could mention WHICH setting to change in the config, instead of just telling us to "find the setting". But even if that works - that is still way to complicated to be an acceptable answer.
At that point I had given up and flashed my SD-Card anew. Luckily, my installation was quite new anyways and I hadn't configured much - otherwise that "solution" would also have been unacceptable.
AFAIK, RetroPie strives for user friendliness - that means having an intuitive UI. An option that sounds great, but that does such damage, is not intuitive - especially if that option is accessible that easily (it is very far up in the menu-tree). I'm using OpenGL in my Raspbian installation where it works well, so I didn't see any reason not to turn it on. The fact that OpenGL only works in a desktop environment and RetroPie runs without a desktop environment, is a very technical detail you can't expect a casual user to know. Even as a graduate computer scientist, I fell for this.
In github issue #1392, @herb_fargus has explained that raspi-config comes from raspbian, not from RetroPie (I knew that before I had asked). Nevertheless, "So sorry, we can't really do anything about this" is just a cheap excuse. You do your own build of Raspbian, so you could run a patch over the raspi-config source code as part of your toolchain. You could provide and preinstall a package with a modified raspi-config (say retropie-config) instead of raspi-config. You could upstream a fix that allows to deactivate the option via command line (or other means). You could also have a startup script that changes the config.txt to turn off OpenGL if it is turned on.
There are things you could do about it and if you want to provide a user friendly UI as you claim, you can't hide behind such cheap excuses.
what's all this "you" business? retropie is a volunteer project. you should replace all "you"/"your" with "I"/"my"....
the bottom line is that you turned on a raspbian feature without knowing what it did. there's lots of fun and exciting ways you can break a linux installation.