Bug 75926

Summary: EDITING: after having worked fine for weeks it now seems to be going to a loop within soffice.bin*32.
Product: LibreOffice Reporter: kengraebe
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: kengraebe
Priority: medium    
Version: 4.2.0.4 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:

Description kengraebe 2014-03-08 22:29:19 UTC
blue circle soon after loading.LO
later the LO screen becomes gray.
nothing works until task manager is used to end the process.
system restart does not resolve.
more than 1 document has the same result.

has this been addressed in a later release?

thanks for any help you can provide.
Operating System: Windows 7
Version: 4.2.0.4 release
Comment 1 kengraebe 2014-03-09 04:19:59 UTC
downloaded 4.2.1.1     problem remains.  i suspect windows, not LO.  what now???    ken
Comment 2 kengraebe 2014-03-09 15:32:36 UTC
in further research I find that if I do not recover the file in question, I can then open and work on other ODT files.  therefore the problem is not windows but something about a particular file which causes soffice.bin*32 to consume 50% of the processor which might be waiting for windows to do something.
Comment 3 Björn Michaelsen 2014-03-28 00:26:01 UTC
Please attach the file that causes the looping.
Comment 4 kengraebe 2014-03-28 04:26:09 UTC
sorry I failed to provide an update.  the problem was a corrupted file.  my so called bug was corrected by reloading an older version from dropbox and hoping that I've remembered all the changes.  thanks for reminding me.    ken


----- Forwarded Message -----
>From: "bugzilla-daemon@freedesktop.org" <bugzilla-daemon@freedesktop.org>
>To: kengraebe@yahoo.com 
>Sent: Thursday, March 27, 2014 8:26 PM
>Subject: [Bug 75926] EDITING: after having worked fine for weeks it now seems to be going to a loop within soffice.bin*32.
> 
>
>
> 
>Björn Michaelsen  changed bug 75926 
>
>What
>Removed
>Added
>Status UNCONFIRMED  NEEDINFO  
>Ever confirmed    1  
>Comment # 3 on bug 75926 from Björn Michaelsen  
>Please attach the file that causes the looping.
>________________________________
> You are receiving this mail because: 
>	* You are on the CC list for the bug.
>	* You reported the bug.
>
>
Comment 5 QA Administrators 2014-10-05 23:05:53 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 6 QA Administrators 2014-11-02 16:43:22 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