This happened only after the update this weekend. Previous update was on the weekend before (25 June).
There have been some commits within this range of dates: http://trac.enlightenment.org/e/changeset/60813/trunk/e/src http://trac.enlightenment.org/e/changeset/60814/trunk/e/src http://trac.enlightenment.org/e/changeset/60815/trunk/e/src Here are my variables: ~> env | grep -E '(LC|LANG|LOC)' E_LOCALE_DIR=/usr/share/locale LIBXCB_ALLOW_SLOPPY_LOCK=1 SAGE_LOCAL=/usr LC_ALL=en_US.ISO-8859-1 ~> grep -E '(LC|LANG|LOC)' /etc/zsh/* /etc/profile* ~/.zshrc /etc/profile.env:export LIBXCB_ALLOW_SLOPPY_LOCK='1' /etc/profile.env:export SAGE_LOCAL='/usr' Actually, I am surprised that LC_ALL is set to this. I am quite sure I had set it to en_US.UTF8 while installing the system. Anyway, e17's lang module shows up some garbage in the advanced settings. But the basic settings seem to show the correct locale: http://ompldr.org/vOWN5aQ So, is it "spank spank raster" or some problem with my locale? :P On 07/05/2011 09:12 AM, Christopher Michael wrote: > I had a similar problem earlier. I solved it by adding > > export LANG=C > > to my ~/.bashrc. Then logout and login again and it's gone ;) > > dh > > > On 07/04/11 21:13, P Purkayastha wrote: >> Hi, >> I am getting segv on e17 restarts. Seems to have to do something with >> the language module. >> >> The gdb log is attached. >> >> ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
