Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: [SOLVED] Nautilus problem, completely stumped

  1. #1
    Join Date
    Feb 2008
    Beans
    10

    [SOLVED] Nautilus problem, completely stumped

    I cannot open the contents of my file system using Nautilus.

    I tried running it from a terminal, just to see if I could learn anything relevant via error messages. This is what I get back:

    Code:
    Initializing nautilus-share extension
    seahorse nautilus module initialized
    
    ** (nautilus:7667): CRITICAL **: nautilus_directory_file_monitor_add: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
    
    (nautilus:7667): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    
    (nautilus:7667): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    
    (nautilus:7667): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    
    (nautilus:7667): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    
    ** (nautilus:7667): CRITICAL **: nautilus_directory_get_uri: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
    Segmentation fault
    It occurred to me then that perhaps I could run it as root from the terminal. Turns out, yes I can. Why can I use my file manager as root but not any other way? Help.

  2. #2
    Join Date
    Dec 2005
    Location
    Kansas
    Beans
    30
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: Nautilus problem, completely stumped

    Usually if you can access a file, application, or anything else on your system with root but not with a user it means your user account doesn't have the correct permissions. Now that said, getting the correct permissions can be a pain, especially if your new.

    To look at the permissions of nautilus first open up your terminal and issue:

    sudo -s
    cd /usr/bin
    ls -l nautilus

    Now the fun part . . . you'll see 3 groups of 3 letters and these three letters are values. The three values total a number and that number signifies the permission of that group. The first group of numbers represent the owner of the file or application, the second group represent the group, the third group represents others.

    Remember I said the three values of each group total a number? Well lets go over that.
    There are 4 numbers that stand represent your systems permissions. 4 = read permissions 2 = write permissions 1 = execute permissions 0 = no permissions.

    Lets say that you want to give the group, the owners, and others complete access to nautilus. The command to use is chmod . . . but what is the number to use? If we want read, write and execute permissions we need to use a 4 + 2 + 1 . . . so the command would be

    chmod 777 nautilus

    Once you learn how the permission numbers work they are easy. If you become a sys admin then you can give crazy, custom permission on any file/app/group without using some java based permission calculator. It's critically important when tons of users accessing a server with different levels of access rights.

    You still may need to change the owner of nautilus. The command would be:

    chown yourusername:yourgroup nautilus

    Most of this is taken from The Complete Idiot's Guide to Linux I picked it up at the library the other day. It's a ridiculously dumb title . . . but useful information for beginners.

    Good luck and I hope this helps a little in clearing up your question.
    Tinker
    Last edited by tinker312; August 12th, 2008 at 05:51 AM. Reason: Cleaning up

  3. #3
    Join Date
    Aug 2006
    Location
    20,000 structs inside C
    Beans
    321
    Distro
    Ubuntu Development Release

    Re: Nautilus problem, completely stumped

    nautilus should be owned by root and in group root with permisions 755 (rwxr-xr-x)
    "Everything that can be invented has been invented." -- Charles H. Duell, Commissioner, U.S. Office of Patents, 1899
    Ubuntu user #24001

  4. #4
    Join Date
    Feb 2008
    Beans
    10

    Re: Nautilus problem, completely stumped

    Would a permissions issue really cause those error messages? I followed your suggestions, problem still persists.

    Also, this is a completely fresh install of 8.04.1. The install CD I used passed the md5 checksum, and the verification tool said everything was fine. I can't figure out why a totally critical component of a desktop environment wouldn't work right out of the box. Very weird.

  5. #5
    Join Date
    Aug 2006
    Location
    20,000 structs inside C
    Beans
    321
    Distro
    Ubuntu Development Release

    Re: Nautilus problem, completely stumped

    I seem to remember a similar bug being reported back in 2006 i think it was something to do with mime types.
    try
    Code:
    nautilus -c
    to run some self tests on nautilus and post the output
    then try
    Code:
    nautilus /
    to see if nautilus will open in a different location (there may be something in the folder screwing it)
    "Everything that can be invented has been invented." -- Charles H. Duell, Commissioner, U.S. Office of Patents, 1899
    Ubuntu user #24001

  6. #6
    Join Date
    Dec 2005
    Location
    India Himalaya
    Beans
    218
    Distro
    Ubuntu Studio 13.04 Raring Ringtail

    Re: Nautilus problem, completely stumped

    Quote Originally Posted by 3gotist View Post
    Also, this is a completely fresh install of 8.04.1. The install CD I used passed the md5 checksum, and the verification tool said everything was fine. I can't figure out why a totally critical component of a desktop environment wouldn't work right out of the box. Very weird.
    Not a direct solution but install konqueror so that your work does not stop,

    Then check to see if nautilus has any updates - if so update it and then check if its back to normal.

    By default nautilus should be enabled for the primary user.

    ram
    K Ramnarayan

  7. #7
    Join Date
    Feb 2008
    Beans
    10

    Re: Nautilus problem, completely stumped

    Quote Originally Posted by Thingymebob View Post
    I seem to remember a similar bug being reported back in 2006 i think it was something to do with mime types.
    try
    Code:
    nautilus -c
    to run some self tests on nautilus and post the output
    Okie doke, here's that
    Code:
    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_icon_container
    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_icon_container
    then try
    Code:
    nautilus /
    to see if nautilus will open in a different location (there may be something in the folder screwing it)
    Still doesn't work.

    Code:
    seahorse nautilus module initialized
    Initializing nautilus-share extension
    
    ** (nautilus:7020): CRITICAL **: nautilus_directory_file_monitor_add: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
    
    (nautilus:7020): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    
    (nautilus:7020): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    
    (nautilus:7020): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    
    (nautilus:7020): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    
    ** (nautilus:7020): CRITICAL **: nautilus_directory_get_uri: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
    Segmentation fault
    Konqueror it is, until I can figure out what the heck is going on. I was using xubuntu for a little while, but I decided to switch cuz there are certain things about it I didn't like. Maybe I ought to go back. Hah.

    Edit: So I created another user on the machine, and I can definitely use nautilus as desired with the new account without changing any permissions or anything like that. I am totally lost, here.
    Last edited by 3gotist; August 12th, 2008 at 08:32 AM. Reason: More info

  8. #8
    Join Date
    Feb 2008
    Beans
    10

    Re: [SOLVED] Nautilus problem, completely stumped

    I figured out a workaround. I dumped everything from my /home directory into a temporary folder on the same partition, and reinstalled using a different username in the installer than my previous one. Everything works fine, now.

    Thanks for your help.

  9. #9
    Join Date
    Apr 2009
    Location
    Illinois
    Beans
    2
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: [SOLVED] Nautilus problem, completely stumped

    I've been having this same issue for awhile and just fixed it. It turns out, for me at least, in my ~/.gnome2 folder there is a nautilus-scripts directory. Mine was a symlink for a directory that did not exist (/usr/share/nautilus-scripts). Once I created that folder nautilus started working.

    Hope my solution works for someone else!

    -Dan

  10. #10
    Join Date
    Jul 2008
    Beans
    6

    Re: [SOLVED] Nautilus problem, completely stumped

    Quote Originally Posted by dwatling View Post
    I've been having this same issue for awhile and just fixed it. It turns out, for me at least, in my ~/.gnome2 folder there is a nautilus-scripts directory. Mine was a symlink for a directory that did not exist (/usr/share/nautilus-scripts). Once I created that folder nautilus started working.

    Hope my solution works for someone else!

    -Dan
    I had exactly this problem under 11.04 as I was reorganizing some things. Took a little be to trace down the problem, but with your post I solved it in seconds. Thanks!

    The critical log line turned out to be in my .xsession-errors:

    ** (nautilus:17226): CRITICAL **: nautilus_directory_file_monitor_add: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •