Red Hat Bugzilla – Bug 165406
oowriter cannot start from the shell given a new filename
Last modified: 2007-11-30 17:11:11 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
When I use a command such as
oowriter filename.odt &
at the command prompt, the program responds with a dialog box stating that the file does not exist. Oowriter does not start in this situation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Issue the oowriter command with the name of a new, nonexistent file as it's argument.
Actual Results: Dialog box appeared telling me that the file does not exist.
Oowriter does not start.
Expected Results: The program should have started, and created a new file for me given the filename, and it should take the file type based on the extension. If there is no extension, assume the default file type.
This is perhaps a small item, but it is really helpful to be able to create a new file on the fly. This would improve usability a lot for those who use the shell prompt.
Enhancement is more suitable for upstream, I've logged it as