Bug 2091518

Summary:	Jabber (XMPP) does not reconnect after waking up from standby since 2.14.8-3
Product:	[Fedora] Fedora	Reporter:	Martin Wolf <mwolf>
Component:	pidgin	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	jskarvad, redhat-bugzilla, stu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-25 16:57:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Wolf 2022-05-30 08:05:08 UTC

Description of problem:
Jabber (XMPP) does not reconnect after waking up from standby since 2.14.8-3

Version-Release number of selected component (if applicable):
2.14.8-3

How reproducible:
Install latest version

Steps to Reproduce:
1. log into a Jabber Account.
2. send PC to standby
3. check if Jabber reconnects 

Actual results:
Jabber account does not reconnect - Pidgin just says "connecting" but does nothing

Expected results:
Reconnect with server after Standby

Additional info:
Rolling back to 2.14.8-2 fixes the problem.
It must have something to do with the CVE-2022-26491 fix jskarvad applied.

Comment 1 Martin Wolf 2022-05-30 23:01:05 UTC

this patch seems to fix my issues:
https://reviews.imfreedom.org/r/1455/

Comment 2 Ben Cotton 2023-04-25 17:17:37 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 16:57:09 UTC

Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.