Summary: | Kgpg crash when canceling the opening of a encrypted file | ||
---|---|---|---|
Product: | [Applications] kgpg | Reporter: | François L. <bigrou> |
Component: | general | Assignee: | Rolf Eike Beer <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
François L.
2009-09-22 11:26:52 UTC
SVN commit 1027307 by dakon: make sure that pointer is never stale CCBUG:208162 M +2 -0 kgpglibrary.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1027307 > -- Backtrace:
> Application: KGpg (kgpg), signal: Segmentation fault
> [KCrash Handler]
> #6 0x080dcaf7 in KgpgLibrary::processDecOver (this=0x8c6e3b8, ret=2,
> iface=0x8d3f690) at
> /home/jan/kdemod/core/kdeutils/src/kdeutils-4.3.1/kgpg/kgpglibrary.cpp:173
This could be a double free, although I have no idea how you might get there.
Anyway, I'll just zero that this everywhere where it's surely no longer valid.
Could you test?
It seems the crash occurs only at the first file I try to open after login in kde, when I cancel the opening even without an attempt to enter the valid passphrase. I tried with and without kgpg launching automatically at the start of the session. If I try to open a second encrypted file after the crash, everything is working fine. By testing you mean patching with the changes of the revision 1027307 and compiling kgpg? I can give it a try but I never compiled a kde app yet. Yes, that patch. A rough example on how to do it is here: http://der-dakon.net/blog/KDE/building-kdeutils.html The path you need to check out is svn://anonsvn.kde.org/home/kde/branches/KDE/4.3/kdeutils/ Okay, tested and it seems to resolve the problem. Thanks ! However I don't know if it's a side effect of the fix but now when cancelling the opening of a file, the error window (labeled something like "Failed to open the encrypted file" followed by the filename(s)) pop up twice now. Should I open another bug report about that ? Let me have a look at this first. > However I don't know if it's a side effect of the fix but now when
> cancelling the opening of a file, the error window (labeled something like
> "Failed to open the encrypted file" followed by the filename(s)) pop up
> twice now. Should I open another bug report about that ?
It's basically the same problem: for whatever reason the function that shows
this message and that deletes the object gets called twice. So for now I only
cured one symptom but still have no clue about the real disease.
Lowering priority as it doesn't crash anymore. This stuff has been reworked. Does this still happen? I won't be able to test for some time but as soon as I can I will update the report. Please report back if there is any news on this. Seems fixed. |