commit b7bf048e7a1b621274841ef40e017adabae5b8e3 Author: hurzl <hu...@online.de> Date: Fri Nov 20 02:51:32 2015 +0100
just compiled up the latest git commit - manually - and it works perfectly. no LIBGL_ALWAYS_SOFTWARE=1 is required. this would indeed tend to suggest that there is a misconfigured dependency: a minor variation in what i have installed and what's specified as "compatible / acceptable". i suspect that somewhere there's a function whose parameters have changed on a minor revision number, that repsnapper was compiled up with that version, that the Package file says "anything >= x.x.x is ok" but actually it's not ok at all. does that ring true at all as a plausible hypothesis? l. --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 24, 2016 at 9:51 PM, Luke Kenneth Casson Leighton <l...@lkcl.net> wrote: >> Hi Luke, >> >> Can you try "env LIBGL_ALWAYS_SOFTWARE=1 repsnapper" to see if it fixes? > > ok i can confirm that the latest version is working. also the > (just-reported) bug with glib also goes away. so that one can be > closed. > > l.
