Created attachment 150116 [details] Firefox window showing plasma splash screen SUMMARY Firefox is set to autostart on login and randomly starts up with an empty window containing just the title bar and initially showing the plasma splash screen. When minimised and then maximised, the wallpaper is displayed instead. The only way to fix this is to close firefox and restart it. Screenshots attached STEPS TO REPRODUCE 1. Add firefox to autostart OBSERVED RESULT Next time you log into plasma, firefox sometimes starts up showing the kde splash screen in the firefox window and other times showing the firefox home screen. EXPECTED RESULT Firefox should always start up showing the firefox home screen SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable ADDITIONAL INFORMATION Seems to only happen during autostart.
Created attachment 150117 [details] Firefox window containing wallpaper
Both cases are caused by the background showing through. In the first screenshot, it's the splash screen, and in the second, it's the wallpaper.
This is happening with both Firefox and Thunderbird without fail at every startup from autostart.
(In reply to Richard Ullger from comment #3) > This is happening with both Firefox and Thunderbird without fail at every > startup from autostart. Can confirm this for FF-102esr and Plasma-(In reply to Richard Ullger from comment #3) > This is happening with both Firefox and Thunderbird without fail at every > startup from autostart. Can confirm this for FF-102esr and Plasma-5.24.7. I'm not seeing this with xfce or with FF-91esr. As a workaround: exclude FF/TB from session-restore. When I start FF-102esr manually after login, everything's fine. I'm not using TB-102.
Sounds like an application issue; if you can still reproduce this issue, please report it to Mozilla