Launchpad has imported 22 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1601082.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2019-12-03T21:39:27+00:00 Pts+bmo wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 Steps to reproduce: 1. Open Firefox and make sure it's the default browser. 2. Open another application that can open links in the default browser. Use that application to open a new tab. 3. Change which window has focus. Actual results: Changing which window has focus causes Firefox to crash. (Sometimes the act of opening the link causes the change of focus so the crash happens as part of step 2, but the first several times I tried, I read the whole article and it only crashed when I switched away.) Expected results: It shouldn't crash. You should be able to change which window has focus normally. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/8 ------------------------------------------------------------------------ On 2019-12-03T21:46:50+00:00 Pts+bmo wrote: I submitted this in crashreporter a few times, e.g.: 5007f351-8b66-43b8-94c1-61bf60191203 36c530fc-462c-45dd-abbc-ce08d0191203 66d7e78e-d1d4-42b7-81f3-3f1d30191203 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/9 ------------------------------------------------------------------------ On 2019-12-04T01:10:02+00:00 Pts+bmo wrote: Okay, I've finally narrowed it down. This only happens when `MOZ_USE_XINPUT2=1` is set in the environment. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/10 ------------------------------------------------------------------------ On 2019-12-04T01:59:00+00:00 Pts+bmo wrote: (In reply to Peter Simonyi from comment #2) > Okay, I've finally narrowed it down. This only happens when > `MOZ_USE_XINPUT2=1` is set in the environment. Hm, I thought that was true, but it's happening again without it set. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/11 ------------------------------------------------------------------------ On 2019-12-04T05:56:48+00:00 Pts+bmo wrote: Okay, the trigger seems to be just using Wayland. Tested with a fresh installation and fresh profile in a fresh user account, the only change being setting `MOZ_ENABLE_WAYLAND=1`. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/12 ------------------------------------------------------------------------ On 2019-12-04T07:53:18+00:00 Pts+bmo wrote: Regression range: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=4b70ece3af6ccc09d0dd09e850f68628aded1467&tochange=4c3bb8394488a27d2e9a2913c4716055604cf068 I can't find a bad build in mozilla-central though. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/13 ------------------------------------------------------------------------ On 2019-12-04T08:23:35+00:00 madperson wrote: based on the regression range, i'll assume it got introduced by bug 1592350. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/14 ------------------------------------------------------------------------ On 2019-12-04T08:30:04+00:00 Pts+bmo wrote: That seems like the most likely one, but only when it was uplifted. I tried mozilla-inbound build built on 2019-11-05 11:37:23.610000, revision 4d585c7e (first build with bug 1592350 fixed) and it does not crash. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/15 ------------------------------------------------------------------------ On 2019-12-04T15:19:36+00:00 Pts+bmo wrote: This also seems to crash when using the switch-to-tab function of the location bar. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/16 ------------------------------------------------------------------------ On 2019-12-05T17:42:21+00:00 Spastorino wrote: If I click `What's New` on the Firefox About dialog it happens the same thing. I guess it's the same issue. Also using `MOZ_ENABLE_WAYLAND=1` Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/18 ------------------------------------------------------------------------ On 2019-12-07T13:08:52+00:00 Farid wrote: I can confirm I am also affected using Wayland, under sway. The bug disappears either by downgrading to 70.0.1 or by disabling the MOZ_ENABLE_WAYLAND environment variable (and thus using XWayland). Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/19 ------------------------------------------------------------------------ On 2019-12-09T12:26:16+00:00 Stransky wrote: I'm unable to reproduce in Fedora 31 / Gnome / Firefox 71 from Mozilla. Do you see that under Gnome or is that Sway only? Also can you please try to get full backtrace, how-to for Fedora is here [1]. The crash stat at mozilla are missing signatures from system libraries. [1] https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_crash Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/20 ------------------------------------------------------------------------ On 2019-12-10T05:28:14+00:00 Pts+bmo wrote: Created attachment 9114802 crash_bt I am using Fedora 31 / Gnome 3 / Firefox 71 from Mozilla. (I do *not* see the bug in the Fedora package `firefox-71.0-8.npgo.fc31.x86_64` though.) I've attached the backtrace (though it's a little incomplete because the Firefox from Mozilla doesn't come with debuginfo). For this one, I triggered the crash by clicking the "What's new" link in the About window, since that's an easy case to set up. Additionally, here's a bit of the console output that didn't end up in the log file: ``` (firefox:62794): Gdk-WARNING **: 07:54:45.019: (gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface) firefox: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&surface->ref_count)' failed. Thread 1 "firefox-bin" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; ``` And I did try the DumpJSStack part of those instructions but unsurprisingly didn't get any results: ``` (gdb) print DumpJSStack() 'DumpJSStack' has unknown return type; cast the call to its declared return type (gdb) print (void)(DumpJSStack()) there is no JSContext on the stack! [Thread 0x7fffe02e3700 (LWP 62803) exited] $1 = void ``` Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/21 ------------------------------------------------------------------------ On 2019-12-10T08:07:54+00:00 Stransky wrote: Can you attach your about:config please? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/22 ------------------------------------------------------------------------ On 2019-12-10T08:12:12+00:00 Stransky wrote: Great, I can reproduce it with Firefox 71 from mozilla but it works with Firefox 72 beta and Nightly and also Firefox from Fedora. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/23 ------------------------------------------------------------------------ On 2019-12-10T12:11:53+00:00 Spastorino wrote: I reproduce the error using Archlinux Firefox 71.0-1, clicking `What's New` from Firefox About dialog is the way I found that makes the error more consistently show up. From time to time it also crashes clicking on links from Gnome notifications but that does not happens in the 100% of the cases. I've mentioned this earlier but I'm also using `MOZ_ENABLE_WAYLAND=1`. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/24 ------------------------------------------------------------------------ On 2019-12-11T00:38:05+00:00 Pts+bmo wrote: I used a fresh profile, so about:config is all defaults. Yes, the crash is only in 71 — Nightly and Beta72 are unaffected. So I guess if there's no 71 point release then no work is needed; this will fix itself for release users in January. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/25 ------------------------------------------------------------------------ On 2019-12-16T10:43:32+00:00 Krs-random wrote: Can confirm, arch - wayland - firefox 71 - MOZ_ENABLE_WAYLAND=1 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/34 ------------------------------------------------------------------------ On 2019-12-16T12:20:45+00:00 Stransky wrote: *** Bug 1598995 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/36 ------------------------------------------------------------------------ On 2019-12-16T12:22:02+00:00 Stransky wrote: Closing as WONTFIX as it's 71 only. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/37 ------------------------------------------------------------------------ On 2019-12-20T08:20:12+00:00 Stransky wrote: *** Bug 1604817 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/38 ------------------------------------------------------------------------ On 2020-01-02T13:34:31+00:00 Stransky wrote: *** Bug 1606618 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/39 ** Changed in: firefox Status: Unknown => Won't Fix ** Changed in: firefox Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1855997 Title: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1 Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: - make sure Firefox is not running - export MOZ_ENABLE_WAYLAND=1 - firefox then in a new terminal - export MOZ_ENABLE_WAYLAND=1 - firefox www.google.com Expectation: - a new tab opens in the Firefox window, loading google Actual result: - firefox crashes This is a recent regression: it used to work fine in 70.0.1+build1-0ubuntu0.19.10.1, broke when I upgraded to 71.0+build5-0ubuntu0.19.10.1. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:41 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1855997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
