https://bugs.freedesktop.org/show_bug.cgi?id=24226
--- Comment #18 from Nathan Kidd <[email protected]> 2010-10-14 13:52:26 PDT --- 1) To further document "lots of people affected by this" (and I'm well aware I haven't gotten off my posterior to fix this either): SuSE brought this up last year[1] and ended up shipping with this patch[2] (a band-aid): - if (glx_direct) - dpyPriv->driswDisplay = driswCreateDisplay(dpy); +// if (glx_direct) +// dpyPriv->driswDisplay = driswCreateDisplay(dpy); [1] http://www.mail-archive.com/[email protected]/msg06684.html [2] https://bugzilla.novell.com/show_bug.cgi?id=469280 2) Bear in mind that making the visuals match exactly merely allows the software renderer to be used, it doesn't allow indirect GLX (check your GLX server strings carefully). LIBGL_ALWAYS_INDIRECT is quite a pain, (more so for XDMCP sessions). In my experience client-side rendering is what most people want if the display is remote. If the network load is too heavy for client-side the render load will very likely be too heavy for the software rasterizer. (And apps can use display lists to alleviate the network load.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
