Summary: | Blowfish crash [Konversation::Cipher::blowfishECB, QCA::Cipher::*] | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Eike Hein <hein> |
Component: | encryption | Assignee: | Travis McHenry <wordsizzle> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | ced.descamps, konversation-devel |
Priority: | NOR | ||
Version: | Git | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Crash backtrace by t-nor
Another crash backtrace by t-nor, this time on key exchange |
More info: [20:26] <Sho_> t-nor: any more info on what exactly you were doing when it crashed? [20:51] <t-nor> Sho_: it seems that konversation crash after i set the key and when a new sentence is display Created attachment 37521 [details]
Another crash backtrace by t-nor, this time on key exchange
This appears to have been a bug in the user's old QCA 2.0.0 from Kubuntu. After building QCA 2.0.2 - the same as on our dev systems where we couldn't reproduce the crashes - it's working fine for him. *** Bug 210792 has been marked as a duplicate of this bug. *** |
Created attachment 37519 [details] Crash backtrace by t-nor A user in #konversation reported a crash when setting an encryption key. IRC nicks were first cedric_ and later t-nor; the latter is the nickserv account name. Quote: [20:16] <t-nor> set a blowfish key give me a segmentation fault Backtrace attached.