oowriter doesn't behave like ooffice -writer

Bug #261148 reported by Cédric Jeanneret deactivated
6
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.

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

any news? maybe it's an upstream bug... ?

Revision history for this message
Neil Munro (neilmunro-deactivatedaccount) wrote :

Thank you for your bug report I have followed your steps to reproduce this bug, I however cannot save files to a samba share, so did it locally to my Desktop folder.

Launched both commands via terminal saving a file to my desktop: Passed.

Saved file as PDF from terminal with both commands: Passed.

Closed writer and opened it with both commands, edited it and saved it with both commands: Passed

Export to PDF with both commands: Failed.
     With both commands I AM presented with an overwrite dialog.

I have attached a screen shot of this happening, I can't reproduce your error through terminal commands or using the menu.

Revision history for this message
Neil Munro (neilmunro-deactivatedaccount) wrote :

I tried on ubuntu 8.04 with open office 2.4.1.

Can you try again and see if this still occurs?

Changed in openoffice.org:
status: New → Incomplete
Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

Hello,

in fact you can't reproduce these errors if you don't have a samba share. here at work, we use a fileserver with smb sharing, and thus we have these problems. even on hardy, latest versions...
Sure if you use directly your filesystem, it works really fine.

Regards,

C.

Revision history for this message
Neil Munro (neilmunro-deactivatedaccount) wrote :

Marked as new since I have no method in which to confirm this, someone else will have to.

Changed in openoffice.org:
status: Incomplete → New
Revision history for this message
Chris Cheney (ccheney) wrote :

I'm not sure why it would work differently. I will have to set up a test smb share to see if I can reproduce it later.

oowriter
==
#!/bin/sh
/usr/lib/openoffice/program/soffice -writer "$@"

ooffice
==
#!/bin/sh
/usr/lib/openoffice/program/soffice "$@"

Revision history for this message
Chris Cheney (ccheney) wrote :

Do you still have this problem with openoffice.org 1:2.4.1-11ubuntu2 in Ubuntu 8.10?

Changed in openoffice.org:
status: New → Incomplete
Revision history for this message
Chris Cheney (ccheney) wrote :

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!

Changed in openoffice.org:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.