#718230 nagstamon: fails to open GUI after fresh install

Package:
nagstamon
Source:
nagstamon
Submitter:
Vincent McIntyre
Date:
2024-02-27 09:51:13 UTC
Severity:
normal
Tags:
#718230#5
Date:
2013-07-29 00:12:34 UTC
From:
To:
% sudo apt-get install nagstamon
% nagstamon
Traceback (most recent call last):
  File "/usr/bin/nagstamon", line 89, in <module>
    GUI.Settings(servers=servers, output=output, conf=conf)
  File "/usr/share/nagstamon/Nagstamon/GUI.py", line 2076, in __init__
    self.builder.add_from_file(self.builderfile)
glib.GError: Unknown internal child: selection

The 'desktop' is fvwm, started with startx.
Is nagstamon expecting some service only provided by gnome/kde/xfce?

The manpage mentions a 'configuration file' but does not disclose
the filesystem location of the file. The upstream docs do not either,
as far as I can see. From reading /usr/bin/nagstamon it appears to be
/usr/share/nagstamon/Nagstamon/Config.py.
That code also checks for 'nagstamon.conf' in various places.
I can find no discussion of what contents nagstamon.conf should have.
The documentation perhaps should be a separate bug -
'no documentation of config file' or so, but that's your call.

Cheers
Vince
#718230#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
#718230#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
#718230#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