http://bugzilla.opensuse.org/show_bug.cgi?id=1176388
Bug ID: 1176388 Summary: OMEMO plugin for Tumbleweed doesn't work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: opensuse@trummer.xyz QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
(from https://build.opensuse.org/package/show/network/gajim#comment-1305719 )
It seems that Gajim 1.2 doesn't work with the old OMEMO plugin version 2.6.29 anymore. The easiest way would be to just update the plugin to the latest version for the 1.2 branch - 2.6.80, see https://dev.gajim.org/gajim/gajim-plugins/-/blob/master/README.md
But the Gajim 1.1 branch that Leap 15.2 and 15.1 have only works with the plugin until version 2.6.30: https://dev.gajim.org/gajim/gajim-plugins/-/blob/gajim_1.1/omemo/CHANGELOG
http://bugzilla.opensuse.org/show_bug.cgi?id=1176388
Maximilian Trummer opensuse@trummer.xyz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sor.alexei@meowr.ru
http://bugzilla.opensuse.org/show_bug.cgi?id=1176388
Maximilian Trummer opensuse@trummer.xyz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dmueller@suse.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1176388 http://bugzilla.opensuse.org/show_bug.cgi?id=1176388#c3
--- Comment #3 from Maximilian Trummer opensuse@trummer.xyz --- June 31st, huh... Anyway, thanks!
http://bugzilla.opensuse.org/show_bug.cgi?id=1176388 http://bugzilla.opensuse.org/show_bug.cgi?id=1176388#c4
Sebastian Wagner sebix+novell.com@sebix.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |sebix+novell.com@sebix.at Resolution|--- |FIXED
--- Comment #4 from Sebastian Wagner sebix+novell.com@sebix.at --- I think it was forgotten to close this old and apparently fixed bug report