Bug 1086162

Summary: Every documents in docx i dont open in libreoffice-4.2.3.3-1.fc20 (updates-testing)
Product: [Fedora] Fedora Reporter: Dandim <dan.dim>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: caolanm, dan.dim, dtardon, erack, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-11 16:05:02 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
libreoffice-bug none

Description Dandim 2014-04-10 09:23:06 UTC
Description of problem:
I update libreoffice from updates-testing to version libreoffice-4.2.3.3-1.fc20.
When i search document (its happen only in format docx) in dolphin and open it, Libreoffice start but not responding... I dont working with application. Only exit it.
But when a type "libreoffice" in terminal and select file from dialog, that works good.
Version-Release number of selected component (if applicable):
libreoffice-4.2.3.3-1.fc20

How reproducible:


Steps to Reproduce:
1. open every docx document
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dandim 2014-04-10 09:23:47 UTC
Created attachment 884821 [details]
libreoffice-bug

Comment 2 Stephan Bergmann 2014-04-10 09:32:16 UTC
The attached png makes it look like this is under KDE?  If it is, it might be related to bug 1085916.

Comment 3 Dandim 2014-04-10 09:38:02 UTC
Yes, Iam using KDE...

Comment 5 Stephan Bergmann 2014-04-11 16:05:02 UTC
I'll tentatively mark this as a duplicate of bug 1085916 for now (for which a fix should arrive shortly, see there).  Feel free to reopen this issue if the problem persists even after update.

*** This bug has been marked as a duplicate of bug 1085916 ***