Bug 214330 - Ocorre quando KOrganizer é finalizado
Summary: Ocorre quando KOrganizer é finalizado
Status: RESOLVED DUPLICATE of bug 171797
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 01:36 UTC by Osvaldo Merlo
Modified: 2009-11-13 10:51 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 Osvaldo Merlo 2009-11-13 01:36:53 UTC
Application that crashed: korganizer
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
It happens every time I close de KOrganizer window or exit the application.

 -- Backtrace:
Application: KOrganizer (korganizer), signal: Aborted
[KCrash Handler]
#6  0xb77ca422 in __kernel_vsyscall ()
#7  0xb5f234d1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0xb5f26932 in *__GI_abort () at abort.c:92
#9  0xb6175f8c in qt_message_output (msgType=QtFatalMsg, 
    buf=0x97655b8 "Fatal Error: Accessed global static 'KProtocolManagerPrivate *kProtocolManagerPrivate()' after destruction. Defined at ../../kio/kio/kprotocolmanager.cpp:64")
    at global/qglobal.cpp:2042
#10 0xb617606e in qFatal (msg=0xb5aeaa0c "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d") at global/qglobal.cpp:2241
#11 0xb59dc084 in operator-> (this=0xb5b20878) at ../../kio/kio/kprotocolmanager.cpp:64
#12 0xb59e0cbe in operator KProtocolManagerPrivate* (url=..., proxy=...) at ../../kio/kio/kprotocolmanager.cpp:64
#13 KProtocolManager::slaveProtocol (url=..., proxy=...) at ../../kio/kio/kprotocolmanager.cpp:340
#14 0xb5a196dd in KIO::SchedulerPrivate::doJob (this=0x94ed660, job=0x94afbf0) at ../../kio/kio/scheduler.cpp:387
#15 0xb5a1a68f in KIO::Scheduler::doJob (job=0x94afbf0) at ../../kio/kio/scheduler.cpp:263
#16 0xb5961f17 in KIO::SimpleJobPrivate::simpleJobInit (this=0x97d5490) at ../../kio/kio/job.cpp:310
#17 0xb5962e99 in TransferJob (this=0x94afbf0, dd=...) at ../../kio/kio/job.cpp:886
#18 0xb5970a07 in KIO::TransferJobPrivate::newJob(KUrl const&, int, QByteArray const&, QByteArray const&, QFlags<KIO::JobFlag>) () from /usr/lib/libkio.so.5
#19 0xb596c716 in KIO::http_post (url=..., postData=..., flags=) at ../../kio/kio/job.cpp:1409
#20 0xb200b4b2 in ?? () from /usr/lib/libkcal_xmlrpc.so.4
#21 0xb200bbc7 in ?? () from /usr/lib/libkcal_xmlrpc.so.4
#22 0xb200c4f4 in ?? () from /usr/lib/libkcal_xmlrpc.so.4
#23 0xb2015780 in KCal::ResourceXMLRPC::doClose() () from /usr/lib/libkcal_xmlrpc.so.4
#24 0xb5882727 in KRES::Resource::close (this=0x96abac0) at ../../kresources/resource.cpp:141
#25 0xb7394465 in KCal::CalendarResources::close (this=0x969ace0) at ../../kcal/calendarresources.cpp:350
#26 0xb73947d4 in ~CalendarResources (this=0x969ace0, __in_chrg=<value optimized out>) at ../../kcal/calendarresources.cpp:247
#27 0xb6f54013 in KOrg::StdCalendar::~StdCalendar() () from /usr/lib/libkorganizer_calendar.so.4
#28 0xb6f55d5f in ?? () from /usr/lib/libkorganizer_calendar.so.4
#29 0xb56c0104 in K3StaticDeleterPrivate::deleteStaticDeleters () at ../../kde3support/kdecore/k3staticdeleter.cpp:56
#30 0xb626fc00 in qt_call_post_routines () at kernel/qcoreapplication.cpp:163
#31 0xb66d4ba8 in ~QApplication (this=0xbfe865c4, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:971
#32 0xb75ee11a in ~KApplication (this=0xbfe865c4, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:904
#33 0xb75f5588 in ~KUniqueApplication (this=0xbfe865c4, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#34 0x0804ec0e in _start ()

This bug may be a duplicate of or related to bug 188718

Reported using DrKonqi
Comment 1 FiNeX 2009-11-13 10:51:14 UTC

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