
apt-listbugs wrote:Grave bugs of metacity (1:2.30.1-3 -> 1:2.34.1-2) <unfixed>
#648052 - metacity segfaults after todays update to wheezy



nautilus
(nautilus:2302): NA-core-DEBUG: na_settings_register_type
(nautilus:2302): NA-core-DEBUG: na_settings_class_init: klass=0x9b44a58
(nautilus:2302): NA-core-DEBUG: na_settings_instance_init: instance=0x9b34350 (NASettings), klass=0x9b44a58
(nautilus:2302): NA-core-DEBUG: na_settings_new: reading mandatory configuration
(nautilus:2302): NA-core-DEBUG: na_settings_new: reading user configuration
(nautilus:2302): NA-core-DEBUG: na_boxed_register_type
(nautilus:2302): NA-core-DEBUG: na_boxed_class_init: klass=0x9b456a0
(nautilus:2302): NA-core-DEBUG: na_boxed_instance_init: instance=0x9b341b0 (NABoxed), klass=0x9b456a0
--- Hash table keys for warning below:
--> gerd50
--> inode/directory
--> l2065
--> l2051
--> root
--> l2055
--> l2056
--> l13
(nautilus:2302): Eel-WARNING **: "unique eel_ref_str" hash table still has 8 elements at quit time (keys above)
--- Hash table keys for warning below:
--> file:///
--> file:///Archiv
--> file:///media1
(nautilus:2302): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 3 elements at quit time (keys above)







Nov 9 14:39:26 misterhost kernel: [ 128.415917] gnome-shell[2135]: segfault at b ip b76f21ec sp bf8ae6d0 error 4 in libmutter.so.0.0.0[b7668000+bf000]





I found the problem.zerozero wrote:do you remember which extension(s) you installed just before that failure start to happn? if so login in fallback-mode, go to usr/share/gnome-shell/extensions and delete it (them)





mockturtl wrote: I seem to remember hearing that "don't power down when I shut the lid" is not an option in gnome3. I think I read it was a design decision. I remember thinking the correct engineering solution would be to drop a tree on that designer.
Can I ssh into this laptop with the lid closed?



viking777 wrote:I had a quick look at gnome3 but it would only start in fallback mode, so if my Nvidia Geforce 8600 is not powerful enough to run it then they can go hang as far as I am concerned, I would only use Fluxbox anyway and thankfully that has not been affected in any way that I can see so far. (incidentally Unity works well enough with my present graphics setup)


thekingmen wrote:The delete key does not work anymore in nautilus after the upgrade to gnome 3. Someone know how to make it work again ?

GregE wrote:
Hi, I sounds like your driver is broken. An Nvidia 8600GS should run the shell OK, but I think you will need Nvidia drivers rather than Nouveau.
cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 290.03 Mon Oct 17 10:23:33 PDT 2011
GCC version: gcc version 4.5.3 (Debian 4.5.3-9) 


viking777 wrote:GregE wrote:
Hi, I sounds like your driver is broken. An Nvidia 8600GS should run the shell OK, but I think you will need Nvidia drivers rather than Nouveau.
- Code: Select all
cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 290.03 Mon Oct 17 10:23:33 PDT 2011
GCC version: gcc version 4.5.3 (Debian 4.5.3-9)
I don't think that is out of date is it?
And I certainly don't use Nouveau!
Thanks for the suggestion anyway, and I agree an Nvidia 8600GS should run the shell, but it doesn't. But as I said earlier it runs Unity 3d without bother.
Edit. I have got to say it doesn't really matter all that much to me, even if I got it going I would still use Fluxbox all the time anyway, it is just that I would like to satisfy my curiosity as to what it is all about.


There is a slightly newer version of Nvidia in experimental, I am using 290.06 with a G210 card and it works a treat. Maybe worth a try to get the latest driver as I think there are issues with Nvidia and xorg. Even going backward to a 275 might actually be better. Depends on how keen you are to solve a problem that does not matter to you.




Elmacus wrote:Now i got Gnome3 to play with, and some interesting faults to handle, like some holdback on Xorg.




Users browsing this forum: No registered users and 3 guests