Previously working OpenSnitch UI fails to start (Fedora 39 / python3.12)

[eisraeli]

OpenSnitch UI ran perfectly on my system until recently I've noticed it's no longer starting after reboots.

Running opensnitch-ui from my terminal results in the following errors:

$ opensnitch-ui                  
/usr/lib/python3/dist-packages/opensnitch/dialogs/prompt.py:569: SyntaxWarning: invalid escape sequence '\.'
  dsthost = '\.'.join(text.split('.')).replace("*", "")
/usr/lib/python3/dist-packages/opensnitch/dialogs/prompt.py:570: SyntaxWarning: invalid escape sequence '\.'
  dsthost = "^(|.*\.)%s" % dsthost[2:]
/usr/lib/python3/dist-packages/opensnitch/dialogs/prompt.py:576: SyntaxWarning: invalid escape sequence '\.'
  return Config.RULE_TYPE_REGEXP, Config.OPERAND_DEST_IP, "%s" % '\.'.join(text.split('.')).replace("*", ".*")
/usr/lib/python3/dist-packages/opensnitch/utils/__init__.py:404: SyntaxWarning: invalid escape sequence '\-'
  g = re.search("([a-zA-Z0-9\-]+)( |\t)+([0-9]+)\/([a-zA-Z0-9\-]+)(.*)\n", line)
Themes not available. Install qt-material if you want to change GUI's appearance: pip3 install qt-material.
/usr/lib/python3/dist-packages/opensnitch/desktop_parser.py:52: SyntaxWarning: invalid escape sequence '\/'
  is_flatpak = re.search("^/usr/[s]*bin/flatpak.*--command=([a-zA-Z0-9-_\/\.\+]+)", cmd)
[1]    12982 segmentation fault (core dumped)  opensnitch-ui

OpenSnitch: 1.6.2 OS: Fedora release 39 (Thirty Nine) x86_64 Kernel: 6.6.13-200.fc39.x86_64 Desktop: KDE Plasma 5.27.10

[eisraeli]

Update: I've updated opensnitch-ui to the latest version (1.6.4) , now I'm just getting:

$ opensnitch-ui
[1]    14124 segmentation fault (core dumped)  opensnitch-ui

[gustavo-iniguez-goya]

Hi @eisraeli ,

mmh, let me see if I can reproduce it. Thank you for the report!

[edit] reproduced, figuring out what's going on and how to fix it.

[gustavo-iniguez-goya]

@eisraeli , I've just updated my Fedora 39 and the problem seems to be fixed, probably it was a regression in Fedora's python3/pyqt5.

Could you update your system and verify that it works?

[eisraeli]

Thanks @gustavo-iniguez-goya It was indeed a qt5 related issue.
Closing this issue.