Bug 1913497

Summary: [abrt] pidgin: sighandler.lto_priv.0(): pidgin killed by SIGABRT
Product: [Fedora] Fedora Reporter: Wilde Geist <cyberabattoir>
Component: pidginAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: igor.raits, itamar, jskarvad, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6ed1cc27bbfdf0ad90a18e282c11346c4543125d
Whiteboard: abrt_hash:849da27e6b6211cb1391649e5c2e92116ad82489;VARIANT_ID=cinnamon;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:23:21 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
File: cover.jpg none

Description Wilde Geist 2021-01-06 23:35:30 UTC
Description of problem:
I tried to Open Pidgin after installing a couple Plug Ins for Matrix and Discord I think it was and never opened. Crashes instantly upon Launch. Kind of like the House and Senate and Federal Government trying to do ANYTHING. Sorry no disrespect to Pidgin.

Version-Release number of selected component:
pidgin-2.14.1-2.fc33

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        pidgin
crash_function: sighandler.lto_priv.0
executable:     /usr/bin/pidgin
journald_cursor: s=32f4a06c11264514b15284d3c7c7eaff;i=9151;b=1523abc2de4c4d799efbd520759eb98a;m=9fef10782;t=5b8428898e6be;x=842262fc041481d1
kernel:         5.10.0-0.rc6.20201204git34816d20f173.92.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Comment 1 Wilde Geist 2021-01-06 23:35:32 UTC
Created attachment 1745085 [details]
File: backtrace

Comment 2 Wilde Geist 2021-01-06 23:35:33 UTC
Created attachment 1745086 [details]
File: core_backtrace

Comment 3 Wilde Geist 2021-01-06 23:35:34 UTC
Created attachment 1745087 [details]
File: cpuinfo

Comment 4 Wilde Geist 2021-01-06 23:35:36 UTC
Created attachment 1745088 [details]
File: dso_list

Comment 5 Wilde Geist 2021-01-06 23:35:37 UTC
Created attachment 1745089 [details]
File: environ

Comment 6 Wilde Geist 2021-01-06 23:35:37 UTC
Created attachment 1745090 [details]
File: limits

Comment 7 Wilde Geist 2021-01-06 23:35:39 UTC
Created attachment 1745091 [details]
File: maps

Comment 8 Wilde Geist 2021-01-06 23:35:39 UTC
Created attachment 1745092 [details]
File: mountinfo

Comment 9 Wilde Geist 2021-01-06 23:35:40 UTC
Created attachment 1745093 [details]
File: open_fds

Comment 10 Wilde Geist 2021-01-06 23:35:41 UTC
Created attachment 1745094 [details]
File: proc_pid_status

Comment 11 Wilde Geist 2021-01-06 23:35:43 UTC
Created attachment 1745095 [details]
File: cover.jpg

Comment 12 Wilde Geist 2021-01-08 02:15:04 UTC
Similar problem has been detected:

Wow! Took most the whole day on this junk Dell to run this. This is likely redundant but is a different machine almost set up like my other doing similar with not only Pidgin not opening up but Chromium Web Browser too no matter what plugins Chromium did open but the innards were blank. What I mean is there was nothing much but the frame and nothing inside to see or type into. I installed some alpha flash thing and still nothing and tried the Gnome Pidgin thing. Does not work when I flip over to XFCE & Flubox either. Nheko IM for Matrix also is like Chromium in that it opens but can not see anything much inside the frame to type into or look at. Sorry to keep blasting these Bugzilla for the same thing but hopefully generate enough data to cross reference for a solution.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        pidgin
crash_function: sighandler.lto_priv.0
executable:     /usr/bin/pidgin
journald_cursor: s=c74d7a799d184b9a8626cf53a6286aa6;i=1d15a;b=498916b9aabe4d3fb388b809f8981735;m=ef3f39d;t=5b85533eb1f71;x=f5cd4a18a266f842
kernel:         5.10.0-0.rc6.20201204git34816d20f173.92.fc34.x86_64
package:        pidgin-2.14.1-2.fc33
reason:         pidgin killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Comment 13 Ben Cotton 2021-02-09 15:37:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 14 Ben Cotton 2022-05-12 15:34:38 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 15 Ben Cotton 2022-06-07 22:23:21 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.