-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.4.z
-
Yes
-
Moderate
-
rhel-se-display
-
ssg_display
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Running dconf update results in a nondeterministic /etc/dconf/db/site file. e.g.
$ a=$(sudo dconf update && hexdump -C /etc/dconf/db/site)
$ b=$(sudo dconf update && hexdump -C /etc/dconf/db/site)
$ sdiff -w200 <(echo "$a") <(echo "$b")
00000000 47 56 61 72 69 61 6e 74 00 00 00 00 00 00 00 00 |GVariant........| 00000000 47 56 61 72 69 61 6e 74 00 00 00 00 00 00 00 00 |GVariant........|
00000010 18 00 00 00 58 00 00 00 00 00 00 28 02 00 00 00 |....X......(....| 00000010 18 00 00 00 58 00 00 00 00 00 00 28 02 00 00 00 |....X......(....|
00000020 00 00 00 00 01 00 00 00 d4 b5 02 00 ff ff ff ff |................| 00000020 00 00 00 00 01 00 00 00 d4 b5 02 00 ff ff ff ff |................|
00000030 58 00 00 00 01 00 00 00 c0 c8 2f 82 00 00 00 00 |X........./.....| | 00000030 58 00 00 00 01 00 00 00 c0 e8 02 27 00 00 00 00 |X..........'....|
00000040 8f 39 0d 7b ff ff ff ff 59 00 00 00 06 00 48 00 |.9.{....Y.....H.| 00000040 8f 39 0d 7b ff ff ff ff 59 00 00 00 06 00 48 00 |.9.{....Y.....H.|
00000050 60 00 00 00 68 00 00 00 2f 2e 6c 6f 63 6b 73 00 |`...h.../.locks.| 00000050 60 00 00 00 68 00 00 00 2f 2e 6c 6f 63 6b 73 00 |`...h.../.locks.|
00000060 00 00 00 28 00 00 00 00 |...(....| 00000060 00 00 00 28 00 00 00 00 |...(....|
00000068 00000068
This is with dconf-0.40.0-6.el9.x86_64. On RHEL 8 with dconf-0.28.0-4.el8.x86_64, the varying bytes are always zero:
$ a=$(sudo dconf update && hexdump -C /etc/dconf/db/site)
$ b=$(sudo dconf update && hexdump -C /etc/dconf/db/site)
$ sdiff -w200 <(echo "$a") <(echo "$b")
00000000 47 56 61 72 69 61 6e 74 00 00 00 00 00 00 00 00 |GVariant........| 00000000 47 56 61 72 69 61 6e 74 00 00 00 00 00 00 00 00 |GVariant........|
00000010 18 00 00 00 58 00 00 00 00 00 00 28 02 00 00 00 |....X......(....| 00000010 18 00 00 00 58 00 00 00 00 00 00 28 02 00 00 00 |....X......(....|
00000020 00 00 00 00 01 00 00 00 d4 b5 02 00 ff ff ff ff |................| 00000020 00 00 00 00 01 00 00 00 d4 b5 02 00 ff ff ff ff |................|
00000030 58 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 |X...............| 00000030 58 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 |X...............|
00000040 8f 39 0d 7b ff ff ff ff 59 00 00 00 06 00 48 00 |.9.{....Y.....H.| 00000040 8f 39 0d 7b ff ff ff ff 59 00 00 00 06 00 48 00 |.9.{....Y.....H.|
00000050 60 00 00 00 68 00 00 00 2f 2e 6c 6f 63 6b 73 00 |`...h.../.locks.| 00000050 60 00 00 00 68 00 00 00 2f 2e 6c 6f 63 6b 73 00 |`...h.../.locks.|
00000060 00 00 00 28 00 00 00 00 |...(....| 00000060 00 00 00 28 00 00 00 00 |...(....|
00000068 00000068
Running under faketime does not help, so this does not seem to be timestamp-related. This non-reproducibility makes our lorax-based installation ISOs also non-reproducible, since Anaconda installs dconf which runs dconf update in its posttrans.
