Bugzilla

On my arch Linux systems, running all the recent Thunderbird Betas in the Plasma desktop under Wayland, for a long time, including 114.0b2 has no problem with this at all - the Thunderbird window has the normal maximise, minimise and close icons and they function as expected.   Whether this is dependent on particular theme settings, or icon set choices where a particular icon theme or choice of desktop settings may lead to a problem would need to know from from other users who may experience the issue with specific settings.  Equally if the original reporter is having this issue in an arch Linux system, it may depend on specific settings - I note that the reporter is using DWM and it is possible that DWM is underlying the cause.  I do know of other Arch Linux users who run Thunderbird under Gnome which also uses Wayland and the issue does not appear in that setup as far as I am aware.

Can the reporter switch DWM to a different window manager and see if the issue persists? One comment that may possibly have some relevance is that a year or so back I did have some problems with the displayed icons for Thunderbird itself which turned out to be due to a problem with the .desktop files - the only way I found at the time to fix that was to remove all desktop files and re-create them from scratch and at the time the Thunderbird icon at the top left of the Thunderbird window was showing a 'W' which was the generic Wayland icon, as well as the panel icon showing the running Thunderbird process was also a 'W' icon.  It is conceivable that in the reporter's case an analogous problem could lead to issues with the max-min and close icons being not present and worth exploring whether in that case looking into the .desktop files for Thunderbird may also help find a fix (in my case I had different sets of .desktop files for stock Thunderbird that I don't use, and for Thunderbird beta, and additional files had been created when making new shortcuts for Thunderbird beta - I cleared them all out and started from scratch, and then it all worked fine).  I hope this helps.

On my arch Linux systems, running all the recent Thunderbird Betas in the Plasma desktop under Wayland, for a long time, including 114.0b2 has no problem with this at all - the Thunderbird window has the normal maximise, minimise and close icons and they function as expected.   Whether this is dependent on particular theme settings, or icon set choices where a particular icon theme or choice of desktop settings may lead to a problem would need to know from from other users who may experience the issue with specific settings.  Equally if the original reporter is having this issue in an arch Linux system, it may depend on specific settings - I note that the reporter is using DWM and it is possible that DWM is underlying the cause.  I do know of other Arch Linux users who run Thunderbird under Gnome which also uses Wayland and the issue does not appear in that setup as far as I am aware.

Can the reporter switch DWM to a different window manager and see if the issue persists? One comment that may possibly have some relevance is that a year or so back I did have some problems with the displayed icons for Thunderbird itself which turned out to be due to a problem with the .desktop files - the only way I found at the time to fix that was to remove all desktop files and re-create them from scratch and at the time the Thunderbird icon at the top left of the Thunderbird window was showing a 'W' which was the generic Wayland icon, as well as the panel icon showing the running Thunderbird process was also a 'W' icon.  It is conceivable that in the reporter's case an analogous problem could lead to issues with the max-min and close icons being not present and worth exploring whether in that case looking into the .desktop files for Thunderbird may also help find a fix (in my case I had different sets of .desktop files for stock Thunderbird that I don't use, and for Thunderbird beta, and additional files had been created when making new shortcuts for Thunderbird beta - I cleared them all out and started from scratch, and then it all worked fine).  I hope this helps. (This in my case was not a Thunderbird bug but an application setup issue unrelated to the Thunderbird code)