I am using Fedora 29 beta and I too come across this problem twice. And a couple of times nautilus crashed. Seems like there is a bug. I have reported it here (https://bugzilla.redhat.com/show_bug....) there are many others who come across and reported this bug. I hope they are resolving it.
Coming to the solution: You can reinstall nautilus. which solved the problem for me. Since then I didn't have any problem with opening it.
First, remove Nautilus, Sudo dnf remove nautilus
Then install it again using, Sudo dnf install nautilus
I believe this will solve your issue.
I've the same problem
nautilus: error while loading shared libraries: libtracker-sparql-2.0.so.0: cannot open shared object file: No such file or directory
I try with dnf install tracker but...
Error unpacking rpm package tracker-2.1.4-1.fc28.x86_64
please help!
I'm experiencing the same problem for the second time. I'm using fedora 29 on a HP laptop. More or less one month ago, nautlus started having a very strange behaviour after an update. every time i had to reboot, nautilus was freezed for about one our. No way to lauch the application, no message when using nautilus -c within terminal.
No way to fix (i tried to disable selinux, to reinstall, etc. etc. etc. ) no way to fix. At the end i created a new user to get nautlis back.
After today update i 'm experiencing the same problem. i need to wait more or less 30 minuti beforre nautilus start working.
[albert@localhost data]$ nautilus -c Initializing nautilus-dropbox 2018.11.28 Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension running nautilus_self_check_file_utilities running nautilus_self_check_file_operations running nautilus_self_check_directory running nautilus_self_check_file running nautilus_self_check_file_utilities running nautilus_self_check_file_operations running nautilus_self_check_directory running nautilus_self_check_file
This is very embarassing, do someone is experiencing the same problem? Is there a possible solution?
Asked: 2017-12-13 21:42:25 -0500
Seen: 1,432 times
Last updated: Oct 26 '18
Ask Fedora is community maintained and Red Hat or Fedora Project is not responsible for content. Content on this site is licensed under a CC-BY-SA 3.0 license.
Well, this is embarrassing. After fiddling with it for about 30 minutes, I walked away for several hours, and when I came back, nautilus was open. Now it's working normally. Not sure what happened.
Permission seems correct.
What is the output that you read when you start
nautilusfrom a non-root terminal?It said "Could not register the application: Timeout was reached." However, when I came back to it after several hours, I was surprised to find nautilus open. So the problem seems to have gone away. I'm not sure what happened.