1976381 - Firefox 142.0a1 20250708210138 didn't appear when starting with my profile

Status: RESOLVED FIXED

(Core :: Widget: Gtk, defect, P3)

Description

[Matt Fagnani]

Steps to reproduce:

I ran Firefox 142.0a1 20250708092136 on Wayland in Plasma 6.4.2 in a Fedora 42 KDE installation. I selected Help then About Nightly. I selected Update to Firefox 142.0a1 (2025-07-08) then selected restart to update.

Actual results:

Firefox 142.0a1 20250708210138 didn't appear when starting with my profile. Only two content processes started instead of the usual eight as shown in the following.

ps aux | grep firefox
matt 36371 11.3 4.0 11669264 309112 ? Sl 20:46 0:03 /home/matt/programs/firefox/firefox-bin
matt 36391 0.0 0.0 55884 7168 ? Sl 20:46 0:00 /home/matt/programs/firefox/crashhelper 36371 17 /tmp/ 18 20
matt 36469 0.2 0.6 272640 47840 ? Sl 20:46 0:00 /home/matt/programs/firefox/firefox-bin -contentproc -parentBuildID 20250708210138 -prefsHandle 0:40108 -prefMapHandle 1:281792 -sandboxReporter 2 -chrootClient 3 -ipcHandle 4 -initialChannelId {07941d36-2eb7-48eb-bf44-7b4a2dda8582} -parentPid 36371 -crashReporter 5 -crashHelper 6 -appDir /home/matt/programs/firefox/browser 1 socket
matt 36492 0.1 0.4 341340 30688 ? S 20:46 0:00 /home/matt/programs/firefox/firefox-bin -contentproc -ipcHandle 0 -signalPipe 1 -initialChannelId {4761fbf9-a1d4-4119-bed6-3808d63087ab} -parentPid 36371 -greomni /home/matt/programs/firefox/omni.ja -appomni /home/matt/programs/firefox/browser/omni.ja -appDir /home/matt/programs/firefox/browser 2 forkserver
matt 36600 0.0 0.0 231256 2344 pts/1 S+ 20:47 0:00 grep --color=auto firefox

I created a new profile, and 142.0a1 20250708210138 started normally with that profile.
This problem appears like that of Bug 1971638.

I bisected between 20250708092136 and 20250708210138 with my profile. The three first changes in the pushlog were Bug 1971161.

5:22.99 INFO: Narrowed integration regression window from [78431d6c, f562693b] (4 builds) to [fa99e2e2, f562693b] (2 builds) (~1 steps left)
5:22.99 INFO: No more integration revisions, bisection finished.
5:22.99 INFO: Last good revision: fa99e2e2b957d91bf31e2237b2db945d600de169
5:22.99 INFO: First bad revision: f562693b5b30344af6419b1668bcbcf3a804daba
5:22.99 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=fa99e2e2b957d91bf31e2237b2db945d600de169&tochange=f562693b5b30344af6419b1668bcbcf3a804daba

I also bisected Bug 1971638 to Bug 1971161. Bug 1971161 was fixed by reverting [Wayland] Get HDR monitor info async 49407f49202c1488708a554d528feccf4a3f85a0

Expected results:

Firefox 142.0a1 20250708092136 should've started normally with my profile.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:stransky, since you are the author of the regressor, bug 1971161, could you take a look?

For more information, please visit BugBot documentation.

Comment 2

[Matt Fagnani]

Attachment: MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 output when Firefox 142.0a1 20250708210138 didn't appear

I'm attaching MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 output when Firefox 142.0a1 20250708210138 didn't appear. I aborted the parent process with kill -6 and submitted the crash as https://crash-stats.mozilla.org/report/index/ad9854ea-8adc-48f5-bad8-7a0340250709

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Attachment: Bug 1976381 [Wayland] Set screens early without HDR info r?emilio

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1971161

Comment 5

[Paul Menzel]

I hat the same issue on Debian sid/unstable with firefox-nightly.

$ mozregression --good 20250706213835 --bad 20250709093153 -p /home/pmenzel/.mozilla/firefox/XXXXXXX.default
[…]
 3:58.49 INFO: No more integration revisions, bisection finished.
 3:58.49 INFO: Last good revision: fa99e2e2b957d91bf31e2237b2db945d600de169
 3:58.49 INFO: First bad revision: f562693b5b30344af6419b1668bcbcf3a804daba
 3:58.49 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=fa99e2e2b957d91bf31e2237b2db945d600de169&tochange=f562693b5b30344af6419b1668bcbcf3a804daba

Comment 6

[Manuel Bucher [:manuel]]

Workaround from emilio in Bug 1976461 comment 1:

