Saw your comment on Bodhi first, so copy-and-pasting here:
What error do you get? Gajim does not contain any references to the axolotl module, so I would assume that any errors are rather due to changes in the omemo plugin (https://dev.gajim.org/gajim/gajim-plugins) but I don't see any relevant changes there.

I did some tests to reproduce the bug.

 * With gajim-1.4.3-1.fc36.noarch package installed:

```
$ gajim
07/06/2022 19:45:30 (W) gajim.c.storage.cache      Execution time for _load_caps_data: 59 ms
07/06/2022 19:45:31 (E) gajim.p.omemo              No module named 'google'
07/06/2022 19:45:31 (E) gajim.p.omemo              No module named 'axolotl'
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/gajim/common/ged.py", line 101, in raise_event
    if handler(event_obj):
  File "/usr/lib/python3.10/site-packages/gajim/remote_control.py", line 319, in on_presence_received
    if obj.old_show < 2 and obj.new_show > 1:
TypeError: '>' not supported between instances of 'str' and 'int'
```

When I check the plugins, OMEMO is no more enabled with a warning message "You are missing Python3-Axololt or use an outdated version."


 * With gajim-1.4.2-1.fc36.noarch package installed:

```
$ gajim
/usr/lib/python3.10/site-packages/gajim/common/jingle_rtp.py:31: PyGIWarning: Farstream was imported without specifying a version first. Use gi.require_version('Farstream', '0.2') before import to ensure that the right version gets loaded.
  from gi.repository import Farstream
/usr/lib/python3.10/site-packages/gajim/common/preview_helpers.py:34: PyGIWarning: GstPbutils was imported without specifying a version first. Use gi.require_version('GstPbutils', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import GstPbutils
07/06/2022 19:56:30 (W) gajim.c.storage.cache      Execution time for _load_caps_data: 58 ms

07/06/2022 19:56:40 (E) gajim.c.ged                Error while running an event handler: <bound method GajimRemote.on_presence_received of <gajim.remote_control.GajimRemote object at 0x7f3a12df1180>>
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/gajim/common/ged.py", line 101, in raise_event
    if handler(event_obj):
  File "/usr/lib/python3.10/site-packages/gajim/remote_control.py", line 319, in on_presence_received
    if obj.old_show < 2 and obj.new_show > 1:
TypeError: '>' not supported between instances of 'str' and 'int'

(org.gajim.Gajim:97717): Gtk-CRITICAL **: 19:58:15.968: gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

```

When I check the plugins, OMEMO is enabled and works well.

Something must have changed somewhere regarding the OMEMO plugin.

The error occurs if the setting 'remote_control' is activated in ACE (which is deactivated by default) and has nothing to do with OMEMO.

The upstream issue is: https://dev.gajim.org/gajim/gajim/-/issues/10934

Thank you zak for your answer and the link.

I think this setting was enabled in older versions and indeed has nothing to do with OMEMO.

The problem lies in the two new errors that appeared after the upgrade to version 1.4.3:
```
07/06/2022 19:45:31 (E) gajim.p.omemo              No module named 'google'
07/06/2022 19:45:31 (E) gajim.p.omemo              No module named 'axolotl'
```

I compared the binaries of versions 1.4.2 and 1.4.3: Due to the update to the newer Python packaging guidelines, the "gajim" binary is now generated differently, which probably has the side effect of not finding locally installed pip modules anymore. I'm not sure whether we can easily fix that.

You are right. Indeed locally installed pip modules are not found anymore.

I uninstalled local pip module **python-axolotl**:
```
$ pip3 uninstall python-axolotl
Found existing installation: python-axolotl 0.2.3
Uninstalling python-axolotl-0.2.3:
  Would remove:
    /home/<username>/.local/lib/python3.10/site-packages/axolotl/*
    /home/<username>/.local/lib/python3.10/site-packages/python_axolotl-0.2.3.dist-info/*
Proceed (Y/n)? Y
  Successfully uninstalled python-axolotl-0.2.3
```

And after I enabled copr repository philfry/gajim and installed **python3-axolotl**:
```
$ sudo dnf copr enable philfry/gajim
$ sudo dnf install python3-axolotl
```

And now OMEMO works well with gajim-1.4.3-1.fc36.noarch \o/

The new packages included in the official Fedora repository could be a relevant solution:
 - bug2043228
 - bug2043231

Thanks for the hint! I hadn't noticed that they were reviewed and included now. I will add them as recommends once they are available in updates.

Oops! I didn't see that they were available via updates-testing. So I removed the packages provided by philfry/gajim and deleted this repository.

Everything works fine with the packages provided by updates-testing.

Thank you very much for your help!

So there is just the problem of having modules installed with pip that are not found.

Great to hear! I'll add this bug to the update in bodhi: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0a4335d91

I think the status should be updated to POST for it to be automatically updated?

FEDORA-2022-d0a4335d91 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d0a4335d91

FEDORA-2022-d0a4335d91 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.