I'm seeing the same thing in my lab and it's getting downright annoying. I keep telling my students that the problem is my inability to correctly configure everything, but they're starting to think that Windows is less crash-prone than Linux and I don't want to be responsible for that perception.
Todd On Thu, 2007-09-13 at 15:21 -0500, Jim Kronebusch wrote: > Well here I have been trying to figure out how to keep Firefox from freezing > clients, > and now I see OpenOffice is a major culprit as well. The best I can do to > repeat the > problem for troubleshooting is to create a new Writer document, insert a few > graphics > from openclipart (5 seems to be plenty), then try printing to one of our HP > LaserJet > 4000 printers, mouse gets a little jerky, sometimes graphics pop up all over > the top of > the screen, then before anything prints the client locks up. > > I have monitored CPU/Memory usage with htop on the server, with htop in > screen 1 on the > client, with xrestop on the client from screen 7, memory usage with free on > screen 1, > and can not find a single spike in anything that seems to lead up to the > freeze. > However if I look at /home/username/.xsession-errors I do see some funky > stuff that > might start to tell a story. See below, I added some comments to help see a > timeline: > > First cleared all stale processes for the user then boot client > -- Log in as user, results below > Xsession: X session started for jim at Thu Sep 13 14:58:58 CDT 2007 > Setting IM through im-switch for locale=en_US. > Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to > /etc/X11/xinit/xinput.d/default. > SESSION_MANAGER=local/ltsp:/tmp/.ICE-unix/9593 > Initializing gnome-mount extension > modinfo: could not find module fglrx > modinfo: could not find module nvidia_legacy > modinfo: could not find module nvidia_new > modinfo: could not find module nvidia > > (gnome-panel:9651): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to > allocate > widget with width -1 and height 24 > --Start OpenOffice no errors > --Add in clipart, no errors > --Print to LaserPrinter, errors below > libGL error: open DRM failed (Operation not permitted) > libGL error: reverting to (slow) indirect rendering > Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a > timestamp > of 0 for 0x280005f (OpenOffice) > Window manager warning: meta_window_activate called by a pager with a 0 > timestamp; the > pager needs to be fixed. > --client now frozen > > The errors are not exactly the same every time. Sometimes the client freezes > sooner > than others. I can also reproduce some errors on saving a file or while > simply making > changes to a document with the graphics already inserted. But printing seems > to be a > sure fire way to freeze every time. > > I have un-installed xterminator, scim, and DIRECTX support thinking they may > be a > problem. No effect. > > I remember a couple of weeks ago David Trask reported similar problems when > working in > Writer and Impress. > > Below are some more errors I have seen, maybe some extra errors will give > more clues: > Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a > timestamp > of 0 for 0x260005d (OpenOffice) > 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 0x2600169 (german - O) > 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 0x280005d (OpenOffice) > 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 0x280005d (OpenOffice) > Window manager warning: meta_window_activate called by a pager with a 0 > timestamp; the > pager needs to be fixed.** (gnome-printer-view:7072): CRITICAL **: > gnome_cups_request_new_for_printer: assertion > `gnome_cups_printer_get_attributes_initializ > ed (printer)' failed > > ** (gnome-printer-view:7072): WARNING **: Neither request nor output_fd set > Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a > timestamp > of 0 for 0x2a00003 (CHS_Main_L) > 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 0x280005d (OpenOffice) > 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 0x280017a (german - O) > Window manager warning: meta_window_activate called by a pager with a 0 > timestamp; the > pager needs to be fixed. > > > If anyone has any suggestions to try and get this resolved, please let me > know. > > Thanks, > Jim Kronebusch > > > > -- > This message has been scanned for viruses and > dangerous content by the Cotter Technology > Department, and is believed to be clean. > > -- edubuntu-users mailing list edubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users