Recovery of documents opens 2 versions: last save and a restore

[Ketil Wendelbo Aanensen]

On Jaunty.

I've experienced this twice now after a system freeze (most likely UXA related). I click the document I was working on from its icon on Gnome Do Docky, the recover document window opens, I run the wizard and a version of the document pops up after a short while. When I close that document, I see the same file open in OOo, and it's from a different save.

Another thing is that the recovered document is older than the manually saved one, but that's been reported earlier.

The problem here is that working on two copies of the same document makes people lose their work over and over, and this really needs to be fixed.

[Chris Cheney (ccheney)]

So are you saying that OOo somehow restored two different copies of the same document? Or how did you otherwise manage to make OOo open the same document twice? I can't seem to make it do that here.

[Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount)]

That is what I'm saying.

After the freeze, I started OOo by opening the file, like
$ oowriter /path/to/file
not like
$ oowriter

It is maybe possible that OOo opened the saved document as well as the restored document?

[Chris Cheney (ccheney)]

Ok, confirmed on Ubuntu version, need to test upstream now.

[Chris Cheney (ccheney)]

Verified on official 3.0.1 as well:

Steps:
1. open existing file
2. make sure autosave is set to a low number of min
3. make a few changes
4. kill soffice
5. reopen using the original file
6. notice after recovery that the original file and the recovered file are both open

[Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount)]

Thanks for confirming this so fast!

[penalvch (penalvch)]

Ketil Wendelbo Aanensen, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 351035
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Does LibreOffice work for you? If using Lucid or Maverick feel free to perform at the Terminal:

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-writer

[Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount)]

I'm sorry, but is there any chance that the above command will do anything with this bug? I mean, the bug report is 2,5 years old, I'm several versions of Ubuntu away, on a newer computer, and of course I'm now using LibreOffice.
A little late to the party this response, isn't it?

I love Ubuntu and open source software, but after 7-8 years of reporting bugs, I'm almost put entirely off. This is one of many examples of bugs being pushed around to confirmed (if even that), then nothing happens at all. Not trying to start up a debate about this on Launchpad (because I know it's not a forum), but I just think it reflects poorly on Ubuntu.

More in relation to this specific bug, I'm not going to vaste any time issuing any commands (whether they work or not) for a trivial bug that will not move any more the next 2,5 years.

I guess this can be changed to status "oldasdirtandnobodybotherswithitanymore", which seems to be a missing option. (At least that would be tongue-in-cheek.)

Sorry about the rant.

[penalvch (penalvch)]

Ketil Wendelbo Aanensen (ketilwaa), your correct that Launchpad is a developer and bug reporting venue, not a complaint forum. However, we are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!