Bug 58515

Summary: undefined: LO Impress 4.0.0.0.beta1-11 crash
Product: LibreOffice Reporter: Simón Alonso Sanchez <simonalsa>
Component: ImpressAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal    
Priority: medium    
Version: 4.0.0.0.beta1   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: soffice bugreport impress 20121219

Description Simón Alonso Sanchez 2012-12-19 12:17:57 UTC
Created attachment 71801 [details]
soffice bugreport impress 20121219

Problem description: LO Impress 4.0.0.0.beta1-11 crash

Steps to reproduce:
1. Make a new LO Impress document
2. Save the LO Impress document to disk
3. Print the LO Impress document
4. Exit the LO Impress closing it by "X" button



Current behavior:
I tried to reproduce it before but i can not do it.

Expected behavior:
Close successful
              
System: Linux 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 1045946368 vsize: 1045946368 resident: 242106368 share: 84344832 rss: 242106368 rss_rlim: 18446744073709551615
CPU usage: start_time: 1355916915 rtime: 12375 utime: 11649 stime: 726 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/lodev4.0/program/soffice.bin'
...
...
...
Operating System: Linux (Other)
Version: 4.0.0.0.beta1
Comment 1 Rob Snelders 2012-12-20 18:19:07 UTC
I can't reproduce it.

Please state clearly if you can reproduce it. When you can't then we can't see what the problem was and can't solve the problem, so I'll have to close the problem.
Comment 2 Gaetano Giunta 2013-01-15 17:42:05 UTC
Not sure if it is related, but:

LO 4.0.0 rc 1 is very crashy upon opening/closing/saving docs (created with olders OOO/LO versions).

Symptoms:
- open doc, close OO => .lock file stays on disk. When restarting Lo, it asks to recover documents
- open doc, change visibility of a slide, try to save it => LO crashes

I can not reproduce this reliably, only about 50% of time.
If needed, I can provide some sample docs

Tested on win7 64bit (+tortoisesvn)
Comment 3 QA Administrators 2013-09-24 01:54:37 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 QA Administrators 2013-10-25 15:13:17 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO