Description of problem: Looks like at-spi is stupidly spewing some warning messages to stderr, which winds up dumping them into ~/.xsession-errors. One particular error... (gnome-terminal:3616): atk-bridge-WARNING **: failure: no device event controller found. ...has been repeating over and over and over and over, to the tune of a 43G ~/.xsession-errors file on my laptop in a mere day and a half of uptime. Looks like the culprit is somewhere in libatk-bridge.so. Version-Release number of selected component (if applicable): at-spi-1.23.6-1.fc10 How reproducible: not exactly sure. I don't actually *use* any of this accessibility stuff...
I think this might do the trick: --- at-spi-1.23.6.orig/atk-bridge/bridge.c 2008-08-15 13:23:16.000000000 -0400 +++ at-spi-1.23.6/atk-bridge/bridge.c 2008-08-15 13:26:15.000000000 -0400 @@ -470,7 +470,7 @@ spi_atk_bridget_get_dec (void) if (BONOBO_EX (&ev)) { - g_warning (_("failure: no device event controller found.\n")); + DBG (1, g_warning (_("failure: no device event controller found.\n"))); registry_died = TRUE; device_event_controller = CORBA_OBJECT_NIL; }
That looks fine, feel free to put that patch into rawhide or where you need it when koji comes back.
Upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=547943
Okay, patch has been added to rawhide and at-spi-1.23.6-2.fc10 has been tagged. Build hosts still offline though.
I've built it now