Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 747 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject Text Attachments
  69063   Fri Nov 22 02:55:50 2019 Warning John S. Haggertyhaggerty@bnl.govBug reportMac OSX3.1.4Trouble on CatalinaI decided to rebuild elog 3.1.4 in Catalina
(MacOS 10.15.1), XCode 11.2.1.  As in
previous builds, I needed to add to the Makefile
  
  69066   Mon Nov 25 16:25:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: Trouble on CatalinaThe Makefile is kind of obsolete, I switched
to CMake. So the Makefiel is mostly there
as backup. To compile elog, do
  
  69076   Thu Dec 19 16:28:06 2019 Warning Devin Bougiedab66@cornell.eduBug reportLinux | Windows | Mac OSX | All | Other3.1.4text wrapping broken in firefoxWhen creating new logbook entries, recent
versions of firefox somehow ignore the message
width setting.
  
  69077   Thu Dec 19 16:40:10 2019 Reply Devin Bougiedab66@cornell.eduBug reportLinux | Windows | Mac OSX | All | Other3.1.4Re: text wrapping broken in firefoxAs an example, I created this same entry in
the demo logbook using Safari.  As you can
see there, the message is wrapped at the
  
  69089   Fri Jan 24 14:56:04 2020 Warning Sara Vaninivanini.sara@gmail.comBug reportLinux3.1.3editor hangs intermittentlyHello,

I'm using ELOG with Ubuntu
19. When I create or edit an entry and I
  
  69099   Fri Jan 31 15:17:04 2020 Warning Laurent Jean-Rigaudlollspam@free.frBug reportLinux3.14 RPMElogd crashes on searchOS: CentOS 7 x86_64 up2date with RPM 3.14
x86_64


Connexion to ELOG
open
  
  69100   Fri Jan 31 15:27:21 2020 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.14 RPMRe: Elogd crashes on searchDo you see the same problem on this server
here?

If not, then it must be related
  
  69101   Fri Jan 31 15:34:56 2020 Reply Laurent Jean-Rigaudlollspam@free.frBug reportLinux3.14 RPMRe: Elogd crashes on searchHi Stefan,

The problem seems to be specific
with our logbooks. Maybe one of the file
  
ELOG V3.1.5-3fb85fa6