I'm having a very weird problem with one of my machines

The Symptom - shortly after logging in, gnome-shell will be
'non-responsive' with the hot corners, Super/Windows Key, etc all
failing to do anything. Clicking on the Activities or User Menu gets
no response

However, the machine is otherwise operational

This is happening on both GNOME 3.6 and 3.8 consistently, but only on
one of my machines.

If I already have windows open, these windows may still work - for
example Firefox is still perfectly responsive, as is Guake and YaST

'Core GNOME' applications like Nautilus however seem to 'lock up' at
the same time. If you happen to have any of these 'core GNOME'
application windows over the top of non-GNOME applications like
Firefox/YaST any mouse clicks seem to pass right through the GNOME
applications, activating whatever you're accidentally clicking on in
the Firefox/YaST windows below

Waiting a while seems to be all it needs to get gnome-shell working as
usual, and it doesn't occur more than once per user session, but it
does seem to be happening on every user session on this machine.

Things I believe I've ruled out

1) Weird settings in /home folder - I destroyed all hidden folders in
my home folder, and this occurs on fresh accounts
2) Nvidia vs Nouveau - yes, this machine has an Nvidia video card, but
this behaviour is happening identically on both Nvidia and Nouveau
video drivers
3) Software selection - this happens on a fresh GNOME openSUSE 12.3
installation from DVD with no customisation what so ever, as well a
fresh 12.3 Install with GNOME Stable 3.8 + guake + owncloud
4) Multi monitors - this seems to happen regardless of what multi
monitor behaviour is in place

Theories I've got left - ie "What's special about this machine?"

All my other GNOME machines and VM's all use Network Manager, this is
the one machine I has that does not. But I see nm-applet is running so
I guess gnome-shell might be doing some weird attempted init on boot,
failing, locking up, then giving up and behaving normally.
This isn't a machine I can easily activate NM on, so before I test
this theory, I would like to hear if anyone else has bumped into
anything like this, and if so, what was the fix for you if you found
one?

And if anyone else has any bright ideas where to look for any
solutions or clues so I can actually file a useful bug report for
someone, I'd appropriate it ;-)
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to