oowriter doesn't behave like ooffice -writer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openoffice.org (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: openoffice.org
Hello,
I just discover a nice thing with OOo :
trying to get ride of gvfs problem, I tried to launch it in several ways :
* through terminal (urxvt, hardy version) : "oowriter <doc.odt>" and "ooffice -writer <doc.odt>"
* through launcher : "oowriter" and "ooffice -writer"
I created a new document, saved it on a samba share. so far, so good. Then I exported it to PDF, in the same smb directory. So far, so good, no error [both with oowriter and ooffice -writer]
Then, close OOo, reopen it, open the same file, edit it, save... ok, no problem. Export it to pdf, same place and name as the previous export. HERE we have a problem :
1- with oowriter : no error BUT it doesn't ask if we really want to override the file
2- with ooffice : ask if we want to override the file, BUT crashes with some I/O error....
Is it normal? I thought oowriter was a "link" to ooffice -writer [or to soffice.bin maybe], and thus should behave the same...
I don't know for now if it's only a problem on ubuntu. I'll try on another linux distro this evening.
any news? maybe it's an upstream bug... ?