Description of problem:
This is reproducng since fc5 for me, where various applications espacially PDF
and images type shows application association problems with nautilus.
I tried to remeove various mime related config files but this never got
permanently helped. The issue seems to start to re-produced always
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. click on applications of various file/mime types
files will not open unless do a right click and mention an application
this should not bother me so much.
attached images of errors, more infomation and debug will be happily provided as
Created attachment 140382 [details]
jpg file error nautilus
Created attachment 140383 [details]
png file error msg nautilus
Created attachment 140384 [details]
pdf error msg nautilus
possibly a dup of 212764, does "update-mime-database /usr/share/mime" as root
(In reply to comment #4)
> possibly a dup of 212764, does "update-mime-database /usr/share/mime" as root
> fix it?
I tried the suggested workaround, but this did not helped. What is the best
preocedure to ensure that the files in $USER $HOME are also updated or which ones
to manually remove in $HOME to test ensure further
I'm not sure what you mean.
(In reply to comment #6)
> I'm not sure what you mean.
Alex, I mean that what files in a users home directory I should also remove or
update to ensure that the system wide configuration is in effect and is working
Ah, removing everying in .local/share/mime (or temporarily moving it) should be
I have problem with ooo documents default action mime type.
Nutilus update correctly when icon isn't selected.
When it's selected the mime type change to application/x-java-archive
and default action doesn't work.
I had been migarating my office setup from RHEL4 to FC6 on a newly assigned
system and this issue reprodued. I tried above discuessed workarouds and
"update-mime-database /usr/share/mime" helped.
But I realized that the issue effected all users system wide, even one of the
users data was moved on to this new setup from another FC6,
where this issue re-produced after installing google-earth, I believe this to be
Are you saying you believe google-earth caused this problem?
(In reply to comment #11)
> Are you saying you believe google-earth caused this problem?
Sorry for a late response, yes I believe google-earth caused this issue, however
I could not deliberatly re-repoduce this issue again yet.