Red Hat Bugzilla – Bug 540198
Nautilus file manager non-functional after upgrade from Fedora 10 to Fedora 12
Last modified: 2010-01-18 07:06:47 EST
Description of problem:
Nautilus non-functional after upgrade from Fedora 10 to Fedora 12
Always (tried twice)
Steps to Reproduce:
1. Update uptodate Fedora 10 to Fedora 12
2. Boot into GNOME
Empty desktop: old background image has been correctly restored, but no files are shown on the Desktop (though they still exist according to the terminal), plus the right-click menu is never shown.
Two nautilus processes are running:
$:andre\> ps ax | grep nautilus
2350 ? S 0:00 nautilus
2353 ? S 0:00 nautilus
2366 pts/0 R+ 0:00 grep nautilus
Also, going to "Places" and choosing any folder does not bring up a file manager window.
Lenovo Thinkpad T61 (got Nouveau only to work by using "nomodeset" as boot parameter)
FIRST OF ALL: THIS IS FIXED, SEE BELOW.
Feel free to close as INVALID or whatever, but cannot hurt to have it documented here. :-)
come up with nothing.
I did not mention in my initial posting here that I cannot run
because I thought that this is unrelated to this issue.
However, after finding similar problem descriptions at
http://forums.fedoraforum.org/showthread.php?p=1293399 and http://osdir.com/ml/fedora-list/2009-11/msg01664.html it might be related.
The first link mentions the theory "nautilus starts up and loads brasero-nautilus, this uses the brasero library and tries to initialize gstreamer".
Here is the output of that issue. It is exactly the same output for all applications mentioned in the list before:
Warning: Unable to create "trees" RDF storage.
Performance can be improved by upgrading librdf.
sys:1: Warning: cannot register existing type `GstSignalProcessor'
sys:1: Warning: g_once_init_leave: assertion `initialization_value != 0' failed
sys:1: Warning: g_type_register_static: assertion `parent_type > 0' failed
(totem:2525): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed
After that it hangs forever.
Also note that after choosing to restart I always got the popup "Application still running: File Manager - No answer"
So after I yum erase'd
and rebooted, my files and folders on the Desktop were finally shown plus there is only one nautilus process running.
Don't know exactly which of the files was the one to blame.
Thanks Andre, this is really useful. I'll leave this bugreport open for a while, I suspect lots of abrt bugs (whose stacktraces are usually full of question marks) point to the same issue.
*** Bug 543826 has been marked as a duplicate of this bug. ***
gstreamer-plugins-good-0.10.17-3.fc12 has been submitted as an update for Fedora 12.
gstreamer-plugins-good-0.10.17-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
Yes, this fixed it for me.
No problems after reinstalling the packages in comment 1 and rebooting.
*** Bug 546085 has been marked as a duplicate of this bug. ***
*** Bug 554016 has been marked as a duplicate of this bug. ***
Even with gstreamer-plugins-good-0.10.17-3.fc12 I still had to remove the below packages to get nautilus to start.
*** Bug 553910 has been marked as a duplicate of this bug. ***
Still persisting, Fedora 12...
Ok, I got it working aswell, by removing gstreamer-plugins-ugly, -bad, -bad-extra
Did anybody allready file bugs against them? And if where did you do so and does omebody take care about?
*** Bug 550924 has been marked as a duplicate of this bug. ***
Have you tried a forced relabeling by SELinux on reboot? That seemed to have fixed the same symptoms that I had after an update done to F12. I lost all of my desktop icons and nautilus would not run. After rebooting with the relabel set, everything worked again.
Yes, I relabel with no luck. Not sure which package but I removed all of the following, then all was good.
*** Bug 553926 has been marked as a duplicate of this bug. ***
I just verified that I do have all of those packages although I have the x86_64 builds, so I don't know if that makes a difference. Don't know what to tell you on that.
It does not, I have x86_64 Fedora 12 up and running and after I removed the pending x86_64 packages and a re-login it worked just fine again
I do notice one difference, I don't have any of the devel packages for gstreamer. That shouldn't matter as all that is is the source code of the respective package, which you only need if you compile software that requires the inclusion of that package into its source at compile time. You could just install one at a time to see which one is causing this to happen. You could have a conflict in some obscure configuration file.
The question is rather what has been done in order to make gstreamer-plugins-good work, as this big was initially reported against gstreamer-plugins-good, and then search for the responsible for the bad/bad-extras/ugly plugins.