Bug 68237 - Crashing on File Save
Summary: Crashing on File Save
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-18 04:14 UTC by The Ravin'
Modified: 2014-06-01 20:30 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
attachment-7854-0.html (1.78 KB, text/html)
2013-08-19 15:54 UTC, The Ravin'
Details
attachment-7854-1.dat (1 bytes, multipart/alternative)
2013-08-19 15:54 UTC, The Ravin'
Details
A Simple Approach To The Bass Fretboard.odt (511.86 KB, application/vnd.oasis.opendocument.text)
2013-08-19 15:54 UTC, The Ravin'
Details

Note You need to log in before you can comment on or make changes to this bug.
Description The Ravin' 2013-08-18 04:14:29 UTC
I'm running LibreOffice 4.1.0.4 release on a DELL 15R (Intel i5 processor) laptop running Windows 8 (64-bit) with 8 GB of RAM.

I've been editing a document in Write that was created in MS Word on Windows 7. Before I encountered this problem today, I had already loaded, edited, and saved the document successfully in .odt format a few days ago.

It's a 26-page document with quite a number of illustrations. When I've worked on this document in the past, I was able to save each change sequentially without a problem. However, today the program crashes nearly every time I save the file. Sometimes it recovers, but only after 5 minutes or more, and mostly it doesn't recover at all. I have to shut it down and recover the document in order to save my changes.

At the time this occurred, I had QuickStart loading on Windows startup. I saw your bug ID 68082 (and 60668), so I exited QuickStart and unchecked the option to load it on Windows startup. Still crashes.

I really like LibreOffice, and since it looks like others are having the same problem, I really hope you can find a solution for us. Thanks!
Comment 1 retired 2013-08-19 14:28:50 UTC
Could you please attach the document in question? It's otherwise impossible to verify this bug (if it doesn't contain sensitive data).

If you see other bugs already covering this, please set this bug here to duplicate and subscribe yourself to the existing bug.
Comment 2 The Ravin' 2013-08-19 15:54:23 UTC
Created attachment 84252 [details]
attachment-7854-0.html

Here's the document you requested.

