Bug 1779809 - Gecko_IOThread - WARNING: pipe error: Broken pipe:
Summary: Gecko_IOThread - WARNING: pipe error: Broken pipe:
Keywords:
Status: CLOSED DUPLICATE of bug 1779570
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 19:02 UTC by Davi Garcia
Modified: 2019-12-09 09:40 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-12-09 09:40:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Davi Garcia 2019-12-04 19:02:02 UTC 
> Description of problem:

After updating Firefox to 71.0-8.npgo, many add-ons (ex.: Lastpass, Multi-account Container, etc) are unresponsive

Version-Release number of selected component (if applicable):

Upgrade  firefox-71.0-8.npgo.fc31.x86_64
Upgraded firefox-70.0.1-4.fc31.x86_64

How reproducible:

Not sure.

I see the following logs when running Firefox on terminal:

$ firefox 

[Parent 438412, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728
[Parent 438412, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728
[Parent 438412, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728
[Parent 438412, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728
[Parent 438412, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 728
Comment 1 Martin Stransky 2019-12-09 09:40:37 UTC 

*** This bug has been marked as a duplicate of bug 1779570 ***
Note You need to log in before you can comment on or make changes to this bug.