Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 178 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  68913   Tue Mar 19 23:24:48 2019 Question Ross Gibsonross.gibson@newcastle.edu.auSince updating to verQuestionWindows3.1.4HTML editor not working after updating to V3.1.4Since updating to v3.1.4 the HTML editor has
stopped working. If I switch to HTML encoding,
the editor appears with a blank field, cannot
  
  68914   Wed Mar 20 01:12:36 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.4Re: HTML editor not working after updating to V3.1.4Have you cleared your browser cache? There
might be some old JavaScript stored there.
If that does not help, remove elog and reinstall
  
  68915   Wed Mar 20 06:50:57 2019 Reply Ross Gibsonross.gibson@newcastle.edu.auQuestionWindows3.1.4Re: HTML editor not working after updating to V3.1.4
Thanks Stefan. Tried these without success.
I tried opening in another browser and it
  
  68932   Tue Apr 23 14:06:36 2019 Warning Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4elogd Service exited with abnormal code: 1Dear all.

I am running elog 

elogd
  
  68933   Tue Apr 23 14:26:51 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1This kind of behavior we typically see
if some elog entry is corrupt. After a few
hours you might access this corrupt entry
  
  68942   Thu Apr 25 11:16:06 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Thanks for the prompt feedback.

a) I confirm that the problems
shows up also when running interactively
  
  68943   Thu Apr 25 11:27:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1What you recommend is enough. Just make
sure to compile elogd with the flags mentioned
before, and when you get the segment violation,
  
  68951   Tue Apr 30 12:47:46 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1I was finally able to catch the crash.

I paste below the info provided
by lldb..
  
ELOG V3.1.5-3fb85fa6