If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Version 51.0.1 doesn't display web pages (blank content) with AppArmor profile

RESOLVED FIXED

Status

()

Firefox
Security
P3
blocker
RESOLVED FIXED
8 months ago
4 months ago

People

(Reporter: Linda, Unassigned)

Tracking

({regression})

51 Branch
x86_64
Linux
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted][ele:1b])

Attachments

(1 attachment)

(Reporter)

Description

8 months ago
Created attachment 8831393 [details]
20170127_201436.jpg

User Agent: Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG-SM-G900A Build/MMB29M) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/4.0 Chrome/44.0.2403.133 Mobile Safari/537.36

Steps to reproduce:

In Ubuntu, software updater updates once a week.  I ran a standard update, and noticed it contained a Firefox update. My homepage is Google, and it opened as black and white with no text (see image).   I restarted with add on disabled (safe mode), and still no text.  When I type in the Google search field, nothing shows up.

I tried some other websites, and still nothing.  The only one that works has no text, www.purple.com.

Another weird thing is that when you open a tab, like troubleshooting info, then switch back to the Google tab, the Google tab now shows the troubleshooting page.

Something is really wrong.  I hate having to try a reset because it screws everything up, if it even will fix this, and I don't think users should have to reset because of a new version.  


Actual results:

Broken, see above.


Expected results:

It should have opened like the normal Google search page, with a white background and text.  When I type in the Google search field, it should show the text I am typing.
(Reporter)

Updated

8 months ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
(Reporter)

Comment 1

8 months ago
I did a refresh.  Firefox -> Help -> Troubleshooting Information -> Give Firefox a Tuneup [Refresh Firefox], and it seemed better.  The default homepage, "about:startpage" shows a Google search box, and it shows the text I type in it, but after that, when you click the search button, it's just blank, a plain white page.

Don't make me go to the dark side and switch to the Chrome browser.

Comment 2

8 months ago
As for the UI & text glitches, this bug seems similiar to Bug 1334533.
As for the title, it is too lame and says nothing specific, please change the title to something more appropriate (you can take the example of a Bug 1334533's title)

Comment 3

8 months ago
Another similiar issue: Bug 1334778.

Updated

8 months ago
Summary: Version 51.0.1 totally broken → Version 51.0.1 cannot makes displaying web pages unreadable (due to hardware accelertation?)

Comment 4

8 months ago
Another similiar one: Bug 1334830 (it is possible that FF 51+ is visually broken)

Comment 5

8 months ago
As for:

> Another weird thing is that when you open a tab, like troubleshooting info,
> then switch back to the Google tab, the Google tab now shows the
> troubleshooting page.

Yet another similiar bug: Bug 1334844
(Reporter)

Updated

8 months ago
Summary: Version 51.0.1 cannot makes displaying web pages unreadable (due to hardware accelertation?) → Version 51.0.1 makes displaying web pages unreadable (due to hardware acceleration?)
(Reporter)

Comment 6

8 months ago
I tried Firefox -> Preferences -> Advanced -> General -> Browsing and cleared "Use hardware acceleration when available".  Closed the browser, reopened, still same problem.  Also tried clearing "Use smooth scrolling", still no change.

My Chromium browser has "Use hardware acceleration when available" checked, and it is working okay, so I doubt the problem is hardware acceleration, but I don't know, maybe if that was a big change from the previous version of Firefox, maybe it is.  I'm not saying this to throw the Chromium browser up to you.  I would rather stick with Firefox.
(Reporter)

Updated

8 months ago
Severity: normal → blocker
(Reporter)

Comment 7

8 months ago
These bugs are related:

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627239
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988

In bug 1659988, in the 3rd patch file of /etc/apparmor.d/usr.bin.firefox, if you change the line (70):

   owner /dev/shm/org.chromium.* c,

to

   owner /dev/shm/org.chromium.* rw,

Apply it to /etc/apparmor.d/usr.bin.firefox

Then, sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox

it fixes it.

That is, the patch file:

***************************************

36a37,39
>   dbus (send)
>        bus=session
>        interface=org.gtk.vfs.MountTracker,
44a48
>   @{PROC}/[0-9]*/net/arp r,
65c69,70
<   owner /{,var/}run/shm/shmfd-* rw,
---
>   owner /{dev,{,var/}run}/shm/shmfd-* rw,
>   owner /dev/shm/org.chromium.* rw,
206a212
>     /usr/share/distro-info/debian.csv r,
209a216
>     /usr/include/python3.[0-5]/pyconfig.h r,
214c221
<     /usr/local/lib/python3.[0-4]/dist-packages/ r,
---
>     /usr/local/lib/python3.[0-5]/dist-packages/ r,
216c223
<     /usr/bin/python3.[0-4] r,
---
>     /usr/bin/python3.[0-5] r,

***************************************

No clue what most of this does, or if it's all necessary, but the line that made the difference (noted above), and the parts about changing python from 3.4 to 3.5, probably helped.

What a waste of weekend.

I'm looking for a job.  Do you want to hire me?
(Reporter)

Updated

8 months ago
Summary: Version 51.0.1 makes displaying web pages unreadable (due to hardware acceleration?) → Version 51.0.1 makes displaying web pages unreadable (due to apparmor?)
(Reporter)

Updated

8 months ago
Summary: Version 51.0.1 makes displaying web pages unreadable (due to apparmor?) → Version 51.0.1 makes displaying web pages unreadable (apparmor profile)

Updated

8 months ago
Duplicate of this bug: 1334778

Updated

8 months ago
Keywords: regression
Summary: Version 51.0.1 makes displaying web pages unreadable (apparmor profile) → Version 51.0.1 doesn't display web pages (blank content) with AppArmor profile

Updated

8 months ago

Updated

8 months ago
Component: Untriaged → Graphics
Product: Firefox → Core

Updated

8 months ago
Duplicate of this bug: 1334903
This doesn't appear to be gfx related?
Component: Graphics → General
Priority: -- → P3
Whiteboard: [gfx-noted]
Hello, I'm asking your help with an experiment with making decisions on bugs. You've been needinfo'ed on this bug. I'd like you to take one action to help this bug make progress toward a decision. The things you can do include:

* If you know or have a good guess of which product and component this bug belongs to, change the product and component of the bug
* If you know of the right person to ask about this bug, redirect the needinfo to them
* If you cannot reproduce the bug, close it

All we need you to do is one thing that will help us make a decision on the bug or resolve it.

Thank you for your help with this. If you have questions, please contact emma@mozilla.com.
Flags: needinfo?(aryx.bugmail)
Whiteboard: [gfx-noted] → [gfx-noted][ele:1b]
Component: General → Security
Flags: needinfo?(aryx.bugmail)
Product: Core → Firefox
Is this still an issue? The linked ubuntu bug is marked as fixed.
Flags: needinfo?(elindarie)
(Reporter)

Comment 13

4 months ago
It's fixed.  I think you can mark it as status:resolved, resolution: fixed.  When I try to edit this bug, it doesn't give me the option to mark it as "fixed".

To fix it, see my comment #7 in this thread

https://bugzilla.mozilla.org/show_bug.cgi?id=1334748#c7

or 

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/comments/5.

Basically, just edit the file "/etc/apparmor.d/usr.bin.firefox" as follows:

Change

   owner /dev/shm/org.chromium.* c,

to

   owner /dev/shm/org.chromium.* rw,

Then, sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox
Flags: needinfo?(elindarie)

Updated

4 months ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.