1. ./firefox --jsconsole
2. SessionStore.getWindows().forEach(w => w.focus())

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/3921362b6aa3
https://hg.mozilla.org/integration/autoland/rev/7c5cd16fb013
[Wayland] Set screens early without HDR info r=emilio

Comment 8

[Matt Fagnani]

I used ./firefox --jsconsole. I only saw the filter output box to enter text in the console so I'm not sure where to put SessionStore.getWindows().forEach(w => w.focus()). After I closed the console, then started 142.0a1 20250709093153 with my profile, Firefox appeared after that within the same session. When I logged out of Plasma then logged back in, the problem happened again. Sometimes after that though there were error messages that Firefox didn't start properly, and it gave the option of starting in safe mode. Firefox appeared in safe mode. Also, the about:support fields were all empty sometimes when I used my profile, but not with a new profile.

I noticed in my MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 output that HDR 1 near the end in D/WidgetScreen New monitor 0 size [0,0 -> 1366 x 768] depth 24 scale 1.000000 CssScale 1.000000 DPI 101.073570 refresh 60 HDR 1]. My screen doesn't support HDR. Hopefully Martin's patch will fix the problem. Thanks.

Comment 9

[Martin Stránský [:stransky] (ni? me)]

(In reply to Matt Fagnani from comment #8)

I noticed in my MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 output that HDR 1 near the end in D/WidgetScreen New monitor 0 size [0,0 -> 1366 x 768] depth 24 scale 1.000000 CssScale 1.000000 DPI 101.073570 refresh 60 HDR 1]. My screen doesn't support HDR. Hopefully Martin's patch will fix the problem. Thanks.

But from the Wayland log it claims HDR support (max luminance is bigger than reference one).

Comment 10

[Matt Fagnani]

Attachment: MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 output with 142.0a1 20250709093153 in GNOME

Thanks. In Plasma System Settings, the Display Configuration screen shows Extended Dynamic Range: Enable EDR is selected which has the tooltip "EDR allows viewing HDR content on SDR displays by dynamically adjusting the backlight. Note that this increases battery usage while viewing HDR content." Could EDR being enabled account for what you mentioned?

In GNOME 48.2 in the Settings, the Displays screen doesn't show an HDR option on my system. When I ran with MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 with 142.0a1 20250709093153 in GNOME, the problem happened. HDR 0 was shown and the max and reference luminances were 80.

[Parent 44047: Main Thread]: D/WidgetScreen WaylandMonitor() [7f8cfd8a8790] num [0] Luminance min 2000 max 80 reference 80
[1777354.416] {Default Queue} wp_image_description_info_v1#63.done()
[Parent 44047: Main Thread]: D/WidgetScreen WaylandMonitor() [7f8cfd8a8790] image_description_info_done monitor 0
[Parent 44047: Main Thread]: D/WidgetScreen WaylandMonitor()[7f8cfd8a8790] ImageDescriptionDone
[Parent 44047: Main Thread]: D/WidgetScreen New monitor 0 size [0,0 -> 1366 x 768] depth 24 scale 1.000000 CssScale 1.000000 DPI 102.669472 refresh 60 HDR 0]

I'm attaching the full output with MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 in GNOME.

When I ran firefox --jsconsole in Plasma then closed the console, 142.0a1 20250709093153 remained running in the background with two content processes. I started 142.0a1 20250709093153 with my profile, and after Firefox appeared still just two content processes were running.

Comment 11

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/7c5cd16fb013

Comment 12

[Matt Fagnani]

142.0a1 20250709215737 didn't have this problem. Thanks. When I ran it with MOZ_LOG="WidgetScreen:5" WAYLAND_DEBUG=1 in Plasma, HDR was 0 and the max and reference luminances were both 200.

[Parent 74381: Main Thread]: D/WidgetScreen WaylandMonitor() [7f1b2ece8190] num [0] Luminance min 100 max 200 reference 200
...
[Parent 74381: Main Thread]: D/WidgetScreen New monitor 0 size [0,0 -> 1366 x 768] depth 24 scale 1.000000 CssScale 1.000000 DPI 101.073570 refresh 60 HDR 0]

Comment 13

[Manuel Bucher [:manuel]]

(In reply to Matt Fagnani from comment #8)

I used ./firefox --jsconsole. I only saw the filter output box to enter text in the console so I'm not sure where to put SessionStore.getWindows().forEach(w => w.focus()).

Sorry, forgot that it is necessary to enable the JS prompt https://firefox-source-docs.mozilla.org/devtools-user/browser_console/:

NB: The Browser Console command line (to execute JavaScript expressions) is disabled by default. To enable it set the devtools.chrome.enabled preference to true in about:config, or set the “Enable browser chrome and add-on debugging toolboxes” (Firefox 40 and later) option in the developer tool settings.