#815762 nagstamon Unicode problems

Package:
nagstamon
Source:
nagstamon
Submitter:
Christoph Goesgens
Date:
2024-02-27 09:51:15 UTC
Severity:
important
Tags:
#815762#5
Date:
2016-02-24 10:56:28 UTC
From:
To:
Hi!

Nagstamon appears to have problems with Unicode.

We currently have two Certificates in the list of problems, which expire
in March ("März" in German).

When you open the list in the nagios webinterface it's displayed like this:

WARNING - Certificate 'sub.domain.de' expires in 19 day(s) (Fr 11
Mär 2016 23:59:00 CET).

In Nagstamon the line only goes to the M of "Mär" and then usually broken
glyphs appear.

This also sometimes leads to later lines _missing_ in nagstamon, which is
why i rated this report important. When this happens, no broken glyphs
appear after the M, the next line is complete except for the "Status
Information", and all later lines are missing completely.

The browser reports that the webinterface is in "Unicode", no idea if it's
UTF-8 or something else. I didn't see a declared encoding in the source code.

Nagios itself is also installed from the debian packages, version 3.5.1 on
Jessie.

Regards,
Christoph

#815762#10
Date:
2017-04-24 10:44:39 UTC
From:
To:
Dear Reporter,

Nagstamon has been largely rewritten for version 2.0, which has probably
fixed many bugs, maybe also the one you have reported here.

Version 2.0.1 is currently packaged in testing (Stretch) and available
as a backport for the stable distribution (Jessie):
https://tracker.debian.org/pkg/nagstamon

Please help me by testing whether the reported bug still exists in
version 2.0.1 of Nagstamon and sending a quick reply to this bug report.
Please also just tell me if you don't use Nagstamon anymore and thus are
unable to reproduce it at all.

Regards,
Moritz Schlarb

#815762#15
Date:
2017-04-24 10:46:31 UTC
From:
To:
Dear Reporter,

Nagstamon has been largely rewritten for version 2.0, which has probably
fixed many bugs, maybe also the one you have reported here.

Version 2.0.1 is currently packaged in testing (Stretch) and available
as a backport for the stable distribution (Jessie):
https://tracker.debian.org/pkg/nagstamon

Please help me by testing whether the reported bug still exists in
version 2.0.1 of Nagstamon and sending a quick reply to this bug report.
Please also just tell me if you don't use Nagstamon anymore and thus are
unable to reproduce it at all.

Regards,
Moritz Schlarb

#815762#22
Date:
2024-02-27 09:42:01 UTC
From:
To:
# Since not receiving any more feedback, I assume these are long done
close 599263
# Since not receiving any more feedback, I assume these are long done
close 675020
# Since not receiving any more feedback, I assume these are long done
close 718230
# Since not receiving any more feedback, I assume these are long done
close 815762
# Closed by upstream
close 889866
# Closed by upstream
close 944646
# Already fixed for so long ;)
fixed 599260 nagstamon/0.9.5-1
close 599260
# Since this conversion happened so long ago, I consider this not relevant for currently supported releases anymore
close 673940
close 767506 nagstamon/2.0.1-1
thanks