Bug 1436682
Summary: | Unable to preview LOKDocView-supported documents from OneDrive | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Krajnak <mkrajnak> |
Component: | gnome-documents | Assignee: | Debarshi Ray <debarshir> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.4 | CC: | cosimo.cecchi, debarshir, elad, extras-qa, fedoraparked, jkoten, mkrajnak, pranav913, tpelka |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gnome-documents-3.22.2-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1394847 | Environment: | |
Last Closed: | 2017-08-01 10:01:37 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: | |||
Bug Depends On: | 1394847 | ||
Bug Blocks: | 1395724 |
Description
Martin Krajnak
2017-03-28 12:41:02 UTC
What kind of documents are you trying to access? I can open PDFs stored on OneDrive. PDFs are okay, but actual documents created by one drive - docx, pptx, xlsx are not working for me and they are working on 7.3 as I am executing the same tests. Would you be able to test the patches on the upstream bug? Communication with OneDrive is extremely flaky for me today, which makes it hard for me to test it thoroughly. So any help is welcome. I have built gnome-documents-3.22.2-2.el7: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12947638 I can confirm that LOCDocView documents are now rendered properly on x86_64, ppc64le, and aarch64. I haven't been able to test on s390x and ppc64 since there is no way to login to one drive account due to known webkit issue on big endian architectures. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2312 |