Closed issue by reedts on void-packages repository

https://github.com/void-linux/void-packages/issues/33876

Description:
While investigating some strange problems on xsession startup using lightdm + i3, I found this line in `/etc/lightdm/Xsession` and was wondering whether the `-nocpp` option is used here for a specific reason: [see here](https://github.com/void-linux/void-packages/blob/a279abf769ef7cab6ebb49d8c99bf774a2ff97b8/srcpkgs/lightdm/files/xsession#L19)

As an example from the archlinux package sources for lightdm: they're omitting the `-nocpp` option (see [here](https://github.com/archlinux/svntogit-packages/blob/8d85fa6b8d07e4a82b24efc7635853110c2f93ed/trunk/Xsession#L19))

Furthermore, having a look at xrdb's source code, you can see [here](https://gitlab.freedesktop.org/xorg/app/xrdb/-/blob/master/xrdb.c#L917) that xrdb should correctly check for the existence of the default cpp preprocessor (`/usr/lib/cpp`) and automatically disables preprocessing of `.Xresources` if the binary cannot be found.

So, in my opinion it should be safe omitting `-noccp` in the global `/etc/lightdm/Xsession` script and would simultaneously allow the user to have their `.Xresources` preprocessed on session-startup if a preprocessor can be found.