Bug 2084590 - [wayland] Thunderbird crashes on screens with different scaling
Summary: [wayland] Thunderbird crashes on screens with different scaling
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 36
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-12 13:27 UTC by Marc Ponschab
Modified: 2023-05-25 16:54 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:54:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marc Ponschab 2022-05-12 13:27:28 UTC
Description of problem:

The main screen (4K) of an XPS 15 9550 is set to a scaling of 200%, the second screen (24", Full HD, portrait) to 100%. Thunderbird-wayland is running on the second screen.

When dragging the main window or opening sub-windows in such a way that parts of the window goes outside the main screen's borders, Thunderbird crashes immediately with the following message:

[1466703.519] wl_display(wl_surface@90, 2, "Buffer size (673x360) must be an integer multiple of the buffer_scale (2)")


Version-Release number of selected component (if applicable):
91.9.0-1.fc36


How reproducible:
Always


Steps to Reproduce:
1. Open thunderbird-wayland on an unscaled screen
2. Drag the Thunderbird window to a 200% scaled screen so that parts of the window are outside the scaled screen.
3. Thunderbird crashs immediately


Actual results:
Thunderbird crashes immediately


Expected results:
The window is displayed on the scaled screen, parts of the window outside the screen are not visible.


Additional info:
I suspect that this bug in Firefox describes the same problem:

https://bugzilla.mozilla.org/show_bug.cgi?id=1767916
https://bugzilla.redhat.com/show_bug.cgi?id=2082878

Thunderbird started without MOZ_ENABLE_WAYLAND=1 does not crash but behaves as expected.

Comment 1 Martin Stransky 2022-05-12 13:55:15 UTC
TB Wayland is based on old 91 ESR line, it's not supposed to run on Wayland correctly.

Comment 2 Marc Ponschab 2022-05-12 14:11:16 UTC
91.9 seems to me to be the latest release. So is there just the beta of 102 or wait?

Comment 3 Marc Ponschab 2022-05-12 16:19:47 UTC
FYI, I tried version 101.0b2, the same error occurs.

Comment 4 Marc Ponschab 2022-05-12 16:28:59 UTC
https://bugzilla.mozilla.org/show_bug.cgi?id=1760001

Comment 5 Jan Horak 2022-06-21 09:04:01 UTC
The crash was mainly due to bug in mutter which should be fixed in F36. Do you still see the crash?

Comment 6 Marc Ponschab 2022-06-23 11:37:24 UTC
Thank you, the problem seems to be fixed indeed, I can't reproduce it anymore.

Should I close the issue and if so, with what status?

Comment 7 Ben Cotton 2023-04-25 17:08:58 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ludek Smid 2023-05-25 16:54:27 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.


Note You need to log in before you can comment on or make changes to this bug.