dragging tabs using pen/eraser on touchscreen causes error exit of Firefox with MOZ_ENABLE_WAYLAND=1
Categories
(Firefox :: Tabbed Browser, defect, P5)
Tracking
()
People
(Reporter: pabs3, Unassigned)
Details
(Whiteboard: QA-not-actionable)
I have the environment variable MOZ_ENABLE_WAYLAND=1 to enable the Wayland support in Firefox, this issue doesn't happen when I remove this environment variable.
The Thinkpad X201 Tablet is a laptop that has a touchscreen with pen, eraser and finger input. I am running Debian 12 bookworm on the laptop and I'm using GNOME shell Wayland version 42 as a desktop with both Firefox 99 and Firefox ESR 91 from the Debian bookworm/unstable apt repositories. I normally use Firefox ESR, so would appreciate it if any patch to fix this issue could be backported there too.
When I use the pen or eraser to try and move a tab to the left or right, Firefox exits immediately and prints errors on the terminal. Firefox 99 also pops up a crash reporter error message dialog. There are no core dumps generated.
The issue doesn't happen with the finger input of the touchscreen, which simply does not do anything with Wayland mode enabled (but does without that enabled).
This is the error in the terminal with Firefox 99:
(Firefox:284037): Gdk-CRITICAL **: 12:58:58.413: gdk_wayland_window_get_wl_surface: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
ExceptionHandler::GenerateDump cloned child 284428
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
This is the error that appears in a Crash Reporter dialog with Firefox 99:
The application had a problem and crashed.
Unfortunately, the crash reporter is unable to submit a report for this crash.
Details: The application didn't leave an application data file.
This is the error in the terminal with Firefox ESR 91:
(firefox-esr:284629): Gdk-CRITICAL **: 13:00:10.274: gdk_wayland_window_get_wl_surface: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
Gdk-Message: 13:00:10.280: Error 22 (Invalid argument) dispatching to Wayland display.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
|
||
Comment 1•4 years ago
•
|
||
Hello! Unfortunately I don't have the hardware to confirm this issue and will add the QA-not-actionable tag. Could you please answer the following questions in order to further investigate this issue.
- Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
- Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
- Do you have any addons installed if so can you list them?
|
|
||
Updated•4 years ago
|
The device where this happens doesn't currently doesn't have a storage device, so it could be some time before I can test this, I'll get back to you once I have a way to do that and have done the requested testing.
That said, I think (but can't yet confirm) the answer to 1 is yes and the answer to 3 is no. I definitely didn't test 2 at the time.
It would be helpful if in the meantime you can think of some additional testing I can do when I do have the device running an OS again, so that I can do the additional testing while it is working.
I tested this again and found that:
With Firefox 107 the issue no longer happens. The pen/eraser now behave the same as the finger mode; they do nothing in Wayland mode, but let you drag the tab in X11 mode.
With Firefox ESR 102.5 the issue still happens, but now a crash reporter dialog comes up.
These happen with a new profile in safe mode, which disables all extensions.
WIth a new profile the crash dialog can't find enough details to submit a report, so I submitted one crash using my regular browser profile.
I have a similar issue with Firefox on Wayland that only happens if MOZ_ENABLE_WAYLAND=1. For me, dragging a tab crashes Firefox 109.0.1.
When I do, Firefox crashes with this console log:
$ firefox
ExceptionHandler::GenerateDump cloned child 99770
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
I am using an XPS 13 Plus, using updated Archlinux and RiverWM as compositor.
Let me know if I can provide any additional info.
which is in line with the previous reporter.
Description
•