https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #19 from Peng Wu <pwu(a)redhat.com> ---
I think the code has changed since the bug report.
Please attach updated backtrace and update the reproduce steps.
It will be helpful to have another bug for pidgin to fix this issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #18 from Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> ---
Why a new one instead of just adding them to the CC list?
Also keep in mind that it's very hard to reproduce the bug. It happens to me
only a couple of times per year.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #17 from Peng Wu <pwu(a)redhat.com> ---
Could you open new bug for pidgin?
Then we can discuss with pidgin maintainers.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|31 |32
--- Comment #16 from Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> ---
Still happening with pidgin-2.13.0-17.fc32.x86_64 & pango-1.44.7-2.fc32.x86_64.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1406031
Bug 1406031 depends on bug 1410052, which changed state.
Bug 1410052 Summary: glibc: pthread_rwlock_rdlock && POSIX 2008 compliance
https://bugzilla.redhat.com/show_bug.cgi?id=1410052
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |UPSTREAM
--
You are receiving this mail because:
You are on the CC list for the bug.