This is not new, it happened with .21 as well for what it seems. http://bugs.gentoo.org/121339 Since this belongs upstream, I suggest disabling nls completely in the ebuild. People having this problem can't figure why the hell xlock doesn't work, and utf8 is the standard nowadays, so that's a BIG percentage of the users which are being bitten by this bug. I suggest to rip out the unicode flag and let it compile without unicode support. I prefer to ditch a feature that doesn't work that not to be able to use the program because it segfaults anyway when you try to use the feature. Reproducible: Always Steps to Reproduce: 1.emerge xlockmore 2.have an utf8 locale 3.run xlock and watch it segfaults, it's automatic Actual Results: it segfaults Expected Results: it shouldn't segfault and it should lock your screen with a "nice" screensaver
Created attachment 197212 [details] Proposal of ebuild that will not segfault
+ 11 Jul 2009; Samuli Suominen <ssuominen@gentoo.org> xlockmore-5.28.ebuild: + Remove USE unicode wrt #277061. Introduce --enable-ttf back because it + can't find fonts wrt #272232.
For me this fixed xglock's previewing segfault.
Thanks for fixing this one.