Bug 1805152

Summary: Build with gtk3
Product: [Fedora] Fedora Reporter: Jan Kratochvil <jan.kratochvil>
Component: pidginAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 34CC: igor.raits, itamar, jan, jan.kratochvil, jskarvad, kdreyer, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:23:14 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 Jan Kratochvil 2020-02-20 11:33:51 UTC
Description of problem:
I am facing a bug which has been fixed in gtk trunk (=gtk3) 10 years ago:
  https://gitlab.gnome.org/GNOME/gtk/commit/c03a3ca6012d8797507f83ce317b74144e5bc464
Pidgin compatibility with gtk3 is claimed to be fixed 8 years ago:
  https://developer.pidgin.im/ticket/8932
Why does Fedora Pidgin still build with gtk2?
I haven't tried to port it to gtk3 myself.

Version-Release number of selected component (if applicable):
pidgin-2.13.0-15.fc31.x86_64

How reproducible:
Once a week.

Steps to Reproduce:
1. Try to copy-paste some link to chat.

Actual results:
Lockup inside gtk_scrolled_window_size_allocate.

Expected results:
No lockup.

Additional info:
OK we could backport the bugfix to gtk2 but still why gtk2 for Pidgin?

Comment 1 Jan Kratochvil 2020-02-24 04:37:51 UTC
Freeze (infinite loop) when pasting long link
https://developer.pidgin.im/ticket/16841

Comment 2 Jan Kratochvil 2020-04-13 07:39:59 UTC
gtk2 fix has been denied:
  Backport a lockup fix from upstream
  https://src.fedoraproject.org/rpms/gtk2/pull-request/4#comment-41244
  Fix freeze (infinite loop) when pasting long link in Pidgin
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1556#note_763456

Is there some prior attempt/experience to build Pidgin with gtk3? Surprisingly Debian also builds it with gtk2 while upstream claims it should build with gtk3.

Comment 3 Jaroslav Škarvada 2020-04-14 20:28:23 UTC
Are you sure that pidgin-2.13.0 (i.e. the latest stable release) can be built with GTK-3? Could you point me to the instructions how to build it?

Comment 4 Jan Kratochvil 2020-04-14 20:46:35 UTC
The only thing I know is my Comment 0 link:
Pidgin compatibility with gtk3 is claimed to be fixed 8 years ago:
  https://developer.pidgin.im/ticket/8932
Whether it is still only in trunk after 8 years, dunno.
OK, I may try to build it.

Comment 5 Jaroslav Škarvada 2020-04-14 20:58:24 UTC
(In reply to Jan Kratochvil from comment #4)
> The only thing I know is my Comment 0 link:
> Pidgin compatibility with gtk3 is claimed to be fixed 8 years ago:
>   https://developer.pidgin.im/ticket/8932
> Whether it is still only in trunk after 8 years, dunno.
> OK, I may try to build it.

I am afraid it's not in the 2.x branch. It seems the configure.ac has some fragments to support gtk-3, but it is probably not enough - for me it's failing if gtk-2 is not detected. I didn't try to patch it.

Comment 6 Jaroslav Škarvada 2020-04-22 16:19:05 UTC
It seems the full gtk3 support is available in the pidgin 3, but the release date is currently unknown.

Comment 7 Ben Cotton 2020-11-03 16:56:57 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Jaroslav Škarvada 2020-11-04 10:35:15 UTC
Moving to rawhide.

Comment 9 Ben Cotton 2021-02-09 16:11:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 10 Ben Cotton 2022-05-12 15:34:29 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 11 Ben Cotton 2022-06-07 22:23:14 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

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