-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nagstamon 3.14 not starting since Plasma 6 #1015
Comments
Hi @timodenissen, how bad. Actually Nagstamon supports Qt6, which Plasma 6 is based on too. So this is really strange. I will try to reproduce by setting up an Arch instance. |
Hi @timodenissen - do you know of an fast way to get an Arch Linux up and running? I did not expect to come out in a shell for installing. Don't get me wrong, I ❤️ shells, but looks more tenacious than assumed. |
@timodenissen another question: do you use Wayland or Xorg? |
@timodenissen how did you install Nagstamon? |
@HenriWahl The fastest way could be using I use the Plasma wayland session, with Plasma 5.27 this was not an issue. I installed Nagstamon via the AUR package. A clone of the repository also results in the same errros. |
+1 to the issue, after recent system upgrade Nagstamon won't load anymore. I also noticed that trying to run nagstamon via pdb-clone, I can get it to work but without any UI whatsover - I hear the sound of alerts, can see the process running, but UI appears for a fraction of a second and immediately crashes. Not sure how helpful it will be for debugging, but will leave the outputs, in
Output from pdb
$ ps auxf | grep -i "nagstamon"
alex 1308329 6.8 0.9 2679496 307964 pts/10 Sl+ 18:51 0:01 | | \_ /usr/bin/python /usr/bin/pdb-clone /usr/bin/nagstamon
alex 1308997 0.0 0.0 6572 2560 pts/14 S+ 18:51 0:00 | \_ grep --color=auto -i nagstamon
alex 1308441 0.0 0.0 268530852 25836 ? S 18:51 0:00 \_ /usr/lib/kf6/kioworker /usr/lib/qt6/plugins/kf6/kio/tags.so tags local:/run/user/1000/nagstamonFUaGdH.1.kioworker.socket $ pdb-clone /usr/bin/nagstamon
pdb-clone 1.10.1 (without the _bdb extension module).
> /usr/bin/nagstamon(21)<module>()
-> import sys
(Pdb) c
QLayout: Attempting to add QLayout "" to StatusWindow "", which already has a layout
QLayout: Attempting to add QLayout "" to StatusWindow "", which already has a layout
QLayout: Attempting to add QLayout "" to StatusWindow "", which already has a layout
DEBUG: 2024-03-15 18:54:51.612610 Saving configuration to file /home/alex/.nagstamon/nagstamon.conf
DEBUG: 2024-03-15 18:54:51.865950 QU Created server.
DEBUG: Initializing SystemTrayIcon
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0cdc0> for state "OK"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0cca0> for state "INFORMATION"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0ce50> for state "UNKNOWN"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0cee0> for state "WARNING"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0cf70> for state "AVERAGE"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d000> for state "HIGH"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d090> for state "CRITICAL"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d120> for state "DISASTER"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d1b0> for state "UNREACHABLE"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d240> for state "DOWN"
DEBUG: SystemTrayIcon created icon <Nagstamon.QUI.QIconWithFilename object at 0x7d2bf9b0d2d0> for state "ERROR"
DEBUG: SystemTrayIcon initial icon: <PyQt6.QtGui.QIcon object at 0x7d2bf9b0cb80>
DEBUG: 2024-03-15 18:54:52.315903 QU FetchURL: https://my.nagios.server.com/nagios/cgi-bin/status.cgi?hostgroup=all&style=hostdetail&hoststatustypes=12&hostprops=262144&limit=0 CGI Data: None
The program exited via sys.exit(). Exit status: 0
> /usr/bin/nagstamon(21)<module>()
-> import sys
(Pdb) DEBUG: 2024-03-15 18:54:52.370530 QU FetchURL: https://nagstamon.de/version/stable CGI Data: None
DEBUG: 2024-03-15 18:54:53.566737 QU FetchURL: https://my.nagios.server.com/nagios/cgi-bin/status.cgi?hostgroup=all&style=hostdetail&hoststatustypes=12&hostprops=524288&limit=0 CGI Data: None
DEBUG: 2024-03-15 18:54:54.490641 QU FetchURL: https://my.nagios.server.com/nagios/cgi-bin/status.cgi?host=all&servicestatustypes=253&serviceprops=262144&limit=0 CGI Data: None
DEBUG: 2024-03-15 18:54:55.755790 QU FetchURL: https://my.nagios.server.com/nagios/cgi-bin/status.cgi?host=all&servicestatustypes=253&serviceprops=524288&limit=0 CGI Data: None
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
DEBUG: 2024-03-15 18:54:56.628821 QU Filter: REGEXP <redacted>
DEBUG: 2024-03-15 18:54:56.628842 QU Filter: ACKNOWLEDGED <redacted>
DEBUG: 2024-03-15 18:54:56.628895 QU Filter: ACKNOWLEDGED <redacted>
... |
@timodenissen thanks for the hint with What is your desktop session manager? I choose the default sddm (or something like that) with Wayland. Edit: Now I used X11 instead of Wayland and now I get a KDE desktop after logging in. |
I use SDDM with no special configuration. Please be aware that X11 is no longer supported by Plasma 6 and may falsify reproducing the error. |
Yes, I think checking it with Wayland is definitely more useful. I will try to get it running. |
At least got Wayland session of Plasma6 running in VM. Now the next questions as non-Arch-user: where did you install Nagstamon from? Edit: Found it. Edit 2: I can confirm the immediate crash. |
@timodenissen this are my findings:
I assume that the Qt6 version in Arch causes the trouble somehow, because the crash happens as soon GUI is involved. Via
|
@timodenissen the mention of |
@timodenissen well, I installed the not yet installed package pulseaudio-qt and now there is no crash. Can you reproduce this? |
@HenriWahl , @timodenissen I am sorry for stepping in. I personally use Endeavour OS (arch based) which also seems to have an issue with nagstamon after updating to Plasma 6. I also have the |
@HenriWahl Sorry for the late reply, I was on vacation. That's interesting, my sound server is pipewire: pactl info | grep "Server Name"
Server Name: PulseAudio (on PipeWire 1.0.4) I could try switching back to PulseAudio and see if that would solve the issue, but that has to wait until tonight. @bouzouste Thanks for the hint :) Unfortunately the crash also occurs with a complete new and empty Nagstamon profile =/ |
@timodenissen I confirm that the app crashes even when there is no configuration. However, If you already have a conf file, you could try changing the following two lines:
so that the floating status bar is disabled, and it (probably) won't crash. If on the other hand, you don't have any configuration available, then you could try using an older version of nagstamon (3.8.0 or older) which seems to be working without issues (versions 3.8.1+ to 3.14+ seem to not like plasma 6) |
@bouzouste Thanks, now Nagstamon's not crashing but shows me a flashing tray icon (expected) but unfortunately I need the window =/ I wait for @HenriWahl to check and add a fix (not that much of a coder myself) or wait for the flatpak to update to latest stable (currently 3.6.0, which somehow can't work with our Prometheus Alert Manager). In the meantime I check the Nagios and Prometheus Alert Manager with their respective web interfaces. |
@timodenissen strange thing that the window isn't working. Well, maybe you could test the 3.14 flatpak release currently being in development at flathub/de.ifw_dresden.nagstamon#8 |
https://flathub.org/apps/de.nagstamon.nagstamon is finally out. |
Fedora 40, Plasma 6. Neither 3.14 from flathub (de.nagstamon.nagstamon), nor 3.14 (or 3.15 from the "latest" repo) RPMs work. This is after manually permitting flatpak access to system and session buses. Without it (by default) it additionally gives multiple errors like this: |
Even after updating to Python 3.12, Nagstamon 3.14 won't show the GUI, neither does using the flatpak |
@timodenissen please try the new flatpak de.nagstamon.nagstamon |
@bbhtt do you think the permissions should be increased? |
@HenriWahl same behaviour for me with the latest flatpak as with running from the tar.gz, the UI flashes and immediately closes.
|
It does not need system or session bus. You need to figure out which bus name it tries to connect to by running it with |
I did a quick test with the latest main branch: cd /tmp
git clone https://github.com/HenriWahl/Nagstamon.git
cd Nagstamon
python ./setup.py build
python ./build/scripts-3.12/nagstamon.py results in
Same error - the status window doesn't open. When stopping
Running the latest flatpak |
With some recent QT updates, I now get these new messages:
|
Does it run? And in which context did you get this updates? On your Linux system or in virtualenv? |
Regular updates on my productive laptop with Arch Linux. The flatpak still doesn't work and still won't show a GUI as well. The following QT packages are installed:
|
Okay now this is strange... I have no new Arch updates installed since yesterday and wanted to dive deepter into debugging. I installed Nagstamon via flatpak in an Ubuntu 24.04 VM and it worked, went back to Arch and... now it's working. After cloning this repository to Running Nagstamon via the AUR package works as intended again. For me this issue is resolved. |
I still can't run nagstamon, either from flatpak or from git, under X11 or Wayland. Under Wayland from git I get additional errors, maybe due to Fedora's python version (3.12.3)?:
|
OK, those additional errors are fixed/silenced with this Arch fix:
Still, nagstamon is not working for me :( |
Really strange, nice to hear it is solved for you. |
Using Arch Linux with the most recent Plasma 6 update, Nagstamon 3.14 no longer starts.
Cleaning my configuration to make sure it's not a profile problem:
Starting Nagstamon from Konsole via
nagstamon
crashes:Running from
bash
results in:ps auxf | grep -i "nagstamon"
shows no Nagstamon process is running.Prior the Plasma 6 update (with Plasma 5.27) everything worked just fine.
The text was updated successfully, but these errors were encountered: