Bug 97234 - LibreOffice 5.1.0.2 crashes during first opening of Impress by selecting Wizard
Summary: LibreOffice 5.1.0.2 crashes during first opening of Impress by selecting Wizard
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.1.0.2 rc
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-18 18:50 UTC by Leopoldo Saggin
Modified: 2016-11-08 12:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leopoldo Saggin 2016-01-18 18:50:02 UTC
I got the same results using both LibO 5.1.0.1RC and 5.1.0.2RC.
Moreover I got these results on 2 different computers both using Windows 10 Pro 64 bit (Fall 2015 edition).
What I did in the 3 cases to have the crash.
1. I updated LibO from 5.0.4.2 to 5.1.0.2 (English version in all the cases).
2. I opened the Writer with an empty doc
3. I opened Calc with an empty doc
4. I opened Impress with an empty doc.
At this point in Impress I chose File -> Wizard and I selected in this order:
a. My Templates (I have none)
b. Presentation (progressively selecting all of them to see their preview)
c. Presentation Backgrounds (progressively selecting all of them to see their preview)
When I reached the backgroiund named Metropolis (or maybe Sunset) ie one of the last of the list,  LibO crashes.
In one case a window reporting "unknown SEH exception" appeared.
If I restart LibO, recover (or unrecover documents crashed) and I repeat the same sequence of operation I did not have crashes anymore like something was "initialized" with the first opening even if it ended with a crash.

Regards,
Topoldo/Leopoldo Saggin
Comment 1 Buovjaga 2016-01-25 11:59:17 UTC
I am unable to make it crash.

Have you enabled Tools - Options - LibO - View - Use OpenGL for all rendering? If yes, try disabling it and restarting LibO.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: 6b65a0e83c4798f117be61af91dbaebdc85e94b7
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-01-21_03:41:08
Locale: fi-FI (fi_FI)

Version: 5.1.0.2 (x64)
Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)
Comment 2 Leopoldo Saggin 2016-01-25 12:14:15 UTC
You wrote:

> Have you enabled Tools - Options - LibO - View - Use OpenGL for all rendering?
> If yes, try disabling it and restarting LibO.

No I haven't.
Anyway it is not so important. I have some more crashes while using writer & Calc standard documents which di not give me any problems with 5.0.x versions which ara mora important to solve but I cannot document because the happened randomly so I cannot submit them.
Comment 4 Leopoldo Saggin 2016-01-25 12:20:55 UTC
Oops... I gave an undesidered <Enter> in the previous message! :-(
Anyway I was saying I had quite a lot of crashes with the need to recovery documents (the same documents I need to update daily that worked fine with LibO 5.0.x), so I probably downgrade to LibO 5.0.x until 5.1.x will provide much more stability.
Regards,
Topoldo/Leopoldo Saggin
Comment 5 Leopoldo Saggin 2016-01-25 12:22:44 UTC
You wrote:
> Please try https://wiki.documentfoundation.org
> /UserProfile#Resolving_corruption_in_the_user_profile

I think this is not the case because it happened on 3 different computers...
Topoldo/Leopoldo
Comment 6 Buovjaga 2016-01-25 12:42:44 UTC
Please try to get a backtrace, then: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 7 Buovjaga 2016-03-02 21:11:05 UTC
Please test with 5.1.1, which will be released soon. You can try it out by installing with this: https://wiki.documentfoundation.org/SI-GUI

And a bt per my previous comment would be great, if it still happens.

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 8 Xisco Faulí 2016-10-10 11:24:22 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2016-11-08 12:50:45 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-20161108