To confirm Chuck's comments above, down-grading libglib2.0-0 to a previous version solved my problem as well..."Computer, Network, and Trash" can all safely be clicked again without fear of having Nautilus bomb-out on me.
I was highly conflicted rolling back the libglib package, as I wanted to be able to continue and assist the troubleshooting efforts...however, I simply can not have my computer dysfunctional for that long; I need it up and running 100%.
I hope this bug does not get marked as "invalid" or canceled...as there is definitely a problem with the libglib2.0-0 package that manifests itself as a Nautilus problem. This problem also appears to be limited to 64-bit users.
I've had Synaptic lock the "good" version of libglib2.0-0 and I will monitor this bug in hopes I can release that lock and upgrade to a fixed version.
To confirm Chuck's comments above, down-grading libglib2.0-0 to a previous version solved my problem as well..."Computer, Network, and Trash" can all safely be clicked again without fear of having Nautilus bomb-out on me.
I was highly conflicted rolling back the libglib package, as I wanted to be able to continue and assist the troubleshooting efforts...however, I simply can not have my computer dysfunctional for that long; I need it up and running 100%.
I hope this bug does not get marked as "invalid" or canceled...as there is definitely a problem with the libglib2.0-0 package that manifests itself as a Nautilus problem. This problem also appears to be limited to 64-bit users.
I've had Synaptic lock the "good" version of libglib2.0-0 and I will monitor this bug in hopes I can release that lock and upgrade to a fixed version.
Thanks all!