After upgrading from F37 to F38, there is an extra package required to successfully read mail after boot. Unless you manually install thunderbird-wayland package, invoking Thunderbird permanently stalls showing a blackscreen. Workaround: Killing the blackscreen and invoking Thunderbird a second time then works as expected. Proposed Fix: If Thunderbird is installed on a Wayland screen, force an install of thunderbird-wayland package. Reproducible: Always Steps to Reproduce: 1.On F37, install and configure Thunderbird as you normally would. 2.Upgrade F37 to F38. 3.Invoke Thunderbird. Note that Thunderbird blackscreens forever. Actual Results: Application blackscreen. Expected Results: Normal Thunderbird operation. See the discussion "Thunderbird black at first launch with F38" on the Fedora user list (email: users.org) for one instance of the issue and how to resolve it. The Fedora update tool is missing a step to install the extra package in F38.
I meant that you should file an issue on Thunderbird about the black screen. The updater doesn't know if you're using Wayland or not. Also, https://bugzilla.redhat.com/show_bug.cgi?id=2177283
Can you run Thunderbird from a terminal the first time to see if there are any error messages?
There are no error messages when you start Thunderbird from the terminal window. I also tried the --jsdconsole option, which opens up a debug window that also blackscreens. Adding in the missing thunderbird-wayland package resolves the problem. I filed this bug against the upgrader because either it or thunderbird package need to know that Wayland is in use and install the new package as part of the upgrade.
I have a clean install of F38 and am normally in GNOME on Wayland. For me, Firefox and Thunderbird work normally without either firefox-wayland or thunderbird-wayland installed. The same was true in earlier Fedora versions.
FWIW I have a clean install too and have the bug described.
*** Bug 2196042 has been marked as a duplicate of this bug. ***
When I started Thunderbird after logging in, I noticed that there was a black screen for about 1 second before it appeared normally as usual. Normally I wouldn't pay attention to that, but maybe it's related. I restarted it two more times and the black screen appeared for 1 second the second time, but not the third. I'm still not clear on what the purpose of the firefox-{wayland,x11} and thunderbird-wayland packages is, since I've never had to install them for normal operation in either Wayland or Xorg, and I'd have thought that since they're not installed by default, they shouldn't normally be necessary.
Workaround: Downgrading from thunderbird-102.10.0-1.fc38.x86_64 to thunderbird-102.9.1-1.fc38.x86_64 resolves this blackscreen bug. Can we get the thunderbird-102.10.0 version removed from the repo to limit the number of people experiencing this high-visibility bug?
For me, the window is not black, but there are some tall, narrow black rectangles outside the window when I tile Thunderbird to the left or right half of the screen. Installing thunderbird-wayland and using the “Thunderbird on Wayland” launcher still fixes it, though.
Interesting Observation: I normally start Thunderbird, kill it due to the black-screen and restart it to read my mail. While I am doing that, I usually also do a dnf update (not using the Gnome Software app due to its major bugs), and then sometimes reboot to pick up the new changes. Twice now I have warm-rebooted (as opposed to cold shutdown and startup) and Thunderbird has worked correctly after the reboot. Upon rebooting, I go into Thunderbird again, and it works correctly the first time, without the black-screen debacle. This result would appear to show that there is an uninitialized variable in the critical chain of actions that is key to the issue. It also may explain why some people have different defects showing, or be unable to show the fault at all. I believe that KVM will clean the memory correctly, while a reboot does not.
Just to add a little more to this issue. I am running Thunderbird 102.10.0 with F38 Desktop on Gnome 44.1 and Wayland windowing system. Having used Fedora, Gnome and Thunderbird for many years now as my daily home PC, this is the first time I've had this issue. I have installed the additional thunderbird-wayland package as recommended and the issue persists. The restart of Thunderbird always works after closing the first black window session. Moving the mouse from side to side in the black window, the cursor changes to the double arrow where the folder menu demarcation is. It does not change in the up and down direction where the preview screen demarcation would normally be.
If you installed the wayland package, then you need to choose the "Thunderbird on Wayland" option, not the "Thunderbird" one.
Samuel stated: > If you installed the wayland package, then you need to choose the "Thunderbird on Wayland" option, not the "Thunderbird" one. I went looking. I'm unsure where you are referring to, but there is no "Thunderbird on Wayland" option. There is however, a thunderbird-wayland package in the repo that depends on thunderbird. The problem is that thunderbird-wayland package does not work. It is broken. With or without it installed, I can see the mouse tracking over edges as expected, but just over an unusable blackscreen. Just for grins, I reinstalled: $ sudo rpm -e thunderbird thunderbird-librnp-rnp-102.10.0-1.fc38.x86_64 thunderbird-wayland $ sudo dnf install thunderbird-wayland Fedora 38 - x86_64 - Updates 59 kB/s | 24 kB 00:00 Fedora Modular 38 - x86_64 - Updates 68 kB/s | 25 kB 00:00 RPM Fusion for Fedora 38 - Free tainted 18 kB/s | 3.2 kB 00:00 Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: thunderbird-wayland x86_64 102.10.0-1.fc38 updates 12 k Installing dependencies: thunderbird x86_64 102.10.0-1.fc38 updates 102 M thunderbird-librnp-rnp x86_64 102.10.0-1.fc38 updates 1.2 M Transaction Summary ================================================================================ Install 3 Packages Total download size: 103 M Installed size: 279 M Is this ok [y/N]: y Downloading Packages: (1/3): thunderbird-wayland-102.10.0-1.fc38.x86_ 88 kB/s | 12 kB 00:00 (2/3): thunderbird-librnp-rnp-102.10.0-1.fc38.x 2.5 MB/s | 1.2 MB 00:00 (3/3): thunderbird-102.10.0-1.fc38.x86_64.rpm 18 MB/s | 102 MB 00:05 -------------------------------------------------------------------------------- Total 17 MB/s | 103 MB 00:06 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : thunderbird-librnp-rnp-102.10.0-1.fc38.x86_64 1/3 Installing : thunderbird-102.10.0-1.fc38.x86_64 2/3 Running scriptlet: thunderbird-102.10.0-1.fc38.x86_64 2/3 Installing : thunderbird-wayland-102.10.0-1.fc38.x86_64 3/3 Running scriptlet: thunderbird-102.10.0-1.fc38.x86_64 3/3 Running scriptlet: thunderbird-wayland-102.10.0-1.fc38.x86_64 3/3 Verifying : thunderbird-102.10.0-1.fc38.x86_64 1/3 Verifying : thunderbird-librnp-rnp-102.10.0-1.fc38.x86_64 2/3 Verifying : thunderbird-wayland-102.10.0-1.fc38.x86_64 3/3 Installed: thunderbird-102.10.0-1.fc38.x86_64 thunderbird-librnp-rnp-102.10.0-1.fc38.x86_64 thunderbird-wayland-102.10.0-1.fc38.x86_64 Complete! Then, running Thunderbird does the exact same thing - blackscreen on first use. On second use, it works as intended.
I don't know which desktop you're using, but after you install that package, you will have two Thunderbird program options, one that has "on Wayland" in the name. That's the one you need to use to avoid this issue.
I'm surprised this is closed. For the past week at least, whichever package you launch first it either crashed, or give you the black screen, then you run the other Thunderbird package and it works normally. Is this really going to stay closed?
We're going to run Thunderbird on Wayland by default for next TB line based on Firefox 115. Until that TB will remain X11 application. What you see is a general bug in XWayland and affects Firefox in X11 mode too. AFAIK it was addressed in mutter somehow. See https://bugzilla.mozilla.org/show_bug.cgi?id=1788205 This patch is used by Debian for Mutter: https://salsa.debian.org/gnome-team/mutter/-/blob/8fcc1a017d342e6dadd521dacfa845824a7de490/debian/patches/display-Set-compositor-selection-earlier-on-XWayland.patch
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.