[Ubuntu 24.04LTS GNOME 46] Window renders transparent with hall of mirrors effect after toggling titlebar
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox146 | --- | unaffected |
| firefox147 | --- | wontfix |
| firefox148 | --- | wontfix |
People
(Reporter: mboldan, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Found in
- Firefox 147.0b1
Affected versions
- Firefox 147.0b1
- Firefox 148.0a1
Tested platforms
- Affected platforms: Ubuntu 22, Ubuntu 24
- Unaffected platforms: macOS 10.15, Windows 10x64, Windows 11x64
Steps to reproduce
- Open the application menu (hamburger menu) -> select "More Tools" -> "Customize Toolbar...".
- From the bottom of the page activate the "Title Bar".
Expected result
- Title Bar is enabled.
Actual result
- Firefox windows disappears and gets unresponsive. See the attached video.
Regression range
- Will search for a regression asap.
Additional notes
- Note that the issue is not reproducible on Firefox 146 RC.
- Note that the issue was reproducible only with Window Protocol - 'wayland'.
- Note that on one try, the FF behavior closed all other opened apps. This was reproduced only once.
| Reporter | ||
Updated•5 months ago
|
| Reporter | ||
Updated•5 months ago
|
Comment 1•5 months ago
|
||
Hi, mboldan - you mentioned crashes as well. Do you have any crash reports you can attach here?
Comment 2•5 months ago
|
||
Please attach your about:support page and make the video public.
Thanks.
| Reporter | ||
Comment 3•5 months ago
|
||
I managed to make the video public.
Note that no crash report is available.
I am attaching a screenshot of the errors from browser console. Please let me know if I can help with any other information.
Note that the issue was reproducible om multiple workstations.
| Reporter | ||
Comment 4•5 months ago
•
|
||
The about:support page is not accesible after following the STR as it can be seen in the attached screencast.
Comment 5•5 months ago
|
||
Please run on terminal with MOZ_LOG="Widget:5" env variable, reproduce the issue and attach the log here.
Make sure you're running latest nightly.
Run on terminal as:
MOZ_LOG="Widget:5" ./firefox > log.txt 2>&1
and attach the log here.
Thanks.
| Reporter | ||
Comment 6•5 months ago
|
||
Attached the log file. Thank you for the steps!
Comment 7•5 months ago
|
||
Please try to find the mozregression:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.
| Reporter | ||
Comment 8•5 months ago
|
||
I also tried to find the regression range.
Last good: 2025-11-11
First bad: 2025-11-12
Pushlog: https://hg-edge.mozilla.org/mozilla-central/pushloghtml?fromchange=5c1a693f1ed10eb4d10df597e4fbf1555c758fba&tochange=051bafeb3aedcd9c81ba9ba9a1f8b46044fb4e09
Note that I was not able to go further with the bisection, since I am constantly logged out and all the windows and applications are closed due to this issue when I am trying to test the intermediate builds.
Comment 9•5 months ago
|
||
You can run the mozregression from command line, reproduce the issue and flip back to terminal where you just type the correct state. mozregression will terminate the firefox and launch a new one. Please try to get the intermediate builds range.
Thanks.
Comment 10•5 months ago
|
||
Mozregression results:
- last good: 2025-11-11
- first bad: 2025-11-12
- pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=f84254926bdf6d2506f6577156f9e7804fc9de38&tochange=cd20a71d574690e3162d9368225defce3ff06969
- potentially regressed by: bug 1998382
Please let me know if there's anything else we can do on our side, thank you.
Comment 11•5 months ago
|
||
Set release status flags based on info from the regressing bug 1998382
Comment 12•5 months ago
|
||
I can reproduce this on Ubuntu 24.04LTS (GNOME 46) but not Ubuntu 25.10 (GNOME 49) with latest Nightly 148.0a1. The window renders transparent with a hall of mirrors effect after toggling the titlebar. There is no crash and it remains responsive to commands but cannot be seen.
Updated•5 months ago
|
Comment 13•5 months ago
|
||
Should we consider reverting bug 1998382 from Beta due to this and bug 2003045?
Comment 14•5 months ago
|
||
Ugh, going off just the history of WaylandSurface.cpp, that's probably a lot easier said than done :\
Comment 15•4 months ago
|
||
Looks like compositor bug of GNOME 46 and also it happens on titlebar switch only. We have only one report of it so far and from QA do think it's okay to keep it as is.
Comment 16•4 months ago
|
||
Will check bug 2003045 for details.
Comment 17•4 months ago
|
||
The bug is marked as tracked for firefox147 (beta) and tracked for firefox148 (nightly). However, the bug still isn't assigned and has low priority.
:jstutte, could you please find an assignee and increase the priority for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 18•4 months ago
|
||
Comment 15 seems to say we can stay relaxed here.
Comment 19•4 months ago
|
||
This is a reminder regarding comment #17!
The bug is marked as tracked for firefox147 (beta) and tracked for firefox148 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned and has low priority.
Comment 20•4 months ago
|
||
This is a reminder regarding comment #17!
The bug is marked as tracked for firefox147 (beta) and tracked for firefox148 (nightly). We have limited time to fix this, the soft freeze is in 3 days. However, the bug still isn't assigned and has low priority.
Updated•4 months ago
|
Updated•4 months ago
|
Comment 21•4 months ago
|
||
Bug in outdated GNOME 46 Mutter compositor in minor functionality.
Updated•4 months ago
|
Description
•