Description of problem: 
I've been seeing a lot of Pidgin crashes on Fedora 31 using Pidgin 2.13.0-15.fc31.x86_64. I'm guessing it might have to do with Discord, but it might be XMPP or Skype.
Abrt shows: Reporting is disabled because the generated backtrace has low information value.
I assume others have reports like: https://retrace.fedoraproject.org/faf/reports/2875464/ but a Fedora bug isn't being opened.

I have interacted with Gary Kramlich / @grim from Pidgin:
https://www.facebook.com/pidgin.im/posts/10162953057695411?comment_id=10163026697765411&reply_comment_id=10163027763525411&notif_id=1586205132681337&notif_t=feed_comment_reply&ref=notif
> Gary Kramlich
developer.pidgin.im is limping along, it's getting hammered by abusive bots at the moment.
As mentioned on discord this seems to be related to https://github.com/EionRobb/purple-discord/issues/288 and will require building the plugin yourself or getting the fedora packager to update it. https://src.fedoraproject.org/rpms/purple-discord looks like they haven't updated it in awhile, so you might want to send them a message/bug report.


Version-Release number of selected component (if applicable):
pidgin-discord-0-25.20190805git250a8a0.fc31.noarch
purple-discord-0-25.20190805git250a8a0.fc31.x86_64

How reproducible:
Multiple times per day for the last few days.


Steps to Reproduce:
1. Enable an account using pidgin-discord
2. Receive a message via Discord
3. Pidgin exceptions, but Abrt won't open a bug (see above). Remote core analysis totally fails, the local analysis provided the above error. I assume this is slowing others from creating this report.
4. I'm not sure 'which' specific inbound Discord message causes the crash as Pidgin doesn't stay up long when a message comes in.

Actual results:
Pidgin core dumps.


Expected results:


Additional info: