Demo
Discussion
Forum
Config Examples
Contributions
Vulnerabilities
Discussion forum about ELOG, Page 178 of 807
Not logged in
Find
|
Login
|
Help
Full
| Summary |
Threaded
-- All entries --
Last day
Last 3 Days
Last week
Last month
Last 3 Months
Last 6 Months
Last Year
-- Category --
Info
Bug report
Bug fix
Question
Request
Comment
Other
6450 Entries
Goto page
Previous
1
,
2
,
3
...
177
, 178,
179
...
805
,
806
,
807
Next
ID
Date
Icon
Author
Author Email
Category
OS
ELOG Version
Subject
Text
68913
Tue Mar 19 23:24:48 2019
Ross Gibson
ross.gibson@newcastle.edu.auSince
updating to ver
Question
Windows
3.1.4
HTML editor not working after updating to V3.1.4
Since 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
Stefan Ritt
stefan.ritt@psi.ch
Question
Windows
3.1.4
Re: HTML editor not working after updating to V3.1.4
Have 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
Ross Gibson
ross.gibson@newcastle.edu.au
Question
Windows
3.1.4
Re: 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
Alessio Sarti
alessio.sarti@uniroma1.it
Bug report
Mac OSX
3.1.4
elogd Service exited with abnormal code: 1
Dear all.
I am running elog
elogd
68933
Tue Apr 23 14:26:51 2019
Stefan Ritt
stefan.ritt@psi.ch
Bug report
Mac OSX
3.1.4
Re: elogd Service exited with abnormal code: 1
This 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
Alessio Sarti
alessio.sarti@uniroma1.it
Bug report
Mac OSX
3.1.4
Re: elogd Service exited with abnormal code: 1
Thanks for the prompt feedback.
a) I confirm that the problems
shows up also when running interactively
68943
Thu Apr 25 11:27:21 2019
Stefan Ritt
stefan.ritt@psi.ch
Bug report
Mac OSX
3.1.4
Re: elogd Service exited with abnormal code: 1
What 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
Alessio Sarti
alessio.sarti@uniroma1.it
Bug report
Mac OSX
3.1.4
Re: elogd Service exited with abnormal code: 1
I was finally able to catch the crash.
I paste below the info provided
by lldb..
Goto page
Previous
1
,
2
,
3
...
177
, 178,
179
...
805
,
806
,
807
Next
ELOG V3.1.5-3fb85fa6