3-level conditional not working, posted by Harry Martin on Thu Mar 20 07:34:24 2025
|
Not sure if this is a bug or not; if it is not, kindly reclassify the category.
Following is a small example of what I will dub a 3-level, conditional logbook:
[cond_test] |
|
Re: 3-level conditional not working, posted by Harry Martin on Sun Jul 20 23:20:02 2025
|
Tried a variant, this time for NEW entries (not EDIT), which I meant to do to begin with; sorry if that was confusing.
[cond_test]
attributes = region, manufacturer, model |
|
collapse does not seem to work as expected, posted by Harry Martin on Thu Jul 17 23:43:25 2025
|
When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire
thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3. |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Fri Jul 18 22:42:02 2025
|
I should add that this does not happen in every logbook. I'm looking into what the distinction is that causes this in certain logbooks and
not in others.
Harry |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Fri Jul 18 23:10:33 2025
|
Figured it out: I had "Sort Attributes" set on the logbooks that were failing to collapse correctly. At least, I think that is
the distinction.
I think I can live with "Sort Attributes" disabled; I don't recall why I chose to set the "Sort Attributes" in the first |
|
Re: collapse does not seem to work as expected, posted by Harry Martin on Sat Jul 19 00:02:45 2025
|
I also notice that collapse does not work properly if I have anything selected in the quick filter.
Harry
Martin wrote:
Figured it out: I had "Sort Attributes" set on the |
once a week we are having elogd segault?, posted by mathew goebel on Fri Jul 18 17:46:43 2025
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df |
|
passing %s to $shell interpreted differently in preset vs preset on reply, posted by Harry Martin on Wed Jun 18 01:20:47 2025
|
I am finding that '%s' passed to a $shell(...) command must be escaped when calling
from Preset on reply, but not when calling Preset
new. Example: |
WYSIWYG Editor Not Showing in HTML Mode, posted by Pawel Nita on Mon May 5 11:39:17 2025
|
Hi all,
I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple
browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area. |
Re: Custom input forms implementation , posted by Marcel Zauner-Wieczorek on Mon Apr 28 11:50:25 2025
|
Please excuse my double-posting. But my first entry was not displayed on the forum and I haven't received feedback yet. I think this is because I
responded to an entry that was still in draft mode, whereas my entry was a "normal" entry. My initial entry has the Message ID: 69870 and was
in reply to: 68348 |
Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 18:45:49 2024 
|
I am receiving a segfault whenever I attempt to upload a file. Please see attached .txt for valgrind output. This occurs in version
elog-3.1.5-1. I reverted back to version elog-3.1.4-3 and the segfault does not occur.
Segfault occurs in Elog version: elog-3.1.5-1 |
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 19:01:39 2024
|
Looks like duplicate report to https://elog.psi.ch/elogs/Forum/69826
gary
holman wrote:
I am receiving a segfault whenever I attempt to upload a file. |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Thu Dec 12 19:46:02 2024
|
A statement like "core dumped" does not help much. Same with valgrind memory leaks. I need a full strack trace with all parameters when the
segment violation occurs. The easiest is when you run elogd vom inside gdb, and once you get the signal, do a "where" to see th full stack trace.
As you can see from this forum, there is absolutely no crash when you upload any file, so it must have to do with your config file or anything |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 20:29:40 2024
|
Thanks for further instructions here is full stack trace:
Program received signal SIGABRT, Aborted. |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Fri Dec 13 15:11:08 2024
|
Thanks to your stack trace, I found a case where a string might get overwritten, but only if the attachment file name is longer than 256 chars. I fixed
the code and made a new RPM:
https://www.dropbox.com/scl/fi/r37qx9aka5ytt3j7vn4km/elog-3.1.5-20241213.el8.x86_64.rpm?rlkey=knct99pdltggunrbmyr2hpfe5&st=pkre24aq&dl=0 |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Fri Dec 13 19:40:57 2024
|
Thanks Stefen!
I built from source (ELOG V3.1.5-3a5f2f00) and I confirmed as fixed.
|
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Evinrude Motor on Tue Jan 7 20:35:23 2025
|
When will the new source be in the standard download area ? I'm on ubuntu .
gary
holman wrote:
Thanks Stefen! |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Tue Jan 7 20:41:13 2025
|
It is in the usual download area which is referenced at https://elog.psi.ch/elog/download.html
Stefan
Evinrude |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Evinrude Motor on Sun Apr 13 13:56:05 2025
|
So this never made it into the download area ? elog-latest.tar is elog-3.1.5-1 and contains no files from 2024 or 2025 .
Thanks |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Thu Apr 17 13:10:43 2025
|
I stopped making tar files, since most people building elog from sources just pull it from the bitbucket repository:
$ git clone https://bitbucket.org/ritt/elog --recursive
$ cd elog |
|
New elog from template should update the subdir, posted by Liam Gaffney on Wed Apr 2 13:01:34 2025
|
Hello. We are using explicity subdir names on our elog server to manage a large number of "Top groups" and sub "groups". When we
create a new logbook from a template in the same group, it would be beneficial to automatically give a new subdir based on the previous one. At the very
least, it should not reuse the same parameter as the template (see below). |