custom module not shown anymore

[bobblkabb]

Got a custom module which used to work until a few days ago:

    "custom/vpn": {
        "interval": 1,
        "return-type": "json",
        "exec": "vpntool.py infojson 2> /dev/null",
        "format": "󰌆   {}",
        "on-click": "vpntool.py an",
        "on-click-middle": "vpntool.py aus",
        "tooltip": true,
        "align": 0,
        "min-length": 18
    },

waybar -l debug doesn't show anything interesting, instead of
[error] Item '': No icon name or pixmap given.

Got waybar 0.12 running on openSUSE Tumbleweed.
Any idea what's going wrong?

[RobertMueller2]

The error message above is from the tray module, so probably unrelated. Can you clarify what isn't working anymore? The display, update, events, all of it?

[bobblkabb]

The module is completely gone, not just invisible. Replaced the icon with text, it's not a display problem it's just vanished.

config.txt

[RobertMueller2]

The module config as such doesn't have a problem in my environment. However, if I use it as is, the module remains disabled. This can be observed by using GTK_DEBUG=interactive. Of course that happens because I don't have vpntool.py, once I replace it with a shell scripts that's producing json, the module works.

The module is disabled:

• if exec output is empty
• if exec command exits with anything else than 0
• if hide-empty-text is set and text variable is empty (this is not relevant here because you have not set the option)

For further troubleshooting, I suggest to

• try GTK_DEBUG=interactive to confirm you see a disabled module too
• run vpntool.py infojson manually and confirm output and exit level
• sometimes output flushing is an issue, but I think since vpntool.py is not a looping script that shouldn't play a role here
• I think it might be interesting to find out whether it was waybar that was updated a few days ago when this stopped working, or something else. I think a waybar update is likely given the recent release, but to be honest, I don't really see anything in the commit history that's likely to have broken this since 0.11.0.

[bobblkabb]

That's it!
Python 3.13 was installed besides 3.11 but without the pandas module I had before. Didn't recognize the switch from 3.11 to 3.13.

Vielen Dank!