Bug 1596748

Summary: about:newtab shows only a blank page
Product: [Fedora] Fedora Reporter: rugk <7d28c752>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: 0xalen+redhat, 7d28c752, alexl, gecko-bugs-nobody, jan.public, jhorak, john.j5live, jprajzne, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-30 13:59:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
about:newtab page
none
Settings not shown… none

Description rugk 2018-06-29 15:14:14 UTC
Created attachment 1455530 [details]
about:newtab page

Description of problem: After the update from Firefox 60 to v61, about_newtab only shows a blank page.


Version-Release number of selected component (if applicable): 61.0-4.fc28


How reproducible: Always.


Steps to Reproduce:
1. Update. Open Firefox.
2. (Open a new tab or manually go to about:newtab.) 

Actual results:
Actually, it does not really show an empty page, but only the "onboarding" Firefox icon is visible – and works, as expected.

Expected results:
New tab page as before…

Additional info:
see screenshot, no errors in JS console
BTW also if I have the dark theme enabled, the background is still white. AFAIK a new thing in FF 61 was that it should be dark, in this case, too.

Comment 1 rugk 2018-06-29 20:47:24 UTC
Actually also the settings on the "home page" page are ju7st non-existant. (see screnshot)

Comment 2 rugk 2018-06-29 20:48:38 UTC
Created attachment 1455575 [details]
Settings not shown…

Comment 3 Martin Stransky 2018-07-02 09:30:29 UTC
Can you please try US locale?

Comment 4 rugk 2018-07-02 17:11:33 UTC
Tried it via

$ LANG=en-US firefox 

and it uses the en locale, but this issue here stays the same. I also tried it in a relatively fresh other profile and for some reason, there it worked without any problems (in German, not [only] en-US there.)

When starting via "$ LANG=en-US firefox" Firefox showed these log output on the console:

(firefox:4934): Gtk-WARNING **: 19:08:35.628: Locale not supported by C library.
	Using the fallback 'C' locale.

(/usr/lib64/firefox/firefox:5065): Gtk-WARNING **: 19:08:37.013: Locale not supported by C library.
	Using the fallback 'C' locale.

(/usr/lib64/firefox/firefox:5199): Gtk-WARNING **: 19:08:38.407: Locale not supported by C library.
	Using the fallback 'C' locale.

(/usr/lib64/firefox/firefox:5214): Gtk-WARNING **: 19:08:38.516: Locale not supported by C library.
	Using the fallback 'C' locale.

(/usr/lib64/firefox/firefox:5219): Gtk-WARNING **: 19:08:38.560: Locale not supported by C library.
	Using the fallback 'C' locale.

Comment 5 Jiri Prajzner 2018-11-12 14:33:21 UTC
i get:

File not found

Firefox can't find the file at jar:file:///usr/lib64/firefox/browser/features/activity-stream.xpi!/chrome/content/prerendered/en-GB/activity-stream-prerendered.html.

    Check the file name for capitalisation or other typing errors.
    Check to see if the file was moved, renamed or deleted.

firefox version 62.0.3 (64-bit)

Comment 6 Martin Stransky 2018-11-12 14:45:20 UTC
Can you please try a new profile and/or Firefox safe mode?

Comment 7 Jiri Prajzner 2018-11-12 14:52:29 UTC
(In reply to Martin Stransky from comment #6)
> Can you please try a new profile and/or Firefox safe mode?

i can reproduce it in safe mode, it actually shows the activity stream every other tab or so, but mostly it doesn't not show what it is supposed to.

Comment 8 rugk 2018-11-12 18:39:36 UTC
This has long fixed itself. (already in the next big Firefox release if I remember)

So if it were about me, you can close the issue, but it seems in https://bugzilla.redhat.com/show_bug.cgi?id=1596748#c5 another user had the same problem.