Summary: | korganizer crashed during shutdown (egroupware, KXMLRPC, K_GLOBAL_STATIC related) | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | George Kiagiadakis <mail> |
Component: | groupware | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | crissi99, faure, gerhard.gappmeier, mh0122, nk, osvaldo.merlo, phobos0, RalfBecker, smartins, sylvain.pare, tuxylord |
Priority: | NOR | ||
Version: | SVN trunk (KDE 4) | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
George Kiagiadakis
2008-09-28 16:03:17 UTC
Forgot to mention, this is svn trunk r865463. Intelligent destructors are not good design, this is another proof of it. Somehow the application should properly close the resources (which is where kio call would be made) before exiting (and that means, before KApplication itself is destroyed -- it's far too late then). But I can see how this doesn't go well with the StdCalendar singleton. Hmm, maybe delete StdCalendar in main, just before the app instance goes out of scope? *** Bug 179373 has been marked as a duplicate of this bug. *** *** Bug 181649 has been marked as a duplicate of this bug. *** *** Bug 181958 has been marked as a duplicate of this bug. *** *** Bug 181953 has been marked as a duplicate of this bug. *** dfaure wrote:
> But I can see how this doesn't go well with the StdCalendar singleton. Hmm,
> maybe delete StdCalendar in main, just before the app instance goes out of
> scope?
Like this?
int result = app.exec();
delete KOrg::StdCalendar::self();
return result;
}
Indeed, it fixes the crash.
Something like this (ideally, only if it exists -- it would be useless to create it just in order to destroy it ;-). I don't work on korganizer myself, hopefully a korganizer developer will react to this patch, otherwise sent it to the kdepim list. It isn't exactly egroupware's destructor, it's doClose(), which creates a http KIO job to call the xmlrpc logout method. If we add that "delete StdCalendar" won't the job get interrupted and killed? Couldn't we just stop sending the "logout" at close? Seems to work fine here. Anyone knows if it's optional? Or maybe make this call synchronous? *** Bug 188718 has been marked as a duplicate of this bug. *** *** Bug 204939 has been marked as a duplicate of this bug. *** *** Bug 208490 has been marked as a duplicate of this bug. *** The current recommendation from EGroupware is to use GroupDAV. It's the only actively developed access method to EGroupware supported by KDE! Ralf *** Bug 214330 has been marked as a duplicate of this bug. *** *** Bug 216537 has been marked as a duplicate of this bug. *** Any chance we can get that fixed? GroupDav deoes not seem to work at all, so right now there is no way to use KOrganizer as eGroupWare client. (In reply to comment #16) > Any chance we can get that fixed? > GroupDav deoes not seem to work at all, so right now there is no way to use > KOrganizer as eGroupWare client. ++10000 (In reply to comment #16) > Any chance we can get that fixed? > GroupDav deoes not seem to work at all, so right now there is no way to use > KOrganizer as eGroupWare client. A new groupdav resource ( akonadi based ) was written from scratch and it works fine. |