Results 1 to 7 of 7

Thread: nautilus can not acces trash:, computer:, network:, ...

  1. #1

    Default nautilus can not acces trash:, computer:, network:, ...

    Hi.
    I had a problem a few weaks ago.
    My system suddenly started to crash all programs, at the point that i had to restart.
    Then it refused to boot properly saying that the filesystem was corrupt and that fsck.xxxx --rebuild-tree would fix the problem.
    I did that.
    It counts 3 steps.
    "0" was ok, then "1" complains about something not done in "0". Runned the tool a couple of times more before finding in internet that it could be a memory problem.

    It was.
    One of my memories was slightly broken.
    I have now changed it, but the filesystem table needed to be rebuildt.
    No problem with that. --rebuild-tree complains with no error, but now i can not access mostly anything from nautilus without a crash.

    This is what happens:
    Double clic on Network icon = crash
    Double clic on Computer icon = crash
    Double clic on Trash icon = crash
    Delete something = Completely loose that (no trash)

    running nautilus from console shows output only when run as root, not as a user, and doesnt crash.

    nautilus --no-desktop
    Code:
    Initializing nautilus-dice extension
    Initializing nautilus-open-terminal extension
    Initializing nautilus-share extension
    Nautilus-Share-Message: REFRESHING SHARES
    Nautilus-Share-Message: ------------------------------------------
    Nautilus-Share-Message: spawn arg "net"
    Nautilus-Share-Message: spawn arg "usershare"
    Nautilus-Share-Message: spawn arg "info"
    Nautilus-Share-Message: end of spawn args; SPAWNING
    
    Nautilus-Share-Message: returned from spawn: SUCCESS: 
    Nautilus-Share-Message: exit code 255
    Nautilus-Share-Message: ------------------------------------------
    Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
    
    
    ** (nautilus:5763): WARNING **: Unable to add monitor: Operation not supported
    
    ** (nautilus:5763): WARNING **: Unable to add monitor: Operation not supported
    And prints an error message dialog without crashing:

    Could not display "network:///".
    Nautilus cannot handle "network" locations.

    The folder contents could not be displayed.
    Sorry, could not display all the contents of "trash": Operation not supported


    GNOME nautilus 2.27.1
    Tryed with 2.24 too.


    I have also found this old bug:
    Bug 523039 - nautilus can't access to trash/computer/network if gvfs isn't installed in the same prefix as glib (glib)
    But the solution mentioned there about the place of gvfs modules is not the problem here.

    The bug is associated with some problem to handle protocols with nautilus, like smb\ computer\, network\, trash\, etc...
    And this is somehow related to gvfs.

    I have downgraded gvfs and again upgraded. no success.
    Downgraded gconf2 and then gdm doesnt starts any more. so upgraded again.



    I am out of clue of where is the problem.
    It seams to be started with the broken memory and the fsck.xxxx --rebuild-tree

    I hope that someone have a clue for me, because i dont want to format all my PC again.

    cheers
    Diego

  2. #2

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    On your place i'd update unconditionally, it would overwrite any corrupted files and after that You should be fine. Hope zypper/rpm are not corrupted.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

  3. #3

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    Sorry. I forgot to mention that.
    I did upgraded the whole system to replace any "broken" file with zypper.

    I supouse that i could as a last resource resintall every single package on my system with zypper and cross my fingers.

  4. #4

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    I know you updated, i mean to update unconditionally what will pull all the packages you currently have (there will be lots of downloading) and not to update.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

  5. #5

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    sorry.
    I dont know what you mean with "update unconditionally"
    Is it different to update every single outdated package and leave no other package to update?

  6. #6

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    I have updated today again some packages including gvfs between and some other gnome apps. Just in case, except for gconf2.

    The problem is solved now.

    So i tink that it was a problem with gvfs or some other that was updated.

    I wonder, how can i know what packages were updated and from what version to what version.
    Is there any log file for zypper with that information?

  7. #7

    Default Re: nautilus can not acces trash:, computer:, network:, ...

    the install log is in /var/log/zypp/history

    Update unconditionally is when you turn on Software management then Package-->>All Packages-->>Update Unconditionally

    It pulls ALL the packages you have installed and also any that need to be updated.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

Posting Permissions

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