Brice Goglin <[EMAIL PROTECTED]> writes: > I can't reproduce the problem here. There are very few commits between
Interesting, as I can reproduce it 100% reliably with both i386 and amd64 binaries. I do have some extra resource settings I neglected to mention earlier, XClock*background: lightgray XClock*font: fixed XClock*geometry: -0+0 XClock*padding: 1 XClock*update: 1 but only *font is at all likely to be relevant. > 1.0.2 and 1.0.3, so it should be very easy to locate where the breakage > occurred. Could you try to git bisect the upstream xclock repository? Sure, no problem. I get $ git bisect log git-bisect start # bad: [1ea56dd7d67cef80f364fafcf985fb4a6846109d] Version bump: 1.0.3 git-bisect bad 1ea56dd7d67cef80f364fafcf985fb4a6846109d # good: [d335cefbbe5d23c410f8e8b7af0692559b649e67] Bump to 1.0.2 git-bisect good d335cefbbe5d23c410f8e8b7af0692559b649e67 # good: [41503ac2d7c84502074b3b6528478fe017060ef7] Add pointer to Xft/fontconfig font name format to man page git-bisect good 41503ac2d7c84502074b3b6528478fe017060ef7 # bad: [6f845b1d5516864e143113ca074e98b7be194adb] Change xclock_CFLAGS to AM_CFLAGS to make automake-1.10 happier git-bisect bad 6f845b1d5516864e143113ca074e98b7be194adb # bad: [a450fbb0f93f8bcdaabfb623fe49ddbb12468287] Man page: add missing options to synopsis section git-bisect bad a450fbb0f93f8bcdaabfb623fe49ddbb12468287 # bad: [8476e5fbddafc171903470000e86a68f66dc3958] Don't segfault if unable to load a usable fontset git-bisect bad 8476e5fbddafc171903470000e86a68f66dc3958 Please let me know if there's any other information you'd like me to provide. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
