Comment 27 for bug 263211

This increase in numbers is consistent, and was caused simply by Right-Clicking on knetworkmanager and hitting escape... over and over again.

1425
1425
1425
1425
1426
1430
1434
1438
1442
1444
1448
1453
1458
1466
1472
1474
1474
1474

It seems that "Maximum clients reached" is more a symptom of it's own bug classification, which is indicative of any application not managing its X resources carefully.

All applications (in all distributions) should undergo testing to prove they have no "X resource leakage" so to speak. Clearly writing a desktop systray-applet that misses reclaiming an X window here and there doesn't seem like that big a deal.... but apparently many apps are causing a big problem.

How do we proceed???