Summary: | Manage sieve scripts from within kcontact will crash kcontact | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Hartmut Manz <manz> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | manz, sebastian |
Priority: | NOR | ||
Version: | 4.10.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
crash information |
Description
Hartmut Manz
2013-01-22 10:36:29 UTC
Created attachment 76964 [details]
New crash information added by DrKonqi
kontact (4.10) on KDE Platform 4.10.00 using Qt 4.8.2
- What I was doing when the application crashed:
This problem still exists in KDE 4.10 final release
-- Backtrace (Reduced):
#6 KSieveUi::ManageSieveScriptsDialog::killAllJobs (this=0xe4d7b60, disconnectSignal=false) at ../../../libksieve/ksieveui/managesievescriptsdialog.cpp:115
#7 0x00007f3cff5cba82 in KSieveUi::ManageSieveScriptsDialog::clear (this=0xe4d7b60, disconnect=<optimized out>) at ../../../libksieve/ksieveui/managesievescriptsdialog.cpp:321
#8 0x00007f3cff5cbd5c in KSieveUi::ManageSieveScriptsDialog::slotRefresh (this=0xe4d7b60, disconnectSignal=<optimized out>) at ../../../libksieve/ksieveui/managesievescriptsdialog.cpp:177
[...]
#10 0x00007f3cfde4c142 in KManageSieve::SieveJob::result (this=<optimized out>, _t1=0xcbbc6f0, _t2=true, _t3=..., _t4=false) at ./sievejob.moc:129
#11 0x00007f3cfde4dc99 in KManageSieve::SieveJob::Private::handleResponse (this=0x128c5ff0, response=..., data=...) at ../../../libksieve/kmanagesieve/sievejob.cpp:201
This happens also on Gentoo. KDE 4.10 from main portage. But it only happens if i activate sieve support on more than 1 server/mailaccount. If i only manage 1 account it works without problems Created attachment 77727 [details]
crash information
The Bug still exists in KDE 4.10.1 Can anyone provide me with information wich packages i need to build with debugging information to get a meaningful backtrace? This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |