From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Epiphany/1.6.5
Description of problem:
I installed kword to convert and old document, and now all .doc documents open in kword, and not openoffice. ugh.
Probably some good reason for this, but given that the standard office suite in FC4 is openoffice, koffice should come second.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It's stolen .odt too. Can it be changed back in a gui, or should I file a bug?
I will look into it...
Hm ok, finally got the time.
Here is where I see the problem:
Dropping the mime typ stuff from the desktop entries would not be a big problem.
The reason I hesitate to do so is this:
If I remove this it would mean for users that don't install ooo that those files
are not owned by any application. Putting triggers into the scripts is a
solution which I do not like at all. Isn't there a clean(er) solution to this?
So if two things have the same mime type, I can't set a preference?
Thats what I would like to have... like a system-control-center where those mime
things are inserted and then you have a list like
odt: ooo, kword, ...
and the user can choose the default. If the list is empty the first one
installed will get the default...
I don't know if this is possible or not will have to investigate this further...
Users certainly can choose a preference (at least in KDE they can, can't comment
See /usr/share/config/profilerc as an example how an admin can set a system-wide
default preferences (ie, you can prioritize preference).
There seems to be no per-user gui way of changing or removing an association.
It's worsened by kword stealing a document type away from OO.org.
> There seems to be no per-user gui way of changing or removing an association.
Yes there is.
KDE Control Center->KDE Components->File Associations.
Find the mimetype to modify, Change "Application Preference Order" to suit.
> It's worsened by kword stealing a document type away from OO.org.
It's not "stealing" anything. They both offer to be able to handle .odt
doc-types, that's all. I think the default ends up being whoever comes first
(In reply to comment #8)
> > There seems to be no per-user gui way of changing or removing an association.
> Yes there is.
> KDE Control Center->KDE Components->File Associations.
> Find the mimetype to modify, Change "Application Preference Order" to suit.
But there isn't in Gnome, which is the default (isn't KDE extras?).
> > It's worsened by kword stealing a document type away from OO.org.
> It's not "stealing" anything. They both offer to be able to handle .odt
> doc-types, that's all. I think the default ends up being whoever comes first
> alphabetically, unfortunately.
It is stealing if I don't want it changed, and I can't change it back!
Re: Gnome's (in)ability to change mime-type/file-association defaults
That's not koffice's fault. Bugzilla against gnome then.
FYI, abiword (which also can handle .doc files) probably will do the same thing
p.s. KDE isn't in Extras (yet).
Thanks for making this clear Rex... I did not know the KDE way of changing this
but it certainly seems like there is a black hole in Gnome for this. I will
close this bug. However I agree that there should be an option for Gnome to
choose a default mime type. Please go ahead and file a bug against gnome.
I agree that the bug is misfiled, and with your statement about a "black hole in
Gnome", but I don't see why opening a new bug will help.
If the bug is miscategorised, then update the title and change the category.
Entering a new bug takes time, and asking someone else to do it takes even longer.
Bugzilla Reporters can reopen/reassign (their) bugs. Knock yourself out.
As Rex said -> you can always reopen and or reassign it if and how you feel fit.
The problem here is: I as koffice maintainer can not really do anything about
this from a koffice point of view and I doubt that reassigning this bug to gnome
would do you any good. After all what we are looking for is a feature
enhancement in gnome and that should be placed in the upstream bugzilla
If you don't have the time I certainly can do this for you. Let me know.