Bug 75120 - FILESAVE: Save document is not working
Summary: FILESAVE: Save document is not working
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.0.alpha0+ Master
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 21:07 UTC by kevin.lewis210
Modified: 2014-10-05 22:59 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 kevin.lewis210 2014-02-17 21:07:50 UTC
Problem description: Saving a text doc is not working. I have copied & pasted work from one doc to another, renamed the new doc and closed it. Upon reopening the new doc NONE of my work is saved.

Steps to reproduce:
1. ….Open existing doc
2. ….Create new doc; copy/paste work from existing doc to new doc
3. ….Save & name new doc; close doc; reopen doc; work NOT saved. 

Current behavior: Not saving; VERY FRUSTRATING; lost 17 pages of work

Expected behavior: Work should be saved; I'm losing A LOT of information/work; I'm fucking pissed

              
Operating System: Mac OS X
Version: 4.3.0.0.alpha0+ Master
Comment 1 retired 2014-02-17 21:51:16 UTC
Hi Kevin, can you please attach the doc file in question so this can be tested against.

Tested here and things are fine with latest nightly on OSX 10.9.1.
Comment 2 Jorendc 2014-02-18 00:06:45 UTC
I hope you are wrong about your used version of LibreOffice...
Are you really using the most instable version (alpha/current master releases) for work related things? If so you should be <quote>fucking pissed</quote> at yourself in particular, not LibreOffice.

Although I fail to reproduce this loss of data, we can't make it more clear then we do now that those versions are for testing purposes only. Same story for betas, even RC versions and .0 releases.

As Foss mentions, can you provide a bit more information/the document in particular.
Comment 3 kevin.lewis210 2014-02-19 20:14:09 UTC
To whom it may concern:

I downloaded the latest version of Libreoffice before the problem occurred.
My operating system is Mac OS 10.7.5. I'm not sure why the problem
happened; I wasn't sure if it was Libreoffice or my computer or what. I
wanted to report the problem to Libreoffice just in case that was the
issue. Either way, I had every right to be "fucking pissed" since I had
lost 17 pages of information and I had to backtrack to try to recover as
much of the information as possible. I went back probably 4 times to find
the lost information, saved it every time, and it just wasn't saving in the
doc. Whatever the problem was, it doesn't seem to be happening anymore.

Anyway, I appreciate your help looking into this problem, and I apologize
for coming off rude.



Thank you,

Kevin Lewis
210-454-4026
kevin.lewis210@gmail.com

*CONFIDENTIALITY NOTICE: This communication is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is privileged, confidential, and exempt from disclosure
under applicable law. If you are not the intended recipient, you are
notified that any use, dissemination, forwarding, distribution, or copying
of the communication is strictly prohibited. Please notify the sender
immediately by e-mail if you have received this by mistake and delete this
e-mail from your system.*


On Mon, Feb 17, 2014 at 6:06 PM, <bugzilla-daemon@freedesktop.org> wrote:

>  Jorendc <jorendc@libreoffice.org> changed bug 75120<https://bugs.freedesktop.org/show_bug.cgi?id=75120>
>  What Removed Added  CC   jorendc@libreoffice.org
>
>  *Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=75120#c2> on
> bug 75120 <https://bugs.freedesktop.org/show_bug.cgi?id=75120> from Jorendc
> <jorendc@libreoffice.org> *
>
> I hope you are wrong about your used version of LibreOffice...
> Are you really using the most instable version (alpha/current master releases)
> for work related things? If so you should be <quote>fucking pissed</quote> at
> yourself in particular, not LibreOffice.
>
> Although I fail to reproduce this loss of data, we can't make it more clear
> then we do now that those versions are for testing purposes only. Same story
> for betas, even RC versions and .0 releases.
>
> As Foss mentions, can you provide a bit more information/the document in
> particular.
>
>  ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 4 QA Administrators 2014-09-03 21:32:32 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 5 QA Administrators 2014-10-05 22:59:43 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