Bug 1657884

Summary: [abrt] pidgin: poll_for_event(): pidgin killed by SIGABRT
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: pidginAssignee: Jan Synacek <jsynacek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: igor.raits, itamar, jskarvad, jsynacek, redhat, stu, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e839f49838c03054b072478559ff7c281d8b33cf
Whiteboard: abrt_hash:e94583e9f253372dcc6eaa6fa8230f88eec5afab;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 18:16:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brian J. Murrell 2018-12-10 16:27:32 UTC
Description of problem:
Typing into a message box

Version-Release number of selected component:
pidgin-2.13.0-6.fc29

Additional info:
reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        pidgin --session 102691acb73cb2cd2d154289358663084100000253380101 --display :0
crash_function: poll_for_event
executable:     /usr/bin/pidgin
journald_cursor: s=e341f018dbb24e518fad7d6c9ce50e34;i=61974;b=40827c6c49e944bfa6e962cfe28807d0;m=16a922988ba;t=57caca0c3365a;x=ce3ea4eb98a98b31
kernel:         4.19.2-301.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 1 Brian J. Murrell 2018-12-10 16:27:35 UTC
Created attachment 1513109 [details]
File: backtrace

Comment 2 Brian J. Murrell 2018-12-10 16:27:36 UTC
Created attachment 1513110 [details]
File: cgroup

Comment 3 Brian J. Murrell 2018-12-10 16:27:37 UTC
Created attachment 1513111 [details]
File: core_backtrace

Comment 4 Brian J. Murrell 2018-12-10 16:27:38 UTC
Created attachment 1513112 [details]
File: cpuinfo

Comment 5 Brian J. Murrell 2018-12-10 16:27:39 UTC
Created attachment 1513113 [details]
File: dso_list

Comment 6 Brian J. Murrell 2018-12-10 16:27:40 UTC
Created attachment 1513114 [details]
File: environ

Comment 7 Brian J. Murrell 2018-12-10 16:27:42 UTC
Created attachment 1513115 [details]
File: limits

Comment 8 Brian J. Murrell 2018-12-10 16:27:43 UTC
Created attachment 1513116 [details]
File: maps

Comment 9 Brian J. Murrell 2018-12-10 16:27:45 UTC
Created attachment 1513117 [details]
File: mountinfo

Comment 10 Brian J. Murrell 2018-12-10 16:27:47 UTC
Created attachment 1513118 [details]
File: open_fds

Comment 11 Brian J. Murrell 2018-12-10 16:27:48 UTC
Created attachment 1513119 [details]
File: proc_pid_status

Comment 12 Brian J. Murrell 2018-12-10 16:27:49 UTC
Created attachment 1513120 [details]
File: var_log_messages

Comment 13 Ben Cotton 2019-10-31 18:58:20 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 14 Christian Kujau 2019-11-01 05:04:25 UTC
The last time this happend on August 8, but not ever since, so I guess this can be closed. A somewhat incomplete backtrace (from syslog) follows:

Aug  8 22:15:47 horus pidgin.desktop[4680]: [xcb] Unknown sequence number while processing queue
Aug  8 22:15:47 horus pidgin.desktop[4680]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
Aug  8 22:15:47 horus pidgin.desktop[4680]: [xcb] Aborting, sorry about that.
Aug  8 22:15:47 horus pidgin.desktop[4680]: pidgin: xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aug  8 22:15:47 horus systemd[1]: Started Process Core Dump (PID 13689/UID 0).
Aug  8 22:15:47 horus systemd-coredump[13690]: Process 12293 (pidgin) of user 1000 dumped core.
#012#012Stack trace of thread 12293:
#012#0  0x00007fc71dce8e75 __GI_raise (libc.so.6)
#012#1  0x00007fc71dcd3895 __GI_abort (libc.so.6)
#012#2  0x00007fc71dcd3769 __assert_fail_base (libc.so.6)
#012#3  0x00007fc71dce1566 __GI___assert_fail (libc.so.6)
#012#4  0x00007fc71ebf68db poll_for_event (libX11.so.6)
#012#5  0x00007fc71ebf6980 poll_for_response (libX11.so.6)
#012#6  0x00007fc71ebf6c85 _XEventsQueued (libX11.so.6)
#012#7  0x00007fc71ebe8727 XPending (libX11.so.6)
#012#8  0x00007fc71e671648 n/a (libgdk-x11-2.0.so.0)
#012#9  0x00007fc71e02fc31 g_main_context_check (libglib-2.0.so.0)
#012#10 0x00007fc71e030182 g_main_context_iterate (libglib-2.0.so.0)
#012#11 0x00007fc71e0305a3 g_main_loop_run (libglib-2.0.so.0)
#012#12 0x00007fc71e82b042 gtk_main (libgtk-x11-2.0.so.0)
#012#13 0x000056307b881b50 main (pidgin)
#012#14 0x00007fc71dcd4f33 __libc_start_main (libc.so.6)
#012#15 0x000056307b88226e _start (pidgin)
#012#012Stack trace of thread 12301:
#012#0  0x00007fc71dda15c7 __GI___poll (libc.so.6)
#012#1  0x00007fc71e0301de g_main_context_poll (libglib-2.0.so.0)
#012#2  0x00007fc71e0305a3 g_main_loop_run (libglib-2.0.so.0)
#012#3  0x00007fc71db90d8a gdbus_shared_thread_func (libgio-2.0.so.0)
#012#4  0x00007fc71e0594e2 g_thread_proxy (libglib-2.0.so.0)
#012#5  0x00007fc71de815a2 start_thread (libpthread.so.0)
#012#6  0x00007fc71ddac303 __clone (libc.so.6)
#012#012Stack trace of thread 12300:
#012#0  0x00007fc71dda15c7 __GI___poll (libc.so.6)
#012#1  0x00007fc71e0301de g_main_context_poll (libglib-2.0.so.0)
#012#2  0x00007fc71e030313 g_main_context_iteration (libglib-2.0.so.0)
#012#3  0x00007fc71e030361 glib_worker_main (libglib-2.0.so.0)
#012#4  0x00007fc71e0594e2 g_thread_proxy (libglib-2.0.so.0)
#012#5  0x00007fc71de815a2 start_thread (libpthread.so.0)
#012#6  0x00007fc71ddac303 __clone (libc.so.6)

Comment 15 Ben Cotton 2019-11-27 18:16:36 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. If you experience problems, please add a comment to this
bug.

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