Comment 155 for bug 349519

It's not a laptop or netbook thing only. I'm running Precise on an older 32 bit Intel x86 machine and I'm not switching desktops. I use the UBUNTU login for the Unity desktop and have since I installed Precise. I find these errors:

Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x260003f (Workspace )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Eclipse SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x26001e2 (Java - Ecl)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2602b3b (New Projec)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x26001e2 (C/C++ - Ec)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2605ce6 (New Projec)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x26001e2 (C/C++ - Ec)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x260727c (Delete Res)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x26001e2 (C/C++ - Ec)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(gnome-shell:19705): Clutter-WARNING **: The meta of type 'StScrollViewFade' with name 'fade' is not attached to the actor 'StScrollView'
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200003 (Eclipse SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200310 (Java - Ecl)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200b49 (Available )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200310 (Java - Ecl)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200310 (Java - Ecl)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x220417e specified for 0x2204181 (Android SD).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2204181 (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220417e (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2211401 (Choose Pac)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220417e (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220417e (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x221cf8a (Security W)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220417e (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x22202a5 (Software U)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220417e (Android SD)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200310 (Java - Ecl)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus 0x1e0009d (vnc and gd) with a timestamp of 0. This shouldn't happen!

...these errors started following the error specified below in my .xsession-errors log file and only appear to happen sporadically:

[000:000] Browser XEmbed support present: 1
[000:022] Browser toolkit is Gtk2.
[000:023] Using Gtk2 toolkit
[000:098] Starting client channel.
[000:098] Warning(clientchannel.cc:435): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection
[000:100] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[000:100] GoogleTalkPlugin not running. Starting new process...
[000:100] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:100] Warning(pluginutils.cc:268): Failed to get GoogleTalkPlugin path. Trying default.
[000:103] Started GoogleTalkPlugin, path=/opt/google/talkplugin/GoogleTalkPlugin
[000:104] Waiting for GoogleTalkPlugin to start...
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
[001:155] Attempting to connect to GoogleTalkPlugin...
[001:156] Warning(clientchannel.cc:435): Unreadable or no port file. Could not initiate GoogleTalkPlugin connection
[001:625] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[001:626] Waiting for GoogleTalkPlugin to start...
[002:628] Attempting to connect to GoogleTalkPlugin...
[002:629] Read port file, port=55666
[002:789] Initiated connection to GoogleTalkPlugin
[002:824] Socket connection established
[002:824] ScheduleOnlineCheck: Online check in 5000ms
[002:890] Got cookie response, socket is authorized
[002:891] AUTHORIZED; socket handshake complete

...as sporadic as they are and surrounded by thousands of these errors which didn't start until following the previous error as well:

ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream

I didn't think that ALSA even ran on my machine anymore since the overall improvement of Pulse Audio even though all of the ALSA structure still exists on my machine. I assumed it was kept around for "just in case" reasons and I have been thinking about removing and purging it all together.

I'm not sure, but I believe all this info actually ties to an apparently unrelated issue I have been trying to track down. My Nautilus has been crashing often and at inopportune times as well as at start up. It's always with a different error and never in an exact traceable sequence. The one thing I always find in association with my nautilus crash is one of these crazy little errors. They are always present. I'm not sure if this is even going to be helpful. My problem is more of an annoyance than a serious problem. It's almost like my init scripts need some kind of an adjustment that one loads before another not knowing it is actually a dependency of another.... maybe the numbering scheme is off kilter? I've seen crazier.