Bug 181649 - crash when exiting organizer connected with eGroupWare
Summary: crash when exiting organizer connected with eGroupWare
Status: RESOLVED DUPLICATE of bug 171797
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-23 10:32 UTC by Gerhard Gappmeier
Modified: 2009-01-26 13:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Gappmeier 2009-01-23 10:32:51 UTC
Version:            (using Devel)
Compiler:          gcc-Version 4.1.2 (Gentoo 4.1.2 p1.1) 
OS:                Linux
Installed from:    Compiled sources

I added an eGroupWare Resource to KOrganizer and syncing works more ore less (that's another story).
But when exiting KOrganizer the app crashes.
So I guess this has to do with the eGroupWare synchronzation.
With this resource it does not crash.

Here is the crash report with the callstack:

Application: KOrganizer (korganizer), signal SIGABRT

Thread 1 (Thread 0xb52476d0 (LWP 27356)):
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb5fff101 in raise () from /lib/libc.so.6
#8  0xb60008e8 in abort () from /lib/libc.so.6
#9  0xb6c0e7ba in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbf85e230 "Fatal Error: Accessed global static 'KProtocolManagerPrivate *kProtocolManagerPrivate()' after destruction. Defined at /home/kde4/kde/src/KDE/kdelibs/kio/kio/kprotocolmanager.cpp:64") at global/qglobal.cpp:2102
#10 0xb6c0e81f in qFatal (msg=0xb72af1c4 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d") at global/qglobal.cpp:2303
#11 0xb71b6feb in KProtocolManager::slaveProtocol () from /home/kde4/kde/lib/libkio.so.5
#12 0xb71eb83a in KIO::SchedulerPrivate::doJob () from /home/kde4/kde/lib/libkio.so.5
#13 0xb71ec6cf in KIO::Scheduler::doJob () from /home/kde4/kde/lib/libkio.so.5
#14 0xb7147022 in KIO::SimpleJobPrivate::simpleJobInit () from /home/kde4/kde/lib/libkio.so.5
#15 0xb714772f in KIO::SimpleJob::SimpleJob () from /home/kde4/kde/lib/libkio.so.5
#16 0xb7147869 in KIO::TransferJob::TransferJob () from /home/kde4/kde/lib/libkio.so.5
#17 0xb71544b3 in KIO::http_post () from /home/kde4/kde/lib/libkio.so.5
#18 0xb2ef88a4 in KXMLRPC::Query::call () from /home/kde4/kde/lib/libkcal_xmlrpc.so.4
#19 0xb2ef8fdd in KXMLRPC::Server::call () from /home/kde4/kde/lib/libkcal_xmlrpc.so.4
#20 0xb2ef972d in KXMLRPC::Server::call () from /home/kde4/kde/lib/libkcal_xmlrpc.so.4
#21 0xb2f0a6c7 in KCal::ResourceXMLRPC::doClose () from /home/kde4/kde/lib/libkcal_xmlrpc.so.4
#22 0xb735e228 in KRES::Resource::close () from /home/kde4/kde/lib/libkresources.so.4
#23 0xb7aa6025 in KCal::CalendarResources::close () from /home/kde4/kde/lib/libkcal.so.4
#24 0xb7aa63b5 in KCal::CalendarResources::~CalendarResources () from /home/kde4/kde/lib/libkcal.so.4
#25 0x080533f4 in KOrg::StdCalendar::~StdCalendar ()
#26 0x0805473f in K3StaticDeleter<KOrg::StdCalendar>::destructObject ()
#27 0xb7b5ba48 in K3StaticDeleterPrivate::deleteStaticDeleters () from /home/kde4/kde/lib/libkde3support.so.4
#28 0xb6d0a3a3 in qt_call_post_routines () at kernel/qcoreapplication.cpp:159
#29 0xb636d485 in ~QApplication (this=0xbf860850) at kernel/qapplication.cpp:938
#30 0xb7d9dfea in KApplication::~KApplication () from /home/kde4/kde/lib/libkdeui.so.5
#31 0xb7da5908 in KUniqueApplication::~KUniqueApplication () from /home/kde4/kde/lib/libkdeui.so.5
#32 0x08051197 in main ()
Comment 1 Dario Andres 2009-01-23 10:59:12 UTC
What KDE version (or SVN revision/branch) are you using ?

Also, were you closing the session (logout/shutdown) ? Did the logout dialog appeared ? Or the session "crashed" and you got into KDM login manager without confirmation (logout/shutdown) dialog?

Comment 2 Dario Andres 2009-01-23 11:00:42 UTC
Also, this is probably related to bug 171797
Comment 3 Gerhard Gappmeier 2009-01-26 12:42:02 UTC
I'm working with revision 915506.

I'm not doing any shutdown or something nasty like that.
Just closing the app using the "x" (Close) button in the right top  corner. 
Same as Alt-F4.

yes, bug http://bugs.kde.org/show_bug.cgi?id=171797 seems to crash at the same 
location in the callstack.

I can reproduce the problem everytime, so I can retest it when it is fixed.
Comment 4 Dario Andres 2009-01-26 13:45:47 UTC
Thanks :)

*** This bug has been marked as a duplicate of bug 171797 ***