On Mon, Apr 26 2010 at 02:30, Andrea Bolognani wrote: >> So, as I mentioned above, I have two X servers from stable with two >> different drivers and one scrotwm from testing, which connects to X >> server via tcp socket. > > So the version of Xlib (or related libraries) used by the X server is > differen than the one loaded by scrotwm.
As far as I understand, there is no Xlib version corresponding to a particular version of X server, they are not synchronized. By the way, if we are right and the bug is some way related to X protocol implementation, the solution may either help in migrating to xcb -- another X client library upstream developers are going to use in future releases. > With “same thing”, you mean “the bug goes away”, right? Sorry.. No, the only way I got rid of the bug is starting scrotwm from a terminal with DISPLAY variable properly set. > However, if we manage to make certain you’re hitting the bug only > because you have an arguably not so common setup, and the same turns > out to be true for Hannes, I will consider downgrading the severity of > this bug. I disagree that my setup is not so common -- tcp socket is actually the second (of 2) way to connect to X server. And -- please don't forget about it -- scrotwm works well with all of my mixed library versions when started from another terminal. -- ~dd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
