Bug 109284 - Blind window "save as" after open doc or docx file
Summary: Blind window "save as" after open doc or docx file
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.4.2 release
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX DOC
  Show dependency treegraph
 
Reported: 2017-07-23 09:15 UTC by Christophe Laronde
Modified: 2018-09-03 14:56 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot (210.88 KB, image/jpeg)
2017-07-23 09:15 UTC, Christophe Laronde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Laronde 2017-07-23 09:15:14 UTC
Created attachment 134795 [details]
screenshot

After open .doc or .docx file, it is impossible to "save as..." : "save as" window is corrupted. The attachment shows what happen when I want to "save as".
Same error with 5.2.7 version.
It happens with french version
Comment 1 Alex Thurgood 2017-07-24 12:39:24 UTC
@Christophe :

1) Please indicate which version of OSX you are using.

2) Does your problem occur only with certain doc/docx files, or all files of that type ?

3) Preferably, it would be useful to have a sample document that shows the described behaviour - you can attach one using the "Add an attachment" link on this page.

No repro for me with :


Version: 5.3.4.2
Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3
CPU Threads: 4; OS Version: Mac OS X 10.12.6; UI Render: default; Layout Engine: new; 
Locale: en-GB (fr_FR.UTF-8); Calc: group
Comment 2 Alex Thurgood 2017-07-24 12:40:40 UTC
@Christophe : are you working in fullscreen mode by any chance ?
Comment 3 Christophe Laronde 2017-07-25 21:05:38 UTC
I hope I answer in the right field... (or perharps I have to add a comment ?)

1) Mac OS 10.12.6 french version.

2) The problem occurs after I open a doc/docx file, whatever

3) I joined a screenshot

4) I don't work in fullscreeen mode

5) Version: 5.3.4.2
Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3
Threads CPU : 4; Version de l'OS :Mac OS X 10.12.6; UI Render : par défaut; Moteur de mise en page : nouveau
Locale : fr-FR (fr_FR.UTF-8); Calc: group
Comment 4 Xisco Faulí 2017-11-13 17:08:00 UTC
To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?
Comment 5 Christophe Laronde 2017-11-13 21:48:47 UTC
(In reply to Xisco Faulí from comment #4)
> To be certain the reported issue is not related to corruption in the user
> profile, could you please reset your Libreoffice profile (
> https://wiki.documentfoundation.org/UserProfile ) and re-test?

I did what you propose : same bug.

I work now with LO Vanilla, made by Collabora (https://www.collabora.com/about-us/open-source/open-source-projects/libreoffice.html) via App Store
Comment 6 Xisco Faulí 2018-01-10 10:23:52 UTC
Hi Christophe,
Does it happen with an specific document or with all doc/docx?
Comment 7 QA Administrators 2018-07-31 09:38:16 UTC Comment hidden (obsolete, spam)
Comment 8 QA Administrators 2018-09-03 14:56:38 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180903