I have tried to read around this insignificant little detail but have no answer.
/var/lib/dbus/machine-id
While building gksu from AUR and try to run it on my latest (of three) installation of obarun (using the last 2018 installer) I run into an error/warning of not having a /var/lib/dbus/machine-id
So I run uuidgen, got an id and put it in a file in that position. Initially I thought it was the partition's UUID which is 36 characters but this id must be 32.
I checked on all my other installations, debian based, arch based, void, alpine, and they all had this file with the uuid in it, except for this installation (I think it was made the day the last installer was revised).
So I don't understand now which process creates it and why did this installation not have one.
GConf Error: Client failed to connect to the D-BUS daemon:
D-Bus library appears to be incorrectly set up: see the manual page for dbus-uuidgen to correct this issue. (Failed to open "/var/lib/dbus/machine-id": No such file or directory; Failed to open "/etc/machine-id": No such file or directory)
I think if you rename the file and run gksu/gksudo you may see the same error. In this 2nd case I added 4 0s at the beginning of the uuid to get the error.
D-Bus library appears to be incorrectly set up: see the manual page for dbus-uuidgen to correct this issue. (UUID file '/var/lib/dbus/machine-id' should contain a hex string of length 32, not length 36, with no other text; Failed to open "/etc/machine-id": No such file or directory)
So why did D-bus library not correctly been set-up?