One new clue, earlier in the log: there's a step where we run `Running command: pactl list modules short` which lists a bunch of modules. On "good" runs (where Firefox ends up automatically using Adwaita), that list has this at the end -- notably including some display/x11-related stuff: ``` [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 24 module-filter-apply [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 25 module-x11-publish display=:0 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 26 module-x11-bell display=:0 sample=bell.ogg [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 27 module-x11-cork-request display=:0 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 28 module-x11-xsmp display=:0 session_manager=local/cc34549f0870:@/tmp/.ICE-unix/58,unix/cc34549f0870:/tmp/.ICE-unix/58 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 29 module-null-sink ``` source: https://firefoxci.taskcluster-artifacts.net/TuF1Oh7PSuWVljIrfejJYA/0/public/logs/live_backing.log Whereas on "bad" runs (where we end up with Ambiance & test failures), that list ends doesn't have the X11 entries and instead just ends like this: ``` [task 2024-05-05T03:02:21.120Z] 03:02:21 INFO - 24 module-filter-apply [task 2024-05-05T03:02:21.120Z] 03:02:21 INFO - 25 module-null-sink ``` Source: https://firefoxci.taskcluster-artifacts.net/MsmS-9LiSmGJt1PYFSTx6g/0/public/logs/live_backing.log Aside form those module-x11-* entries, the list is otherwise the same. So it looks like some X11 modules aren't getting loaded, or something, and so maybe we're rendering with a nerfed display in the bad runs, in some sense?
Bug 1895092 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
One new clue, earlier in the log: there's a step where we run `Running command: pactl list modules short` which lists a bunch of modules. On "good" runs (where Firefox ends up automatically using Adwaita), that list has this at the end -- notably including some display/x11-related stuff: ``` [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 24 module-filter-apply [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 25 module-x11-publish display=:0 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 26 module-x11-bell display=:0 sample=bell.ogg [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 27 module-x11-cork-request display=:0 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 28 module-x11-xsmp display=:0 session_manager=local/cc34549f0870:@/tmp/.ICE-unix/58,unix/cc34549f0870:/tmp/.ICE-unix/58 [task 2024-05-04T23:20:59.177Z] 23:20:59 INFO - 29 module-null-sink ``` source: https://firefoxci.taskcluster-artifacts.net/TuF1Oh7PSuWVljIrfejJYA/0/public/logs/live_backing.log Whereas on "bad" runs (where we end up with Ambiance & test failures), that list ends doesn't have the X11 entries and instead just ends like this: ``` [task 2024-05-05T03:02:21.120Z] 03:02:21 INFO - 24 module-filter-apply [task 2024-05-05T03:02:21.120Z] 03:02:21 INFO - 25 module-null-sink ``` Source: https://firefoxci.taskcluster-artifacts.net/MsmS-9LiSmGJt1PYFSTx6g/0/public/logs/live_backing.log Aside from those module-x11-* entries, the list is otherwise the same. So it looks like some X11 modules aren't getting loaded, or something, and so maybe we're rendering with a nerfed display in the bad runs, in some sense?