Launchpad has imported 14 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1598995.

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-11-25T04:03:50+00:00 Bjonnh-ff wrote:

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

Steps to reproduce:

- Open firefox (empty or used profile, no difference)
-  Open an URL from xdg or from a terminal (firefox-developer-edition 
https://www.mozilla.org)


Actual results:

Firefox Crashes and ask to restart. If I run firefox in a terminal I see:
(firefoxdeveloperedition:496386): Gdk-WARNING **: 21:58:25.007: 
(../gtk/gdk/wayland/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.
ExceptionHandler::GenerateDump cloned child 496921
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.


Expected results:

Firefox should open a new tab

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/0

------------------------------------------------------------------------
On 2019-11-25T04:11:39+00:00 Bjonnh-ff wrote:

I tried with setting GDK_BACKEND=x11. As long as GDK_BACKEND is set for
the new firefox call, when adding a new tab in a terminal it works.

If I set GDK_BACKEND only for the initial firefox call, the subsequent
calls in another terminal with GDK_BACKEND unset do not open a new tab,
and after a few seconds a window saying that firefox is not responding
appears.

I will make firefox run in X11 mode for now. But I would be happy run
any experiment that could help solve that issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/1

------------------------------------------------------------------------
On 2019-11-25T04:17:16+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/2

------------------------------------------------------------------------
On 2019-11-26T13:32:37+00:00 Stransky wrote:

Which desktop do you run? And do you see it also with nightly and release?
Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/3

------------------------------------------------------------------------
On 2019-11-28T18:47:02+00:00 Bjonnh-ff wrote:

I do not see it with release. 
Desktop is gnome-shell.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/4

------------------------------------------------------------------------
On 2019-11-28T18:59:12+00:00 Bjonnh-ff wrote:

Doesn't happen with 20191128-firefox-72.0a1 . So I guess it has been
fixed and will make its way in the DE?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/5

------------------------------------------------------------------------
On 2019-11-29T22:04:04+00:00 François Glais wrote:

Isn't it expected to have some issues when meddling with GDK_BACKEND?

Wouldn't the use of MOZ_ENABLE_WAYLAND=1 solve the issue? Or Firefox
really tries to support both approaches?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/6

------------------------------------------------------------------------
On 2019-12-02T17:40:11+00:00 Bjonnh-ff wrote:

I only used GDK_BACKEND to revert to x11 (and then solving the issue).
GDK_BACKEND was unset in the issue reported.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/7

------------------------------------------------------------------------
On 2019-12-04T21:59:57+00:00 Maxime de Roucy wrote:

I can confirm this bug.

Archlinux (uptodate)
Mozilla Firefox 71.0

Same result with `MOZ_ENABLE_WAYLAND=1` or `GDK_BACKEND=wayland`.

```
max@mde-oxalide % MOZ_ENABLE_WAYLAND=1  firefox
(firefox:2094): Gdk-WARNING **: 22:52:46.806: 
(../gtk/gdk/wayland/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.
ExceptionHandler::GenerateDump cloned child 2328
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.
Failed to open curl lib from binary, use libcurl.so instead
```
the line Gdk-WARNING / crash appear when I run
```
xdg-open 'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995'
```
Same result if I run `MOZ_ENABLE_WAYLAND=1 firefox 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995'`.

If I run `firefox 'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995'` 
without env, it open a window saying:
```
Firefox is already running, but is not responding. To open a new window, you 
must first close the existing Firefox process, or restart your system.
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/8

------------------------------------------------------------------------
On 2019-12-11T07:58:35+00:00 Marius Gedminas wrote:

I've started seeing this on Ubuntu with Firefox 71:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997.  Firefox
70 did not suffer from this crash.  I've stopped using
MOZ_ENABLE_WAYLAND=1 as a workaround.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/12

------------------------------------------------------------------------
On 2019-12-11T08:21:59+00:00 Stransky wrote:

(In reply to Marius Gedminas from comment #9)
> I've started seeing this on Ubuntu with Firefox 71: 
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997.  Firefox 70 
> did not suffer from this crash.  I've stopped using MOZ_ENABLE_WAYLAND=1 as a 
> workaround.

Mariu, can you check if that works for you in Beta or Nightly?
Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/13

------------------------------------------------------------------------
On 2019-12-11T08:47:39+00:00 Marius Gedminas wrote:

I cannot reproduce this in Beta (firefox-72.0b4.tar.bz2).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/14

------------------------------------------------------------------------
On 2019-12-16T07:10:25+00:00 Stransky wrote:

*** Bug 1603977 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/16

------------------------------------------------------------------------
On 2019-12-16T12:20:45+00:00 Stransky wrote:


*** This bug has been marked as a duplicate of bug 1601082 ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/17


** Changed in: firefox
       Status: Unknown => Invalid

** 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:
  Invalid
Status in firefox package in Ubuntu:
  Triaged

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     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to