[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2019-07-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83263

--- Comment #16 from Jason Lee  ---
That's why you should have used
https://spinbackup.com/products/google-apps-backup/ from Spinbackup. They would
not have allowed your data to get corrupted. My opinion is that its the best
product in the business. I hope that you will take some time to check it out.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2019-07-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83263

--- Comment #15 from Jason Lee  ---
That's why you should have used
https://spinbackup.com/products/google-apps-backup/ from Spinbackup. They would
not have allowed your data to get corrupted. I hope that you will take some
time to check it out.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2015-01-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #13 from Lionel Elie Mamane lio...@mamane.lu ---
I'm sorry your data file got corrupted. Since we don't know how to reproduce
it, realistically I don't think much will happen.

The corrupted file is not even recognised by file as a ZIP file anymore.

I treated the corrupted file with zip -F, and then it opened correctly, table
and report.

I'm not sure what to do QA-wise to this bug... I recognise it happened, but
keeping it open without clear reproduction steps is not going to achieve
anything. Robinson, what's your opinion?

(In reply to robert from comment #8)
 There should be a permanent backup from the *.odb-file to the backup-folder
 of LibreOffice.

There is an autosave every XX minutes; that's what the autorecovery uses; AFAIK
one can just copy the autosave file before restarting LibreOffice; I think it
is somewhere in ~/.config/libreoffice/4/. See tools / options / load/save /
general / save autorecovery information every XX minutes.



(In reply to robert from comment #8)
 (In reply to Alex Thurgood from comment #7)
 Thoughts on embedded hsqldb and known legendary instability ? 

 It isn't the instability of HSQLDB. Most of the problems appear while the
 data were saved in the same packed file as all other things. It wouldn't be
 better with an internal Firebird.

I'm not so sure. Embedded HSQLDB does rather horrible tricks to fake that the
database is saved to the odb after each transaction; I wouldn't be too
surprised if the file corruption problems came from there. Embedded Firebird by
design does not (and requires a save to save the data in the odb file).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2015-01-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Robinson Tryon (qubit) qu...@runcibility.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #14 from Robinson Tryon (qubit) qu...@runcibility.com ---
(In reply to Lionel Elie Mamane from comment #13)
 I'm not sure what to do QA-wise to this bug... I recognise it happened, but
 keeping it open without clear reproduction steps is not going to achieve
 anything. Robinson, what's your opinion?

We really need to be able to reproduce the problem to try to track down what
caused it. We could stick this bug in NEEDINFO for a while, but I'm going to
just go ahead and RESOLVE it as WORKSFORME, as we can't reproduce the problem
by following the steps.

Rainer: If you experience this bug again, please leave another comment. It's
really helpful that you've filed this report, as this provides more information
in the event that someone else runs into the same bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2015-01-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Robinson Tryon (qubit) qu...@runcibility.com changed:

   What|Removed |Added

 CC||qu...@runcibility.com

--- Comment #12 from Robinson Tryon (qubit) qu...@runcibility.com ---
(In reply to Rainer Rillke from comment #0)
 File opens as writer document despite it should be a database (see bug
 report)
 ...
 FILESAVE: Corrputed database file when saving

Can we reproduce the problem of getting a corrupted database file when saving?

What's next here?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2015-01-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #11 from Alex Thurgood ipla...@yahoo.co.uk ---
Adding self to CC if not already on

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-12-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Julien Nabet serval2...@yahoo.fr changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #10 from Julien Nabet serval2...@yahoo.fr ---
It won't solve the problem but upgrading to last stable LO version, ie 4.3.4,
may help a bit.
Indeed, 4.3.0.4 is the first non Beta version of 4.3 branch.
Again, it's not the solution, just a start.

About hsqldb, hope an upgrade from 1.8 to 2.3 release (I don't know when) may
help to improve LO stability waiting by the full adoption of Firebird which may
take some time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Michael Stahl mst...@redhat.com changed:

   What|Removed |Added

 CC||mst...@redhat.com

--- Comment #9 from Michael Stahl mst...@redhat.com ---
the unzip tool complains about various errors in the attachment - very odd,
i've never seen that before (but then i rarely look at Base bugs).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Michael Stahl mst...@redhat.com changed:

   What|Removed |Added

 Attachment #105448|text/plain  |application/vnd.oasis.opend
  mime type||ocument.database

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-12-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Michael Stahl mst...@redhat.com changed:

   What|Removed |Added

 Attachment #105449|application/octet-stream|application/vnd.oasis.opend
  mime type||ocument.database

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-10-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #7 from Alex Thurgood ipla...@yahoo.co.uk ---
Thoughts on embedded hsqldb and known legendary instability ? IMHO this has
been known for years, the forums and mailing lists are rife with people
complaining about mangled data, that should be warning enough - the problem
pre-existed the creation of the LO project, ever since Sun took the decision to
integrate the hsqldb engine as default, back when OOo 2 was released, so at
least 10 years.

Of course, it is inherently problematic that embedded hsqldb remains the
default, but until we have a suitable replacement, there's probably not much we
can do about that with current resources.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-10-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #8 from rob...@familiegrosskopf.de ---
(In reply to Alex Thurgood from comment #7)
 Thoughts on embedded hsqldb and known legendary instability ? 

It isn't the instability of HSQLDB. Most of the problems appear while the data
were saved in the same packed file as all other things. It wouldn't be better
with an internal Firebird.

Most instable element of Base is the Report-Builder, and there the crating of a
report. When I create a report I press very often the Button to save all this
to to the Base-File and the from the Base-GUI to the harddisk.

There should be a permanent backup from the *.odb-file to the backup-folder of
LibreOffice. It would help to save data. You could find this as a macro in the
Base-Handbook.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-31 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #5 from rob...@familiegrosskopf.de ---
Have had a look at the database-file. When I extract the whole file there isn't
extracted the mimetype-information of the *.odb-file.

So I took an empty new database, put all the content of database, reports,
content.xml and settings.xml instead of the content of the new database-file
into the packed file and could open the *.odb-file with a table Microspecies
(141 rows) and a report, which couldn't be opened.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-31 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Joel Madero jmadero@gmail.com changed:

   What|Removed |Added

 CC||lio...@mamane.lu

--- Comment #6 from Joel Madero jmadero@gmail.com ---
@Lionel - any thoughts on this one?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #3 from Rainer Rillke rainerril...@hotmail.com ---
(In reply to comment #2)
 Please understand that our goal is to reproduce problems so that we can
 diagnose what went wrong - just saying this happened doesn't give us
 anything to reproduce by.

For this reason, I attached the corrupted odb file. I guess someone with
sufficient knowledge of this file format can very easily find out the reason it
opens now with writer instead of base. So what does it mean if it starts with
writer? That the zip file was not fully written or that some file inside the
archive is corrupt. Note that the more information you I have, I will me more
likely to get an idea how to reproduce it.

Apart from that, I still suggest to add a warning to the UI on first use that
base is not stable/ and or always create backups of the whole odb file *by
default*. This seems to be justified as a query for corrupt base files
https://bugs.freedesktop.org/buglist.cgi?order=Importancelist_id=462365short_desc=corruptquery_format=advancedbug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTshort_desc_type=allwordssubstrcomponent=Databasecomponent=Libreofficeproduct=LibreOffice
returned 36 bugs, the majority of them created less than 12 months ago. Given
that base is certainly less extensively used than writer or calc, I bet this is
enough evidence.

Please note that some bugs are inherently hard to reproduce (see bug 75717 for
example), if they for example need a complex chain of actions in advance to
enter in corrupt state, or time-dependent bugs, e.g. only happening on high CPU
load by other programs, etc.

Joel, considering the bug's description, can you recommend me a tool assisting
me detecting whether libre office enters into a broken state (e.g. buffer
overflows, other debugging tools and information)? BTW, reading Bug 60880#c10
it seems to me that this message could be improved linking to those tools able
to assist debugging LO for newcomers. Do you recommend me filing bugs like that
in future, even if I am unable to reproduce? I just wonder whether it's worth
the efforts, OTH I think it's important to somehow track the occurrences of
issues like that?

Seeing other bug reports about corrupted files, I'd like to mention that my
file system otherwise works well. The file was located on a local ntfs system;
the drive is a relatively new SSD.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Joel Madero jmadero@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |---

--- Comment #4 from Joel Madero jmadero@gmail.com ---
We're not going to add a warning - the software comes with a license that says
basically comes as is. We're not even sure how this happened so adding some
generic warning that stuff might happen is not useful for anyone. That being
said - you're right, maybe the db is sufficient for a developer to see what
happened. Moving back to UNCONFIRMED for now

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Rainer Rillke rainerril...@hotmail.com changed:

   What|Removed |Added

Summary|FILESAVE: Corrputed |FILESAVE: Corrupted
   |database file when saving   |database file when saving

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

--- Comment #1 from Rainer Rillke rainerril...@hotmail.com ---
Created attachment 105449
  -- https://bugs.freedesktop.org/attachment.cgi?id=105449action=edit
File recovered by merging the report from the corrupt file into an old copy
from %temp%

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Rainer Rillke rainerril...@hotmail.com changed:

   What|Removed |Added

   Hardware|Other   |x86-64 (AMD64)
 OS|All |Windows (All)
Version|unspecified |4.3.0.4 release

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83263] FILESAVE: Corrupted database file when saving

2014-08-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=83263

Joel Madero jmadero@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID
 CC||jmadero@gmail.com

--- Comment #2 from Joel Madero jmadero@gmail.com ---
Unfortunately without more there's really nothing we can do. Closing as
INVALID. If you can get reproducible steps together please feel free to add
them and then set the bug back to UNCONFIRMED.

Please understand that our goal is to reproduce problems so that we can
diagnose what went wrong - just saying this happened doesn't give us anything
to reproduce by.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs