Firefox doesn't restart after update

Bug #1871009 reported by fabtagon
This bug affects 2 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)

Bug Description

After upgrading to firefox amd64 74.0.1+build1-0ubuntu0.18.04.1 (using apt-get), a message appeared in the running Firefox session: 'Firefox needs to be restarted' (as usual, nothing wrong with that). After clicking ok (or 'do it now' or what the exact message was), Firefox terminates.

Expected behaviour: Firefox actually restarts

Experienced behaviour: Nothing seemed to happen. Firefox terminated but never came back. (Starting Firefox again by hand worked flawlessly.)

I have no profiles defined. I don't usually pass any options when starting Firefox.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 74.0.1+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
 /dev/snd/controlC0: fab 3616 F.... pulseaudio
 /dev/snd/controlC1: fab 3616 F.... pulseaudio
 saved-telemetry-pings/a1103722-309c-47da-b9da-2bc9411237b9 (0o600, wrong owner)
 saved-telemetry-pings/e1cac187-9dd1-48b9-bb99-8c67374c7212 (0o600, wrong owner)
 saved-telemetry-pings/fbf7331c-39a9-4539-97fa-280e7d343563 (0o600, wrong owner)
BuildID: 20200403064753
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 6 03:13:58 2020
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-04-27 (1805 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
 default via dev eth0 proto dhcp metric 100 dev lxcbr0 proto kernel scope link src linkdown dev eth0 scope link metric 1000 dev eth0 proto kernel scope link src metric 100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-f8832267-2764-4f52-b9df-136771180712
PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=74.0.1/20200403064753 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to bionic on 2018-08-18 (596 days ago) 08/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M. 970A-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: To be filled by O.E.M. To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
fabtagon (fabtagon) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you add your journalctl log from the session where you had the issue?

Changed in firefox (Ubuntu):
status: New → Incomplete
Revision history for this message
fabtagon (fabtagon) wrote :

Installation happened about 02:29:09, as atp log tells:

Start-Date: 2020-04-06 02:29:09
Commandline: apt-get upgrade -y
Requested-By: USERNAME (1001)
Upgrade: firefox-locale-de:amd64 (74.0+build3-0ubuntu0.18.04.1, 74.0.1+build1-0ubuntu0.18.04.1), firefox-locale-en:amd64 (74.0+build3-0ubuntu0.18.04.1, 74.0.1+build1-0ubuntu0.18.04.1), firefox-locale-sv:amd64 (74.0+build3-0ubuntu0.18.04.1, 74.0.1+build1-0ubuntu0.18.04.1), firefox:amd64 (74.0+build3-0ubuntu0.18.04.1, 74.0.1+build1-0ubuntu0.18.04.1)
End-Date: 2020-04-06 02:29:35

Revision history for this message
Olivier Tilloy (osomon) wrote :

I'm not seeing any clue as to what might have happened in the journal, unfortunately.

Just to confirm: this was a one-off issue, now firefox works well?

Revision history for this message
fabtagon (fabtagon) wrote :

Yes, Firefox works well.

No, this seems to happen for about 50% of Firefox updates. In case of past occourences, one problem was that command line parameters (that had been given to the instances that had been stopped) were not passed to the restarted instance. But this bug is, afaik, fixed. And in my current setup, Firefox doesn't require any parameters to restart gracefully.

Olivier Tilloy (osomon)
Changed in firefox (Ubuntu):
status: Incomplete → New
Revision history for this message
fabtagon (fabtagon) wrote :

Same issue again when updating to 80.0+build2-0ubuntu0.20.04.1 today.

Revision history for this message
fabtagon (fabtagon) wrote :

Alas when updating to 80.0.1+build1-0ubuntu0.20.04.1.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Found bug 1900095 which describes the same issue, I've also experienced the same with the last couple of Firefox updates.

Olivier Tilloy (osomon)
Changed in firefox (Ubuntu):
importance: Undecided → Medium
Revision history for this message
fabtagon (fabtagon) wrote :

Alas when updating to 84.0+build3-0ubuntu0.20.04.1

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers