Bug 1313244 - NetFlix does not work, if fedora-user-agent-chrome is installed
NetFlix does not work, if fedora-user-agent-chrome is installed
Product: Fedora
Classification: Fedora
Component: fedora-user-agent-chrome (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Tomas Popela
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-03-01 03:56 EST by customercare
Modified: 2016-03-01 06:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-03-01 06:49:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description customercare 2016-03-01 03:56:31 EST
Description of problem:

NetFlix with google-chrome does not work, if fedora-user-agent-chrome is installed.

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

How reproducible:


Steps to Reproduce:
1. install google-chrome-stable
2. start it,log into netflix, start playback -> Error m7111-1957-205032
3. stop chrome, deinstall fedora-user-agent-chrome
4. start it,log into netflix,
5. erase cookies https://netflix.com/clearcookies
6. start playback
7. works.

Actual results:

unusable NetFlix

Expected results:

normal behavior.

Additional info:

Why was it installed ?
Why can it not be configured ?
Why do we have to erase it ? deactivating it, did not do the trick. It's pure existance stopped NetFlix from working.

What does it do, to have an impact by pure existence ? 

Chrome obviosly does not need it .
Comment 1 Tomas Popela 2016-03-01 06:49:22 EST
thank you for your bug report. The issue was fixed with commit [0] and the new version including the fix is already being published to Chrome Store.

[0] - https://github.com/tpopela/fedora-user-agent-chrome/commit/7d36204e00e844754f582ebb28feb89068a592f6

For the rest of your questions please look at bug 1266569.

Note You need to log in before you can comment on or make changes to this bug.