Bug 2006814

Summary: [abrt] pidgin: _gdk_x11_get_window_child_info(): pidgin killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: pidginAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: igor.raits, jskarvad, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/da626cb25ea0f166e34792a122c4c5ae28c9fd58
Whiteboard: abrt_hash:8db799def66a20abb7f7e3d3d2ef100a4647cba3;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:23:56 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: 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

Description Brian J. Murrell 2021-09-22 13:19:38 UTC 
Description of problem:
I don't know what caused it.

Version-Release number of selected component:
pidgin-2.14.1-3.fc34

Additional info:
reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-pidgin-25691.scope
cmdline:        pidgin -d
crash_function: _gdk_x11_get_window_child_info
executable:     /usr/bin/pidgin
journald_cursor: s=062455f8566746cebaf1e6e7b38ae2f4;i=52cc9;b=a9b9f4b78cc141558818d41a1105cadb;m=69e67ac5d;t=5c9cef4ab3cf7;x=7dd57db1b01018e4
kernel:         5.13.9-200.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Potential duplicate: bug 1624439
Comment 1 Brian J. Murrell 2021-09-22 13:19:41 UTC 
Created attachment 1825325 [details]
File: backtrace
Comment 2 Brian J. Murrell 2021-09-22 13:19:42 UTC 
Created attachment 1825326 [details]
File: core_backtrace
Comment 3 Brian J. Murrell 2021-09-22 13:19:43 UTC 
Created attachment 1825327 [details]
File: cpuinfo
Comment 4 Brian J. Murrell 2021-09-22 13:19:45 UTC 
Created attachment 1825328 [details]
File: dso_list
Comment 5 Brian J. Murrell 2021-09-22 13:19:46 UTC 
Created attachment 1825329 [details]
File: environ
Comment 6 Brian J. Murrell 2021-09-22 13:19:47 UTC 
Created attachment 1825330 [details]
File: limits
Comment 7 Brian J. Murrell 2021-09-22 13:19:48 UTC 
Created attachment 1825331 [details]
File: maps
Comment 8 Brian J. Murrell 2021-09-22 13:19:49 UTC 
Created attachment 1825332 [details]
File: mountinfo
Comment 9 Brian J. Murrell 2021-09-22 13:19:50 UTC 
Created attachment 1825333 [details]
File: open_fds
Comment 10 Brian J. Murrell 2021-09-22 13:19:51 UTC 
Created attachment 1825334 [details]
File: proc_pid_status
Comment 11 Ben Cotton 2022-05-12 15:35:03 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 12 Ben Cotton 2022-06-07 22:23:56 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.