1905858 - In the Bookmarks Bar with held mousedown Firefox crashes on ESC key

Status: RESOLVED WONTFIX

(Core :: Widget: Gtk, defect, P3)

Description

[bugzilla-ffx]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

Steps to reproduce:

In the bookmarks bar, inside a bookmarks folder (tiny window with the folder's content) I accidentally clicked a bookmark and because it was accidental i didn't release the held-down mouse button. I tried to prevent opening the webpage by pressing the ESC key on my keyboard.

Actual results:

The entire Firefox instance crashed / closed.

Expected results:

The tiny window with the bookmark folder's contents should close, just as it does when pressing ESC without the mouse button pressed.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Martin Stránský [:stransky] (ni? me)]

Can you please create a screencast of the issue:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Create_screenshot/screencast_for_a_bug_report

Please attach content of about:support page.

Please try to attach backtrace of the crash:
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Using_Mozilla_crash_reporter

Thanks.

Comment 3

[bugzilla-ffx]

Attachment: about:support

Comment 4

[bugzilla-ffx]

Attachment: screencast.mkv

Comment 5

[bugzilla-ffx]

Attachment: stderr output

Error messages in standard error, but nothing in about:crashes

Comment 6

[Martin Stránský [:stransky] (ni? me)]

Version: 115.12.0esr is not supposed to run under Wayland. Please try latest version - 127.0.2.

Comment 7

[bugzilla-ffx]

I did not know that. This version together with wayland is distributed by Debain in the standard gnome installation. It seems this issue is therefore to be attributed to the distribution of unmatching software versions. On 172.0.2 Fedora this issue is indeed fixed. Thank you for your effort.