Firefox crashes instantly after update from 51.0.1 to 52 on Ubuntu 16.04

Bug #1671079 reported by activjob GmbH on 2017-03-08
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Fix Released
Critical
firefox (Ubuntu)
Undecided
Unassigned

Bug Description

After the update from

firefox:amd64 51.0.1+build2-0ubuntu0.16.04.2 to 52.0+build2-0ubuntu0.16.04.1

on Ubuntu 16.04 LTS Firefox doesn't start anymore but shows the crash report dialog instead. On the terminal we get

    ExceptionHandler::GenerateDump cloned child 8129
    ExceptionHandler::SendContinueSignalToChild sent continue signal to child
    ExceptionHandler::WaitForContinueSignal waiting for continue signal...
    Speicherzugriffsfehler (Speicherabzug geschrieben)

This is mozilla's crash report:
https://crash-stats.mozilla.com/report/index/50b93881-7cf2-493d-a495-fc7b42170308

This happens to all users and also after removing ~/.mozilla

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Brandon (delvecktor) wrote :

I'm having this issue over XRDP.

safemode and firefox-trunk don't work either.

Changed in firefox:
importance: Unknown → Critical
status: Unknown → In Progress
activjob GmbH (la2nchpad-net) wrote :

It works when env var LOGNAME is set ... or: https://reviewboard.mozilla.org/r/118190/diff/1#index_header

Changed in firefox:
status: In Progress → Confirmed
Changed in firefox:
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 52.0.1+build2-0ubuntu0.12.04.1

---------------
firefox (52.0.1+build2-0ubuntu0.12.04.1) precise-security; urgency=medium

  * New upstream stable release (52.0.1build2)
    - Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson <email address hidden> Wed, 08 Mar 2017 16:00:56 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 52.0.1+build2-0ubuntu0.16.10.1

---------------
firefox (52.0.1+build2-0ubuntu0.16.10.1) yakkety-security; urgency=medium

  * New upstream stable release (52.0.1build2)
    - Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson <email address hidden> Wed, 08 Mar 2017 15:35:53 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 52.0.1+build2-0ubuntu0.14.04.1

---------------
firefox (52.0.1+build2-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * New upstream stable release (52.0.1build2)
    - Fix LP: #1671079 - Don't crash if LOGNAME is not set in the environment

 -- Chris Coulson <email address hidden> Wed, 08 Mar 2017 15:50:13 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.