[kontact] [Bug 332672] New: Kontact crashed when enabling/disabling modules
https://bugs.kde.org/show_bug.cgi?id=332672 Bug ID: 332672 Summary: Kontact crashed when enabling/disabling modules Classification: Unclassified Product: kontact Version: 4.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Application: kontact (4.12.3) KDE Platform Version: 4.12.3 Qt Version: 4.8.6 Operating System: Linux 3.11.0-18-generic i686 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I opened the Kontact's configuration dialog, enabled KNotes, disabled KNode and finally disabled Knotes - and Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb16ad740 (LWP 2516))] Thread 5 (Thread 0xaee39b40 (LWP 2560)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xb5825d90 WTF::pageheap_memory+20720, mutex=0xb5825d78 WTF::pageheap_memory+20696) at forward.c:149 #3 0xb4faba7c in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4fabacf in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb31cad78 in start_thread (arg=0xaee39b40) at pthread_create.c:311 #6 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 4 (Thread 0xae518b40 (LWP 2586)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xae5867dc, mutex=0xae5867c4) at forward.c:149 #3 0xb4fdaae3 in WTF::ThreadCondition::wait(WTF::Mutex) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4cb6744 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb4fc1866 in WTF::threadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb4fda459 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb31cad78 in start_thread (arg=0xae518b40) at pthread_create.c:311 #8 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 3 (Thread 0xa9a7cb40 (LWP 4487)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb6087a0b in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb30fba4b in poll (__timeout=__timeout@entry=3968, __nfds=__nfds@entry=1, __fds=__fds@entry=0xa9102160) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 g_poll (fds=fds@entry=0xa9102160, nfds=nfds@entry=1, timeout=timeout@entry=3968) at /build/buildd/glib2.0-2.38.1/./glib/gpoll.c:132 #4 0xb30ecb68 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0xa9102160, timeout=3968, context=0xa91004e0) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:4006 #5 g_main_context_iterate (context=context@entry=0xa91004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3707 #6 0xb30ecca8 in g_main_context_iteration (context=0xa91004e0, may_block=1) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3773 #7 0xb63eb9ef in QEventDispatcherGlib::processEvents (this=0xa9100468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #8 0xb63ba813 in QEventLoop::processEvents (this=this@entry=0xa9a7c258, flags=...) at kernel/qeventloop.cpp:149 #9 0xb63bab39 in QEventLoop::exec (this=this@entry=0xa9a7c258, flags=...) at kernel/qeventloop.cpp:204 #10 0xb62a721d in QThread::exec (this=this@entry=0xa264bc0) at thread/qthread.cpp:537 #11 0xb62a736b in QThread::run (this=0xa264bc0) at thread/qthread.cpp:604 #12 0xb62a9b4f in QThreadPrivate::start (arg=0xa264bc0) at thread/qthread_unix.cpp:349 #13 0xb31cad78 in start_thread (arg=0xa9a7cb40) at pthread_create.c:311 #14 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xabbdbb40 (LWP 4771)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xac16f8d0, mutex=0xac16f8b8) at forward.c:149 #3 0xac06cc72 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #4 0xac06ccbf in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #5 0xb31cad78 in start_thread (arg=0xabbdbb40) at pthread_create.c:311 #6 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb16ad740 (LWP 2516)): [KCrash Handler] #7 ref (this=0x320fc0) at
[kleopatra] [Bug 331062] Kleopatra doesn't report accessibility information through the QT accessibility infra structure
https://bugs.kde.org/show_bug.cgi?id=331062 Emanuel Schütze eman...@intevation.de changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||eman...@intevation.de Ever confirmed|0 |1 --- Comment #1 from Emanuel Schütze eman...@intevation.de --- Thanks for your important bug report! That's helps to understand what developers can do to improve Kleopatra for visually impaired people. Is there anybody who has time to do it? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 332673] New: Notes don't appear in summary view unless I go into Pop-up notes
https://bugs.kde.org/show_bug.cgi?id=332673 Bug ID: 332673 Summary: Notes don't appear in summary view unless I go into Pop-up notes Classification: Unclassified Product: kontact Version: 4.13 pre Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: mfraz74+...@gmail.com If I start Kontact in summary view, there are no notes showing. If I go into the pop-up notes plug-in and then go back to the summary view, the notes are now visible. Reproducible: Always Steps to Reproduce: 1. Open Kontact in summary view 2. See that no notes are visible 3. Go into popup notes and then back to summary view 4. See that the notes are now there -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319171] Infinite popup message when imap connection error
https://bugs.kde.org/show_bug.cgi?id=319171 --- Comment #12 from t...@ewetel.net --- Thank you Christian, but is there a way to implement this solution right now? Because this bug really drives me crazy at the moment. Or do I have to wait for the 4.13 release on April 16th? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319171] Infinite popup message when imap connection error
https://bugs.kde.org/show_bug.cgi?id=319171 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #13 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #12) Thank you Christian, but is there a way to implement this solution right now? Because this bug really drives me crazy at the moment. Or do I have to wait for the 4.13 release on April 16th? Unfortunately you'll have to wait. But there might be release candidate packages for your distributions, which would also allow you to give me feedback in case you're not yet happy with the solution. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332684] New: [Maildir] lots of stats calls to /etc/localtime on synchronizing folders
https://bugs.kde.org/show_bug.cgi?id=332684
Bug ID: 332684
Summary: [Maildir] lots of stats calls to /etc/localtime on
synchronizing folders
Classification: Unclassified
Product: Akonadi
Version: 4.12
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Maildir Resource
Assignee: kdepim-bugs@kde.org
Reporter: mar...@lichtvoll.de
I think I found a cause for slowness of KMail after downloading and filtern
mails when it synchronizes folders: For Maildir file it stats it does two stat
calls to /etc/localtime.
Reproducible: Always
Steps to Reproduce:
1. Have a large POP 3 account with some mailing list folders of several 1
mails
2. Wait a while for lots of new mails to arrive
3. Download mails
4. Filter mails
Actual Results:
merkaba:~ ps aux | grep 10350 | grep -v grep
martin 10350 18.2 4.1 633212 329004 ? Rl 13:08 15:52
/usr/bin/akonadi_agent_launcher akonadi_maildir_resource
akonadi_maildir_resource_0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623610.R679.merkaba,
{st_mode=S_IFREG|0644, st_size=9688, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623610.R724.merkaba,
{st_mode=S_IFREG|0644, st_size=3832, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623610.R818.merkaba,
{st_mode=S_IFREG|0644, st_size=2909, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623610.R90.merkaba,
{st_mode=S_IFREG|0644, st_size=2754, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623611.R182.merkaba,
{st_mode=S_IFREG|0644, st_size=2984, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623611.R187.merkaba:2,S,
{st_mode=S_IFREG|0644, st_size=4869, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350
stat(/home/martin/.local/share/local-mail/.Lichtvoll.directory/.Linux.directory/kernel-ml/new/1368623611.R297.merkaba,
{st_mode=S_IFREG|0644, st_size=3520, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
10350 stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
merkaba:~ grep -c stat( strace-bla.txt
108244
merkaba:~ grep -c stat(\/etc/localtime strace-bla.txt
72058
From a different period during maildir resource being busy with itself (not
possible to attach strace twice to the maildir resource):
merkaba:~ strace -c -f -p 10350
Process 10350 attached with 2 threads - interrupt to quit
10350^CProcess 10350 detached
Process 10391 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
45.330.220536 457 483 getdents
39.640.192880 6 31360 stat
3.990.019400 6 2994 2883 recvmsg
3.080.014972 11 139451 read
2.380.011592 8 1392 poll
1.560.007571 11 663 write
1.120.005430 21 256 brk
1.100.005375 5 1123 ioctl
0.590.002865 17 164 sendmsg
0.490.002398 8 304 access
0.300.001443 722 2 rename
0.140.000682 85 8 open
0.080.000401 4010 statfs
0.060.000280 140 2 2 lstat
0.050.000257 1418 close
0.040.000192 1910 openat
0.020.000107 7
[Akonadi] [Bug 332684] [Maildir] lots of stats calls to /etc/localtime on synchronizing folders
https://bugs.kde.org/show_bug.cgi?id=332684 --- Comment #1 from Martin Steigerwald mar...@lichtvoll.de --- akonadi maildir resource is CPU bound on one core (100%) for minutes during that case. KMail is blocked. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 303946] Kontact started twice and chrashed when closen one instance
https://bugs.kde.org/show_bug.cgi?id=303946 Raúl rasas...@gmail.com changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #4 from Raúl rasas...@gmail.com --- Bug still alive in kontact 4.11.5 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 332491] Clicking deleting the message does not go automatically to the trash
https://bugs.kde.org/show_bug.cgi?id=332491 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- ? What is your account type ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 332710] New: Kmail opens two tabs in rekonq for the same URL contained in a message
https://bugs.kde.org/show_bug.cgi?id=332710 Bug ID: 332710 Summary: Kmail opens two tabs in rekonq for the same URL contained in a message Classification: Unclassified Product: kmail2 Version: 4.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: valterm...@gmail.com When clicking on an URL in a message kmail opens exactly two tabs with the same page. Reproducible: Always Steps to Reproduce: 1. Read a message containing an URL 2. Click on the URL 3. Actual Results: rekonq starts and opens two tabs for the same link Expected Results: Only one tab opened expected I've opened also a bug for rekonq, but I'm not sure where the issue starts from. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 332673] Notes don't appear in summary view unless I go into Pop-up notes
https://bugs.kde.org/show_bug.cgi?id=332673 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- I confirm it. I didn't find yet the bug. I continue to investigate -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332724] New: IMAP-Resource crashes on retrieval after starting Kontact
https://bugs.kde.org/show_bug.cgi?id=332724 Bug ID: 332724 Summary: IMAP-Resource crashes on retrieval after starting Kontact Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: newslet...@huskytaube.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.11) KDE Platform Version: 4.11.5 Qt Version: 4.8.4 Operating System: Linux 3.11.0-18-generic i686 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: Started Kontact and got a notification that IMAP resource crashed. No retrieval of e-mails happens and a restart of the resource of of Kontact does produce the same effect. -- Backtrace: Application: Oliver vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb4a0e740 (LWP 2417))] Thread 2 (Thread 0xb1feab40 (LWP 2420)): #0 0xb771c424 in __kernel_vsyscall () #1 0xb57794d2 in clock_gettime (clock_id=1, tp=0xb1fe9ff8) at ../sysdeps/unix/clock_gettime.c:115 #2 0xb72083ec in do_gettime (frac=0xb1fe9ff0, sec=0xb1fe9fe8) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0xb72edfd2 in updateCurrentTime (this=0xb1602074) at kernel/qeventdispatcher_unix.cpp:354 #5 QTimerInfoList::timerWait (this=0xb1602074, tm=...) at kernel/qeventdispatcher_unix.cpp:461 #6 0xb72ec67b in timerSourcePrepareHelper (src=optimized out, timeout=0xb1fea0ec) at kernel/qeventdispatcher_glib.cpp:136 #7 0xb72ec70d in timerSourcePrepare (source=0xb1602040, timeout=0xb1fea0ec) at kernel/qeventdispatcher_glib.cpp:169 #8 0xb5484143 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb5484a5f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb5484ca8 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #11 0xb72ec8df in QEventDispatcherGlib::processEvents (this=0xb1600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0xb72bb9f3 in QEventLoop::processEvents (this=this@entry=0xb1fea258, flags=...) at kernel/qeventloop.cpp:149 #13 0xb72bbd19 in QEventLoop::exec (this=this@entry=0xb1fea258, flags=...) at kernel/qeventloop.cpp:204 #14 0xb71aae3d in QThread::exec (this=this@entry=0x9235158) at thread/qthread.cpp:542 #15 0xb71aaf8b in QThread::run (this=0x9235158) at thread/qthread.cpp:609 #16 0xb71ad72f in QThreadPrivate::start (arg=0x9235158) at thread/qthread_unix.cpp:338 #17 0xb55b3d78 in start_thread (arg=0xb1feab40) at pthread_create.c:311 #18 0xb576601e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb4a0e740 (LWP 2417)): [KCrash Handler] #7 0x080891ee in MoveItemsTask::recordNewUid (this=this@entry=0x92af320) at ../../../resources/imap/moveitemstask.cpp:289 #8 0x08089810 in MoveItemsTask::onSearchDone (this=0x92af320, job=0x91cb450) at ../../../resources/imap/moveitemstask.cpp:241 #9 0xb72d1fc7 in QMetaObject::activate (sender=sender@entry=0x91cb450, m=m@entry=0xb5bda4cc KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbff0f338) at kernel/qobject.cpp:3539 #10 0xb5a350f5 in KJob::result (this=this@entry=0x91cb450, _t1=_t1@entry=0x91cb450) at ./kjob.moc:208 #11 0xb5a35142 in KJob::emitResult (this=0x91cb450) at ../../kdecore/jobs/kjob.cpp:318 #12 0xb64f8e4e in KIMAP::Job::handleErrorReplies (this=this@entry=0x91cb450, response=...) at ../../kimap/job.cpp:84 #13 0xb651e489 in KIMAP::SearchJob::handleResponse (this=0x91cb450, response=...) at ../../kimap/searchjob.cpp:161 #14 0xb6511d46 in KIMAP::SessionPrivate::responseReceived (this=0x9234f70, response=...) at ../../kimap/session.cpp:285 #15 0xb65147bb in KIMAP::SessionPrivate::qt_static_metacall (_o=0x12b, _id=0, _a=0xb16fe2a8, _c=optimized out) at ./moc_session_p.cpp:77 #16 0xb72ce77a in QMetaCallEvent::placeMetaCall (this=0xb1602908, object=0x9234f70) at kernel/qobject.cpp:524 #17 0xb72d658b in QObject::event (this=0x9234f70, e=0xb1602908) at kernel/qobject.cpp:1194 #18 0xb67ce744 in QApplicationPrivate::notify_helper (this=0x90c5158, receiver=0x9234f70, e=0xb1602908) at kernel/qapplication.cpp:4567 #19 0xb67d5223 in QApplication::notify (this=0xbff0fb84, receiver=receiver@entry=0x9234f70, e=e@entry=0xb1602908) at kernel/qapplication.cpp:4353 #20 0xb5db6ff4 in KApplication::notify (this=0xbff0fb84, receiver=0x9234f70, event=0xb1602908) at ../../kdeui/kernel/kapplication.cpp:311 #21 0xb72bceda in QCoreApplication::notifyInternal (this=0xbff0fb84, receiver=receiver@entry=0x9234f70, event=event@entry=0xb1602908) at kernel/qcoreapplication.cpp:946 #22
