Hi,
I have installed OpenOffice 3.1 downloaded from the openoffice.org website on CentOS 5.4 x86_64.
The downloaded file is actually an archive containing RPMs. I did not use their setup tool but installed directly the RPMs I was interested in via 'yum localinstall' (my idea is in the future to put them on a custom yum repository, so that they can be managed via regular yum install / update).
It works fine, except that when I double-click on, say, *.odt files in the file browser I get the following exception:
Cannot open xxxxxxx.odt The filename "xxxxxxx.odt" indicates that this file is of type "odt document". The contents of the file indicate that the file is of type "OpenDocument Text".
If I do a right-click, Open with... > Open Office Writer 3.1, it opens the file properly.
1. Did anybody already experienced that? 2. Do you know where I can manage the file types in GNOME?
I have already added Open Office 3.1 as the default application to open such files (Right-click, Properties > Open With)
Thanks in advance!
Mathieu
Mathieu Baudier wrote:
Hi,
I have installed OpenOffice 3.1 downloaded from the openoffice.org website on CentOS 5.4 x86_64.
The downloaded file is actually an archive containing RPMs. I did not use their setup tool but installed directly the RPMs I was interested in via 'yum localinstall' (my idea is in the future to put them on a custom yum repository, so that they can be managed via regular yum install / update).
It works fine, except that when I double-click on, say, *.odt files in the file browser I get the following exception:
Cannot open xxxxxxx.odt The filename "xxxxxxx.odt" indicates that this file is of type "odt document". The contents of the file indicate that the file is of type "OpenDocument Text".
Did you install the relevant rpm from the desktop-integration folder?? This has fixed these issues for me previously
If I do a right-click, Open with... > Open Office Writer 3.1, it opens the file properly.
- Did anybody already experienced that?
- Do you know where I can manage the file types in GNOME?
I have already added Open Office 3.1 as the default application to open such files (Right-click, Properties > Open With)
Thanks in advance!
Mathieu _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Did you install the relevant rpm from the desktop-integration folder?? This has fixed these issues for me previously
I have installed openoffice.org3.1-redhat-menus.noarch from the sekto-integration subfolder. Is it what you had done?
On Mon, Nov 09, 2009 at 09:40:01PM +0100, Mathieu Baudier wrote:
Hi,
I have installed OpenOffice 3.1 downloaded from the openoffice.org website on CentOS 5.4 x86_64.
The downloaded file is actually an archive containing RPMs. I did not use their setup tool but installed directly the RPMs I was interested in via 'yum localinstall' (my idea is in the future to put them on a custom yum repository, so that they can be managed via regular yum install / update).
It works fine, except that when I double-click on, say, *.odt files in the file browser I get the following exception:
Cannot open xxxxxxx.odt The filename "xxxxxxx.odt" indicates that this file is of type "odt document". The contents of the file indicate that the file is of type "OpenDocument Text".
If I do a right-click, Open with... > Open Office Writer 3.1, it opens the file properly.
- Did anybody already experienced that?
- Do you know where I can manage the file types in GNOME?
I have already added Open Office 3.1 as the default application to open such files (Right-click, Properties > Open With)
i've removed the default OOo that comes with Centos 5.4 and replaced it with OOo 3.1.1 and I'm not having that trouble.
Don't know if this relates or not, but did you also install the RPM file for RedHat menu integration? If you unpack the archive that contains all the RPM files, there will be a subdirectory containing a bunch of files, each of which is a set of menu updates for various distributions. I've never investigated to see what they install, but I suppose it is possible that they install info that relates to the app linkage to file types and vice-versa.
On 11/10/2009 06:06 AM, fred smith wrote:
On Mon, Nov 09, 2009 at 09:40:01PM +0100, Mathieu Baudier wrote:
Hi,
I have installed OpenOffice 3.1 downloaded from the openoffice.org website on CentOS 5.4 x86_64.
The downloaded file is actually an archive containing RPMs. I did not use their setup tool but installed directly the RPMs I was interested in via 'yum localinstall' (my idea is in the future to put them on a custom yum repository, so that they can be managed via regular yum install / update).
It works fine, except that when I double-click on, say, *.odt files in the file browser I get the following exception:
Cannot open xxxxxxx.odt The filename "xxxxxxx.odt" indicates that this file is of type "odt document". The contents of the file indicate that the file is of type "OpenDocument Text".
If I do a right-click, Open with...> Open Office Writer 3.1, it opens the file properly.
- Did anybody already experienced that?
- Do you know where I can manage the file types in GNOME?
I have already added Open Office 3.1 as the default application to open such files (Right-click, Properties> Open With)
i've removed the default OOo that comes with Centos 5.4 and replaced it with OOo 3.1.1 and I'm not having that trouble.
Don't know if this relates or not, but did you also install the RPM file for RedHat menu integration? If you unpack the archive that contains all the RPM files, there will be a subdirectory containing a bunch of files, each of which is a set of menu updates for various distributions. I've never investigated to see what they install, but I suppose it is possible that they install info that relates to the app linkage to file types and vice-versa.
Have you updated the system after installing vanilla OOo? If yes, then that may be the problem. Because similar thing happened with me.
Have you updated the system after installing vanilla OOo? If yes, then that may be the problem. Because similar thing happened with me.
Yes I did update... Could you then fix it?
Do you think that I should force a reinstall?
On 11/10/2009 03:11 PM, Mathieu Baudier wrote:
Have you updated the system after installing vanilla OOo? If yes, then that may be the problem. Because similar thing happened with me.
Yes I did update... Could you then fix it?
Do you think that I should force a reinstall? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Most probably, the update you installed includes update for OOo. Since your version is vanilla and you are updating it with CentOS repos, this problem appears.
The only thing I can suggest is simply remove and install the vanilla OOo and *don't* update it with yum using the CentOS repo. To update it, you should use the OOo's update method. Otherwise this kind of errors will keep on coming.
Most probably, the update you installed includes update for OOo. Since your version is vanilla and you are updating it with CentOS repos, this problem appears.
The only thing I can suggest is simply remove and install the vanilla OOo and *don't* update it with yum using the CentOS repo. To update it, you should use the OOo's update method. Otherwise this kind of errors will keep on coming.
First, thanks a lot for your help! I will do what you suggest (uninstall/reinstall vanilla OO).
However I'd like to understand better, since I don't think that what happened is what you describe: - before installing the vanilla OO (3.1), I made sure that I had completely 'yum remove' the official OO (2.3) - so when I did the standard 'yum update' on my CentOS 5.4 installation I had no official OO installed, so I don't see how it could have messed things up?
Don't you think that this rather due to the fact that I did not use the vanilla OO 3.1 setup assistant? (but plain 'yum localinstall' on their RPMs instead) Or do I miss something from your explanation?
Anyhow, I'll reinstall and let know here what it fixed or not.
On 11/10/2009 06:52 PM, Mathieu Baudier wrote:
Most probably, the update you installed includes update for OOo. Since your version is vanilla and you are updating it with CentOS repos, this problem appears.
The only thing I can suggest is simply remove and install the vanilla OOo and *don't* update it with yum using the CentOS repo. To update it, you should use the OOo's update method. Otherwise this kind of errors will keep on coming.
First, thanks a lot for your help! I will do what you suggest (uninstall/reinstall vanilla OO).
However I'd like to understand better, since I don't think that what happened is what you describe:
- before installing the vanilla OO (3.1), I made sure that I had
completely 'yum remove' the official OO (2.3)
- so when I did the standard 'yum update' on my CentOS 5.4
installation I had no official OO installed, so I don't see how it could have messed things up?
Don't you think that this rather due to the fact that I did not use the vanilla OO 3.1 setup assistant? (but plain 'yum localinstall' on their RPMs instead) Or do I miss something from your explanation?
Anyhow, I'll reinstall and let know here what it fixed or not. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Your way of thinking is perfect. But even when you are not having official OOo, you were having vanilla OOo. And *unfortunately* sometimes the update rpm from OOo(vanilla) and OOo(official) are having the *same name*. So when you update, it can mess with the things(I came accross such instance for fedora+vanilla OOo 3.1).
I *don't* think this is because not using the setup assistance. Moreover I *don't* even think this is because of missing 'desktop integration' as suggested by Matheu. Because it will only add an OOo entry to the menu.
If you have the original default.list then you can even try for Janez's suggestion.
I did some tests today: - removed/reinstalled OO 3.1 from RPM => did not solve the problem - updated /usr/share/applications/defaults.list as per Janez advice => did not solve the problem
Interestingly I have this issue with ODT files but not with ODS (spreadsheets) files.
I'll keep digging (maybe on a clean virtualized install) and let know here (any ideas still welcome!)
I also install RPMs from OO.org. To make file associations work, you have to modify /usr/share/applications/defaults.list
here is what i did, to make it work: *cp /usr/share/applications/defaults.list /usr/share/applications/defaults.list.orig sed -i 's#openoffice.org-1.9#openoffice.org3#g' /usr/share/applications/defaults.list*
I hope it helps
BR
Janez
-
Digvijay Patankar -
fred smith -
Janez Kosmrlj -
Mathieu Baudier -
Rob Kampen