On 8/19/2013 7:28 AM, bugzilla-daemon@freedesktop.org wrote:
>
> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=68237#c1> 
> on bug 68237 <https://bugs.freedesktop.org/show_bug.cgi?id=68237> from 
> James <mailto:spam35@gmx.net> *
> Could you please attach the document in question? It's otherwise impossible to
> verify this bug (if it doesn't contain sensitive data).
>
> If you see other bugs already covering this, please set this bug here to
> duplicate and subscribe yourself to the existing bug.
> ------------------------------------------------------------------------
> You are receiving this mail because:
>
>   * You reported the bug.
>
Comment 3 The Ravin' 2013-08-19 15:54:24 UTC
Created attachment 84253 [details]
attachment-7854-1.dat
Comment 4 The Ravin' 2013-08-19 15:54:24 UTC
Created attachment 84254 [details]
A Simple Approach To The Bass Fretboard.odt
Comment 5 tommy27 2013-08-20 13:49:06 UTC
(In reply to comment #4)
> Created attachment 84254 [details]
> A Simple Approach To The Bass Fretboard.odt

I can edit and save this test document with no issues using LibO 4.1.0.4 on Win7 64bit.

try downloading the portable LibO version from here:
http://www.winpenpack.com/main/download.php?view.1354

and try loading your document in it. do you still experience those crashes?
Comment 6 The Ravin' 2013-08-20 16:31:44 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > Created attachment 84254 [details]
> > A Simple Approach To The Bass Fretboard.odt
> 
> I can edit and save this test document with no issues using LibO 4.1.0.4 on
> Win7 64bit.
> 
> try downloading the portable LibO version from here:
> http://www.winpenpack.com/main/download.php?view.1354
> 
> and try loading your document in it. do you still experience those crashes?

Thanks, Tommy. I'm wondering what's different about the "portable" version you recommend from the release version I got off the main website? I also wonder if your using it on Win7 is a good test, since I'm running Win8?

Also, I'm new to LibO, so I need to ask: If I try the version you recommend, do I need to first uninstall the release version I'm using? Or should I just install the portable version over the top of my current installation?
Comment 7 tommy27 2013-08-20 16:47:49 UTC
(In reply to comment #6)
> Thanks, Tommy. I'm wondering what's different about the "portable" version
> you recommend from the release version I got off the main website? I also
> wonder if your using it on Win7 is a good test, since I'm running Win8?

if you try a virgin portable version had it doesn't crash it means that something is wrong with your installation or user profile.

if it crashes the same way it means it's a Win8 specific bug.

> Also, I'm new to LibO, so I need to ask: If I try the version you recommend,
> do I need to first uninstall the release version I'm using? Or should I just
> install the portable version over the top of my current installation?

no. you should't uninstall anything nor overwrite it.
the portable version can run from any location (even an USB drive) but please use a different folder than your release installation
Comment 8 The Ravin' 2013-08-20 17:20:04 UTC
(In reply to comment #7)
> (In reply to comment #6)
> > Thanks, Tommy. I'm wondering what's different about the "portable" version
> > you recommend from the release version I got off the main website? I also
> > wonder if your using it on Win7 is a good test, since I'm running Win8?
> 
> if you try a virgin portable version had it doesn't crash it means that
> something is wrong with your installation or user profile.
> 
> if it crashes the same way it means it's a Win8 specific bug.
> 
> > Also, I'm new to LibO, so I need to ask: If I try the version you recommend,
> > do I need to first uninstall the release version I'm using? Or should I just
> > install the portable version over the top of my current installation?
> 
> no. you should't uninstall anything nor overwrite it.
> the portable version can run from any location (even an USB drive) but
> please use a different folder than your release installation

So, Tommy--the download you recommended attempted to install a Trojan on my system. Thank you very much!
Comment 9 The Ravin' 2013-08-20 17:30:16 UTC
IMPORTANT NOTICE! As someone new to LibreOffice, I'm discovering some of the potential dangers of open-source. I had a request from a "James" to upload the file I've been having problems with, so I did, thinking I was sending it to a development team looking into this bug. However, I see now that open source bug tracking appears to be from the global community, and the address for the "James" I sent my file to is called "spam35@gmx.net." 

Then I got info from a "Tommy27" (barta@quip.it) that I should download a "portable" version of LibO and try it. But the download attempted to install a Profiler Trojan on my system (fortunately trapped by McAfee). 

I'm pissed, and since I know that other people are having file save issues similar to mine, if you hear from either of these people or if you receive similar requests advice, DO NOT RESPOND!
Comment 10 tommy27 2013-08-20 17:38:52 UTC
@The Ravin' 
please, take a deep breath and calm down.

X-LibreOffice is a serious project and is the official portable release from the italian LibreOffice site:  https://it.libreoffice.org/download/portatile/

I don't know why you received a trojan alert downloading it but I suspect it's a false positive from your McAfee antivirus. I suppose you know what a "false positive" means with antivirus software, right?

I have that version on my computer and Avast antivirus has no issue with it.
Comment 11 tommy27 2013-08-20 19:33:20 UTC
(In reply to comment #9)
> IMPORTANT NOTICE! As someone new to LibreOffice, I'm discovering some of the
> potential dangers of open-source. 

you totally misunderstood the situation... there's no danger in an open-source project like LibO

> I had a request from a "James" to upload
> the file I've been having problems with, so I did, thinking I was sending it
> to a development team looking into this bug. However, I see now that open
> source bug tracking appears to be from the global community, and the address
> for the "James" I sent my file to is called "spam35@gmx.net." 

James is not a spammer. I don't why he has such an email address but he's not a spammer... I've seen many of his posts in the bug tracker and he never does spam.

this reminds me when I was in the US during the 9/11 period and a policeman wanted to inspect me because I had a t-shirt with KILLER LOOP text on it ( http://www.killerloop.com/ ). Believe it or not but he was suspicious because of the word "killer"... I had to explain it that it was just a sportswear brand and I had no intention of killing anybody.
Comment 12 tommy27 2013-08-22 08:03:52 UTC
(In reply to comment #8)
> 
> So, Tommy--the download you recommended attempted to install a Trojan on my
> system. Thank you very much!

I reported this to the winPenPack forum (authors of X-LibO) and to the italian OpenOffice/LibreOffice newsgroup and multiple users with different anti-virus found no virus inside it. I still think it's a false positive of McAfee.
Comment 13 Joel Madero 2013-08-22 15:26:32 UTC
It is a false positive - blame the closed source virus scanner instead of our product. Send them an email telling them to cool off their bs false positives which freak out noobs and people who don't know much about computers.
Comment 14 Julien Nabet 2013-08-23 05:13:51 UTC
The Ravin: if you prefer not testing portable version, you can rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile).
It'll allow to know if the bug is due to LO customization.

For the rest, I confirm there may have some false positives about virus, just take a look to this list:
https://bugs.freedesktop.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__closed__&product=LibreOffice&content=virus&list_id=336750

About James, he's not a spammer. I suppose he has several emails to manage his emails more easily.

Also, do not answer from your emailer but by using these links:
- https://bugs.freedesktop.org/show_bug.cgi?id=68237# (to add a comment)
- https://bugs.freedesktop.org/attachment.cgi?bugid=68237&action=enter (to add an attachment with a comment)
And yes attachments can be seen by anybody.

Finally to remove this attachment, since we're not able to do this, please take a look at this:
https://bugs.freedesktop.org/show_bug.cgi?id=57005
In brief:
Create a Bug Product=freedesktop.org, Component=Bugzilla and ask for deletion of particular contents
Comment 15 tommy27 2013-08-23 12:27:35 UTC
is there any  Windows 8 (64-bit) user who can check the test document?
as I said before I do not reproduce any crash on Win7 (64-bit)
Comment 16 The Ravin' 2013-09-08 21:40:39 UTC
UPDATE ON POTENTIAL TROJAN INSTALL (see note below): In spite of seemingly well-meaning reassurances that the trojan install I experienced a couple of weeks ago was a "false positive," I have been dealing with recurrent malware issues ever since then. I'm hoping that by now I have it finally cleaned up, but (a) it's simply too coincidental that malware got installed (I'm pretty careful about what I install and how the process goes) at the same instant as a "false positive" from McAfee, and (b) I've been using McAfee for several years now, and it has not, to my knowledge, ever given a false positive before. I'm not claiming the evidence is conclusive that anyone intentionally attempted to compromise my system, but the detection of a trojan from the pocket office download and the subsequent ongoing malware infection is too coincidental to ignore. I'm still using LibreOffice and hoping for a resolution to the issue I reported, but I can only say for other users to be VERY CIRCUMSPECT about downloading anything recommended by "helpful" users (even if they might actually be well-intentioned).
Comment 17 tommy27 2013-09-08 22:02:45 UTC
As said before, X-LibO doesn't contain any malware. I think that you downloaded something else from an advertising banner on the X-LibreOffice webpage. 

The correct download button for X-LibO is the one with the drive icon with the blue arrow. Other banners with "green download buttons" are ad-ware and could contain the trojan you reported. 

I have an "ad-block" extension on my browser which automatically hides those ad-ware banners, but now that I've temporarily disabled that extension I see that you probably clicked on the wrong icon.

I'm sorry that you experienced subsequent issues but it's the job of your McAfee anti-virus to protect you against infections... if you still experience troubles after that try using another antivirus.
Comment 18 Joel Madero 2013-09-08 23:59:20 UTC
Please in the future do not bring up other issues on bug reports that are unrelated.

We have already said that LibreOffice is not a trojan, doesn't contain a trojan and doesn't get installed with malware. By putting these things in comments on unrelated bugs you are just clogging up comments and making it harder to focus on the issue at hand - which here appears to be a crash on file save.

If you need tech support for your malware issues I suggest finding a local shop to take a look.
Comment 19 tommy27 2013-09-09 07:36:13 UTC
@The Ravin'
you should try upgrading to LibO 4.1.1.2 and tell us if you still face that issue with your document.

nobody here was able to replicate it but there's no been any Win8 64bit tester yet.
Comment 20 The Ravin' 2013-09-09 15:40:02 UTC
(In reply to comment #19)
> @The Ravin'
> you should try upgrading to LibO 4.1.1.2 and tell us if you still face that
> issue with your document.
> 
> nobody here was able to replicate it but there's no been any Win8 64bit
> tester yet.

Thanks, Tommy -- I installed 4.1.1.2, and the problem still exists. It does seem to recover after a long, long wait -- maybe 5 minutes or more. 

Is there really no one else working on LibreOffice who has Win8(64)? As you're aware from having a copy of the doc in question, it contains numerous graphical insertions, but I suspect the problem has to do less with that than with LibreOffice on my particular platform. 


I've used OpenOffice occasionally for a long time without problem, though I may never have tried this particular document with OpenOffice--can't recall. I also don't seem to have any problem with other documents in LibreOffice, though I haven't had occasion to try it extensively so far, especially with pasting in lots of graphics. I'll keep experimenting on my end, and appreciate the efforts to resolve the issue.

I do feel I need to say a word about myself and the comments by you and others regarding my experience. I'm a retired SysAdmin and have been using or supporting PC's since their inception in the early '80's. I've had extensive experience with every version of Windows desktop and server since 3.0, installing, configuring, networking, supporting, etc., until my retirement 6 years ago. So, while I'm sure I'm not up on the latest OS and software developments, I'm not moronic enough to have clicked on the wrong download link, as some of you seem to presume. I'm not a programmer, and I can certainly make mistakes (like anyone else), but I do pretty much know what I'm doing with PC's.

I'm also as sympathetic, even committed, to the philosophy of open source software. However, every time I've tried it (various types and versions over the years), I've found open source to be more problematic than commercial software. Except for early use of WordPerfect, I've always used MS Office because of my sysadmin work in collaborative workgroups. OpenOffice was never able to quite match the collaborative features of MS Office. I've always deplored the proprietary nature and expense of MS licensing, however, and I no longer need the collaborative features of MS Office.

So I'd appreciate it if you'd please try not to pre-judge the abilities or experience of me or other users. I still do not believe that the trojan installation was a "false positive," especially since I began having trouble with malware at precisely the same time. I don't accuse you or anyone else of intentional maliciousness, but while I can't (and shouldn't have to) explain what happened when I tried to download PocketOffice from the link you provided, what I experienced was real and not the result of ignorance on my part.

I apologize for the long diatribe, but I do feel that the attitudes of you and others involved here have been somewhat prejudicial and even bordering on insulting. This is not helpful. I'm a good-faith user with a significant problem that others have clearly experienced as well. I'm still here, still hoping for a solution, and still willing to help where I can. So, maybe we can all treat each other with respect and get on solving the problem now...? Again, I do appreciate the ongoing efforts by you and others, but I also defend my (and other users') legitimate right to feel somewhat pissed about the trojan thing. It wasn't stupidity or imagination.

Seems to me the next step is to try it on a Win8(64) platform.
Comment 21 The Ravin' 2013-09-09 15:57:40 UTC
(In reply to comment #18)
> Please in the future do not bring up other issues on bug reports that are
> unrelated.
> 
> We have already said that LibreOffice is not a trojan, doesn't contain a
> trojan and doesn't get installed with malware. By putting these things in
> comments on unrelated bugs you are just clogging up comments and making it
> harder to focus on the issue at hand - which here appears to be a crash on
> file save.
> 
> If you need tech support for your malware issues I suggest finding a local
> shop to take a look.

Joel, with all due respect, I believe my comments are NOT peripheral to this case, but completely relevant, because the trojan/malware issues I've been having are the direct result of my following the instructions provided here. 

I'm a highly experience user, and I did NOT make a stupid or ignorant mistake, as you seem to presume. 

I hear and appreciate your insistence that LibreOffice is not a point of infection, but I also need an explanation as to why explicitly following the instructions provided in this forum led to my computer being infected in the process. Also, I know how to clean up a malware infection--I've cleaned up many, myself, in my years as SysAdmin--and I know I can always take my system in to a local shop. 

I'd suggest that, instead of presupposing my own incompetency and responding defensively, you all focus on figuring out how & why my machine got infected with malware and why I and others are having this problem saving files. 

I'm here to help with that, if I can. I do sincerely sappreciate that you and others are working on this problem, but you need to realize that I and other users are not interested in jumping through a lot of hoops to solve technical problems--we just want to USE the software, not fix it. 

I do believe the problem is probably Win8 specific (maybe also b/c 64-bit OS?), and, since you have a copy of the offending document I provided, I think the problem needs further testing on that specific platform, instead of supposing that I did something stupid.
Comment 22 Joel Madero 2013-09-09 16:28:28 UTC
I had no presumption as to your knowledge, only repeating what was already stated.

As to you only wanting to use the software - open source is about collaboration, in order for the software to work we need users to stop thinking that they should just be "using" and instead feel like they want to be a part of a community - else we end up with situations like we have now with millions of users and a QA team that is less than 25 people strong.....the ratio is horrendous

That being said, thanks for the additional input and for taking the time to be frank, I (and the QA team as a whole) always appreciate constructive feedback
Comment 23 tommy27 2013-09-09 21:56:59 UTC
@The Ravin'
I find very disappointing that you still insist saying that X-LibreOffice contained a trojan. 

facts are:
................................
1- you had troubles with a document that anybody here seems to open with no issues. your problems existed before downloading X-LibO and you said that tew days before experiencing the bug, your standard LibO installation was able to laod and save it. 

have you ever thought that LibO malfunctions could be caused by a damage in your O/S?

................................

2- I suggested you to try X-LibreOffice (I do not know what is that Pocket Office that you mentioned before) and you claimed that it tried to install malware, while nobody here, in the italian LibO newsgroup and in the winPenPack forum (see topic: http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?57332) has found anything suspicious after testing it on several virus scanner. 

so I still suspect that you clicked on the wrong download button and did not realize you were downloading something else... 

are you really sure that when you visited this page: http://www.winpenpack.com/main/download.php?view.1354 and clicked on the blue arrow with drive icon just?

are you really sure that it opened a sourceforge page with a download countdown to download a file called: "X-LibreOffice_4.1.0_rev16.zip" ? 

do you remember which file McAfee said it had a trojan inside?

................................

3- regarding your computer competence I cannot say neither that you are an experience user or a newbie... but I have to say that some of your comments were really naive... When you wrote that "IMPORTANT NOTICE" alerting people that James' email address contained the word "spam" I could not believe my eyes...
................................

having said that, I'd be glad to test your document on a Win8 PC if I had one...

what I can say that I still load, edit and save your document with no crash using X-LibreOffice 4.1.1 and, most important my antivirus sees no trojan in X-LibO and my system has no malware issue after that.
Comment 24 Julien Nabet 2013-09-11 20:21:20 UTC
The Ravin:
could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a new try?
If you still reproduce, could you try to retrieve extra information by following this link?
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
Comment 25 QA Administrators 2014-05-17 00:34:32 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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 26 QA Administrators 2014-06-01 20:30:29 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