Summary: | Konversation got suddendly stuck | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Germano Massullo <germano.massullo> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | kossebau |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Germano Massullo
2021-11-23 18:20:47 UTC
By the backtrace, this seems an issue over at Qt side (or rather fontconfig), at least when used from gdb. Konversation just calls QInputDialog::getText() and things get stuck inside that call, so there is little we can do to fix that. This needs to be reported upstream, as Konversation would not be the only one affected by this. I would start with reporting to Qt, perhaps QFontconfigDatabase::setupFontEngine() does something wrong here. KDE developers should take care of reporting this to upstream, since they know more about Qt than the average user |