Steps to reproduce:
Details:
From what I gather the issue comes down to save_cursor_theme_name function being invoked twice in lxappearance_save_gtkrc - first when generating settings for gtk2, and second time when generating settings for gtk3. The flow goes rougly like this:
save_cursor_theme_name.save_cursor_theme_name.This is problematic as save_cursor_theme_name may have the side effect of unsetting cursor_name field of the global app struct. In particular for a theme like "redglass" that doesn't provide an "index.theme" file it will consider it invalid and thus unset the field. So the value of app.cursor_theme will make its way into gtk2 settings but will no longer be present when generating gtk3 settings to a prior call to save_cursor_theme_name.
I shall note that the theme works perfectly fine in both gtk2 and gtk3 applications.
A simple work around would be to invoke save_cursor_theme_name only once after both gtk2 and gtk3 settings have been saved, or perhaps adjust the validation logic as the particular theme in question would appear to be working fine.
Please let me know if you require any additional details.
Thank you.