ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69881
|
Fri Jul 18 17:46:43 2025 |
| mathew goebel | mgoebel@emich.edu | Question | Linux | V3.1.5-30a | once a week we are having elogd segault? |
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
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this? |
69875
|
Mon May 5 11:39:17 2025 |
| Pawel Nita | pawel.nita@uj.edu.pl | Bug report | Linux | V3.1.3-7933898 | WYSIWYG Editor Not Showing in HTML Mode |
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.
Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!
Thanks in advance,
Pawel |
Draft
|
Mon May 5 11:47:11 2025 |
| John | Hjohn@secondcomingtechnologies.com | Bug report | Linux | V3.1.3-7933898 | Re: WYSIWYG Editor Not Showing in HTML Mode |
Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am
Pawel Nita wrote: |
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.
Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!
Thanks in advance,
Pawel
|
|
Draft
|
Mon May 5 13:50:12 2025 |
| Pawel Nita | pawel.nita@uj.edu.pl | Bug report | Linux | V3.1.3-7933898 | Re: WYSIWYG Editor Not Showing in HTML Mode |
Hi John,
Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing. I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.
Best regards,
Pawel
John wrote: |
Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am
Pawel Nita wrote: |
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.
Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!
Thanks in advance,
Pawel
|
|
|
69877
|
Mon May 5 13:50:12 2025 |
| Pawel Nita | pawel.nita@uj.edu.pl | Bug report | Linux | V3.1.3-7933898 | Re: WYSIWYG Editor Not Showing in HTML Mode |
Hi John,
Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing. I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.
John wrote: |
Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am
Pawel Nita wrote: |
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.
Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!
Thanks in advance,
Pawel
|
|
|
67703
|
Tue Sep 16 17:59:27 2014 |
| Chris Jennings | cjennings@cosma.com | Bug report | Windows | V2.9.2-24 | Sort by date prior to 2002 |
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris |
67704
|
Tue Sep 16 18:05:41 2014 |
| Chris Jennings | cjennings@cosma.com | Bug report | Windows | V2.9.2-24 | Re: Sort by date prior to 2002 |
Chris Jennings wrote: |
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort. |
67705
|
Wed Sep 17 17:45:18 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | V2.9.2-24 | Re: Sort by date prior to 2002 |
Chris Jennings wrote: |
Chris Jennings wrote: |
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.
|
I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.
Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.
Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!  |