After looking through the environment variables that are set between cases that are working and that aren't working, I found that DCONF_PROFILE=custom is being set in the case that is not working. Of course, there is no custom dconf profile inside of the Puritine chroot.
As a further test for my theory, I did "DCONF_PROFILE=custom gedit" on my normal Ubuntu machine and lo and behold, I could not type into the Gedit window just like on the Frieza.
I'm not really sure why DCONF_PROFILE=custom is being set on Frieza which should probably be investigated. I can also explicitly unset DCONF_PROFILE when launching apps in Puritine and in Libertine containers in general.
After looking through the environment variables that are set between cases that are working and that aren't working, I found that DCONF_PROFILE= custom is being set in the case that is not working. Of course, there is no custom dconf profile inside of the Puritine chroot.
As a further test for my theory, I did "DCONF_ PROFILE= custom gedit" on my normal Ubuntu machine and lo and behold, I could not type into the Gedit window just like on the Frieza.
I'm not really sure why DCONF_PROFILE= custom is being set on Frieza which should probably be investigated. I can also explicitly unset DCONF_PROFILE when launching apps in Puritine and in Libertine containers in general.