[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 René Krell changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from René Krell --- (In reply to Justin Zobel from comment #11) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Sorry, I can't tell you any longer, haven't used KDE for a very long time and don't have an instance for testing the fix the next time. The issue has been probably fixed by the commit mentioned above. You may close this if you want. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 René Serral changed: What|Removed |Added CC||rser...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368434] Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #10 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #9) > akonadi-calendar: > commit 12711617070bae66679d107e270c7fb5a676c154 Aha, ok, finally found it: https://github.com/KDE/akonadi-calendar/commit/12711617070bae66679d107e270c7fb5a676c154 Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #7) > Thanks I tested it. > David fixed a bug in 5.5.0 > We can open this eml file and see invitation without problem now. > So I think that in new version it will work. > > I will delete your testcase Great, thank you. Do you have any reference to the fix (some Git commit or another issue)? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Just for the record, as a hint: Thunderbird 45.8.0 does show this kind of messages (TNEF) without any trouble - in header there appears: "This message contains an invitation to an event." with the Decline | Tentative | Accept buttons. Which probably means this seems not to be an authorization or other integration problem. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- It also depends what do you expect as testcase. Is it enough to forward you a mail causing this problem, and how (inline, as attachment). Or should I save this mail (which format *.eml, *.txt)? What is the best way for you? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- I cannot attach these mails publically, because they are confidential. But I might choose one to forward to your mail address if you promise not to make them public, ok? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Special headers of the affected message look like this: --- ... X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: mail.a.company.com X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: multipart/alternative; boundary="_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_" MIME-Version: 1.0 --_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 ... --- -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378228] New: KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 Bug ID: 378228 Summary: KMail hangs when trying to open a MS Outlook calendar (invitation) message Product: kmail2 Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- Linkage info: - KDE Frameworks 5.31.0 - Qt 5.7.1 (built against 5.7.1) If I receive a calendar message (invitation) from MS Outlook via KMail/Akonadi the message window starts showing "retrieving folder contents" and hangs up infinitely. After that, even on changing to other messages in the message list the message window does not recover from that. To recover, I have to restart KMail and Akonadi (akonadictl restart), but if the first message to show after restarting KDE is the same calendar message again, the whole problem reappears of course. -- You are receiving this mail because: You are the assignee for the bug.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are the assignee for the bug.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Summary|Opening new message very|Plasmashell falls into high |slow and freezes KMail for |CPU load after a while, |several second each |desktop and kmail remains ||almost unresponsive ||(initial kmail issue) -- You are receiving this mail because: You are the assignee for the bug.
[plasmashell] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Product|kmail2 |plasmashell Component|message list|general Version|Git (master)|5.8.4 CC||bhus...@gmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 --- Comment #6 from René Krell <renda.kr...@gmail.com> --- This seems to become a plasmashell issue. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Created attachment 102662 --> https://bugs.kde.org/attachment.cgi?id=102662=edit Compressed output of valgrind --tool=callgrind --instr-atstart=no plasmashell for a few minutes after starting callgrind_control -i o Added the compressed output of 'valgrind --tool=callgrind --instr-atstart=no plasmashell' for a few minutes after starting 'callgrind_control -i o'. I started callgrind_control when kmail started to be unresponsive, including the rest of the plasmashell. I'm not able to interpret the output shown in kcachegrind. Can someone look at this, please? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- I'm currently keeping plasmashell running in valgrind according to this comment: https://forum.kde.org/viewtopic.php?f=289=121533=7ab1403c4fedc79c23d4cadac1e09fd3=45#p343228 and waiting for plasmashell to fall into the high CPU load again, which is apparently the reason for the unresponsiveness of KMail. As soon as this will be the case I try to send some kcachegrind dump from it to get this issue to the right direction. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- Sorry, that was to fast. Baloo isn't the cause. I run into this problem again with deactivated File Search, but now I have plasmashell at high load: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3392 rkrell20 0 0,255t 471020 187628 S 115,3 1,456 33:34.98 plasmashell There is no comparable process in this situation with such a high CPU load. Now even restarting KMail doesn't help. Navigating between messages is almost unresponsive in both accounts, IMAP and Local Folders. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- The only process I saw with a high load during reproducing the problem was the baloo_file_extractor. After that I switched off Search -> File Search -> [ ] Enable File Search. Deactivating the Baloo File Extractor might be way how to avoid the issue reported here, I'll watch this several days. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Important addition: This problem doesn't happen right after system start, but some time after using KMail (after several seconds, minutes or even hours). At the moment I can't see it, but when it happens the notebook's fan is running on higher speed, probably due to a high CPU load. As soon as the problem occurs, KMail doesn't recover from it, so the high load remains instant until the next system restart. I nobody can reproduce this, please give me some hints what outputs to generate and provide, and what to do else to help analyzing. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 373368] New: Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 Bug ID: 373368 Summary: Opening new message very slow and freezes KMail for several second each Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- KMail 5.3.3 (QtWebEngine), OpenSUSE Tumbleweed, Linux (x86_64) release 4.8.12-1-default: Kmail is very slow when navigating between messages in the message list. I have two accounts - an IMAP account (Activated Download all messages for offline use) and a Local Folders account. To be sure this is no migration problem from KDE 4 I stopped KMail and Akonadi and removed the following folders and files: ~/.local/share/akonadi ~/.config/akonadi ~/.kde4/share/config/akonadi* After that I restarted Akonadi and resynchronized the account again. Thus, this should be a clean state. When having synchronized all messages after the above cleanup action the problem reoccurs again: I click on several messages in the message list, marking a new message in the message list freezes KMail for several seconds before the new message is shown in the message window. This behavior happened from my point of view since the QtWebEngine has been introduced as message viewer. Because I've read about multi-threading problems of Nouveau, I tried also the native NVidia driver, no change so far. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 369514] KMail crash on starting (nouveau-related)
https://bugs.kde.org/show_bug.cgi?id=369514 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- (In reply to BingMyBong from comment #1) > Maybe this should be logged against qtwebengine and nouveau as well Did report it to nouveau: https://bugs.freedesktop.org/show_bug.cgi?id=98039 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 369514] New: KMail crash on starting (nouveau-related)
https://bugs.kde.org/show_bug.cgi?id=369514 Bug ID: 369514 Summary: KMail crash on starting (nouveau-related) Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.4-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I started KMail. Using OpenSUSE Tumbleweed 20160927 and the Nouveau driver (kernel 4.7.4, xf86-video-nouveau-1.0.13), KMail crashes everytime I try to start it. The KDE Plasma desktop and Chromium run without any flaw. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff6d0b6a940 (LWP 12021))] Thread 42 (Thread 0x7ff52effb700 (LWP 12105)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6b9c95d49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ff6b9c96460 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ff6b9c96630 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ff6b9c9323d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7ff52f7fc700 (LWP 12103)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7ff52fffd700 (LWP 12102)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7ff5f4fca700 (LWP 12101)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7ff5f57cb700 (LWP 12100)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7ff5f5fcc700 (LWP 12099)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7ff5f67cd700 (LWP 12098)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7ff5f6fce700 (LWP 12097)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be710201 in JSC::BlockAllocator::blockFreeingThreadMain() () at heap/BlockAllocator.cpp:139 #2
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 René Fritz <r...@colorcube.de> changed: What|Removed |Added CC||r...@colorcube.de --- Comment #3 from René Fritz <r...@colorcube.de> --- I can confirm this bug using KMail 5.0.2 from Kubuntu Wily. Deleting doesn't really work (as described). And it seems all emails are fetched every time on sync. -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #143 from René Krell <renda.kr...@gmail.com> --- (In reply to Hussam Al-Tayeb from comment #142) > That breaks execution of other filters. I want it to still get filtered to > Inbox/Bugs/KDE It should not break any other filters if you uncheck Advanced -> "If this filter matches stop processing here". I created such a filter with the simple condition "All messages" and give it a try. Thanks for the hint. Should be seriously solved anyway. -- 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 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com --- Comment #7 from René Krell <renda.kr...@gmail.com> --- The problem does still appear in Akonadi + KMail 15.08.1. -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com --- Comment #134 from René Krell <renda.kr...@gmail.com> --- The problem does still appear in Akonadi + KMail 15.08.1. Many duplicate mails from IMAP. Have just automatically created filter by the Anti Spam Wizard (Bogofilter) activated. -- 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 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 --- Comment #9 from René Krell <renda.kr...@gmail.com> --- Sorry, bad link in the comment above - isn't this a duplicate of https://bugs.kde.org/show_bug.cgi?id=283682 -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #137 from René Krell <renda.kr...@gmail.com> --- (In reply to Hussam Al-Tayeb from comment #136) > > is the default empty filter which is there before you add yours. > It doesn't do anything. Since this is likely some sort of race issue with > filters, it's not going to appear when there are no filters (only the > one). > > Maybe junk filtering and virus scans should not be exposed as filters but > instead some internal plugins (with configuration options) that hook in as > filters. To have an empty filter without any setting makes no sense to me. I would put an empty list there. But this is just a view. Worse is that filtering and mail fetcher resources actually have synchronization problems about four years (!) according to the creation time of this report. I can provide logs or any information I'm able to gather from my system for analyzing. I'm not able to solve this. -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #138 from René Krell <renda.kr...@gmail.com> --- Once more for KMail + Akonadi 15.08.1 regarding the hanging Mail Filter Agent progressbar at 0%: The progressbar hanging forever (along with just having as filter) disappeared after: akonadictl stop akonadictl start -- 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 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- Isn't this a duplicate of https://bugs.kde.org/show_bug.cgi?id=294690 ? -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #135 from René Krell <renda.kr...@gmail.com> --- Created attachment 94708 --> https://bugs.kde.org/attachment.cgi?id=94708=edit Filter after removing all filters manually - in this state it works Once more for KMail + Akonadi 15.08.1. After removing all four filter auto-generated by the Anti Spam Wizard for Bogofilter the messages from IMAP are retrieved in a regular manner again, without any duplicates. Before that I saw a race in the progress bars at the bottom right-hand side between the mail filter agent and the IMAP agent, which doen't happen now, but there is a hanging progressbar at 0% for the Mail Filter Agent. Opening the filter dialog again results in an entry I've never made: . In this state the messages are retrieved regularly. -- 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 335457] Kontact/KMail crash when deleting a folder with subfolders imported from Thunderbird to a Local Folders Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=335457 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from René Krell <renda.kr...@gmail.com> --- Problem cannot be reproduced any longer in Kontact 5.0.1 / KDE Applications 15.08.1. -- 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 347814] Akonadi crashes on Owncloud calendar
https://bugs.kde.org/show_bug.cgi?id=347814 René Serral rser...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from René Serral rser...@gmail.com --- In the last GIT I tried is seems that the crash doesn't occur anymore. Thanks -- 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 350909] New: IMAP resource crashes from time to time
https://bugs.kde.org/show_bug.cgi?id=350909 Bug ID: 350909 Summary: IMAP resource crashes from time to time Product: Akonadi Version: GIT (master) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: rser...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Eventually (I found this like 5 or 7 times already) I receive a message stating that the IMAP resource has crashed. In my system I have currently 5 IMAP accounts (2 Google based and 3 using other servers). I observed, don't know if related, that one of the accounts had the server down when this happened. Here I paste the backtrace: Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f14cfa5b940 (LWP 4492))] Thread 8 (Thread 0x7f14cdb7f700 (LWP 4530)): #0 0x7f14dbaf153d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f14d8ac6252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f14d8ac7ddf in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f14cf693aa9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7f14dc68387e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f14d95410a4 in start_thread (arg=0x7f14cdb7f700) at pthread_create.c:309 #6 0x7f14dbafa07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 7 (Thread 0x7f14cc841700 (LWP 4587)): #0 0x7f14dbaed60d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f14d7f91280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14d7f4d96c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14d7f4de60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f14d7f4dfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f14dc8cc35c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f14dc870b62 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14dc67e8b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f14dc68387e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f14d95410a4 in start_thread (arg=0x7f14cc841700) at pthread_create.c:309 #10 0x7f14dbafa07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f14c7fff700 (LWP 4597)): #0 0x7f14dbaf153d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f14d7f4debc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14d7f4dfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14dc8cc35c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f14dc870b62 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f14dc67e8b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f14dc68387e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14d95410a4 in start_thread (arg=0x7f14c7fff700) at pthread_create.c:309 #8 0x7f14dbafa07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f14c6dee700 (LWP 4760)): #0 0x7f14dbaf153d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f14d7f4debc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14d7f4dfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14dc8cc35c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f14dc870b62 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f14dc67e8b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f14dc68387e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f14d95410a4 in start_thread (arg=0x7f14c6dee700) at pthread_create.c:309 #8 0x7f14dbafa07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f14c5c70700 (LWP 4791)): #0 0x7f14dbaf153d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f14d7f4debc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14d7f4dfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14dc8cc35c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
[Akonadi] [Bug 347814] Akonadi crashes on Owncloud calendar
https://bugs.kde.org/show_bug.cgi?id=347814 --- Comment #3 from René Serral rser...@gmail.com --- I have many events on that calendar, is there any easy way to achieve this? Thanks On 06/25/2015 10:59 PM, Grégory Oestreicher wrote: https://bugs.kde.org/show_bug.cgi?id=347814 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||g...@kamago.net Resolution|--- |WAITINGFORINFO --- Comment #1 from Grégory Oestreicher g...@kamago.net --- Hey, It looks like (at least) one event in your calendar triggers an exception because its type is not correctly detected by the resource. Could you try to isolate it and attach it to this bug report? Cheers, Grégory -- 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 348304] Starting Kontact or kmail results in a crash
https://bugs.kde.org/show_bug.cgi?id=348304 --- Comment #2 from René Serral rser...@gmail.com --- Konsole output Hi, now whenever I try to start kmail directly I get: kmail: symbol lookup error: kmail: undefined symbol: _ZN16KontactInterface20PimUniqueApplication5startEv I tried a clean build using kdesrc-build kdepim If I run kontact I get in stdout: Konsole output QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kf5.kiconthemes: Theme tree: (Breeze) Using blocking call! Using blocking call! Using blocking call! kf5.kservice.sycoca: Trying to open ksycoca from /home/rserral/.cache5/ksycoca5 Loading Plugin: To-do List log_kontactinterface: plugin-objectName()= korganizer running standalone: false log_kontactinterface: plugin-objectName(): korganizer LIBNAMEPART: korganizerpart Loading Plugin: Special Dates LIBNAMEPART: Loading Plugin: Contacts log_kontactinterface: plugin-objectName()= kaddressbook running standalone: false log_kontactinterface: plugin-objectName(): kaddressbook LIBNAMEPART: kaddressbookpart Loading Plugin: Journal log_kontactinterface: plugin-objectName()= korganizer running standalone: false log_kontactinterface: plugin-objectName(): korganizer LIBNAMEPART: korganizerpart Loading Plugin: Mail log_kontactinterface: plugin-objectName()= kmail2 running standalone: false log_kontactinterface: plugin-objectName(): kmail2 LIBNAMEPART: kmailpart Loading Plugin: Calendar log_kontactinterface: plugin-objectName()= korganizer running standalone: false log_kontactinterface: plugin-objectName(): korganizer LIBNAMEPART: korganizerpart Loading Plugin: Feeds log_kontactinterface: plugin-objectName()= akregator running standalone: false log_kontactinterface: plugin-objectName(): akregator LIBNAMEPART: akregatorpart Loading Plugin: Popup Notes log_kontactinterface: plugin-objectName()= knotes running standalone: false log_kontactinterface: plugin-objectName(): knotes LIBNAMEPART: Loading Plugin: Summary LIBNAMEPART: Plugging New actions new_mail Plugging New actions new_contact Plugging New actions new_contactgroup Plugging New actions new_event Plugging New actions new_todo Plugging New actions feed_new Plugging New actions new_journal Plugging New actions new_note log_kontactinterface: kmailpart log_kontactinterface: Creating new KPart log_kontactinterface: /usr/local/kde5/lib/x86_64-linux-gnu/plugins/kmailpart.so log_kmail: InstanceName: kontact log_kmail: InstanceName: kontact log_kmail: Starting up... KMail Kernel ETM () connectToServer /tmp/akonadi-rserral.Tgp2RG/akonadiserver.socket connectToServer /tmp/akonadi-rserral.Tgp2RG/akonadiserver.socket log_mailtransport: Found Akonadi type Dummy MailTransport Resource log_mailtransport: Have SMTP, Sendmail, and 1 Akonadi types. log_mailtransport: 1551162894 log_mailtransport: type 0 log_mailtransport: 514864914 log_mailtransport: type 0 log_mailtransport: 657394172 log_mailtransport: type 0 log_mailtransport: 1996210202 log_mailtransport: type 0 log_mailtransport: log_kmail: log_kmail: KMail init with akonadi server state: 2 log_mailcommon: Initialized and looking for specialcollection folders. QObject::connect: No such signal MessageList::Pane::closeRequest(QWidget*) in /usr/src/kde5/src/kde/kdepim/messagelist/pane.cpp:167 log_messagelist: Invalid content item type log_messagelist: Left content item loading failed log_messagelist: Group header row loading failed log_messagelist: Column loading failed log_messagelist: Saved theme loading failed log_messagelist: Invalid content item type log_messagelist: Left content item loading failed log_messagelist: Group header row loading failed log_messagelist: Column loading failed log_messagelist: Saved theme loading failed log_messagelist: Invalid content item type log_messagelist: Left content item loading failed log_messagelist: Group header row loading failed log_messagelist: Column loading failed log_messagelist: Saved theme loading failed log_messagelist: Using model: Akonadi::EntityTreeModel QObject::connect: No such signal MessageList::Pane::mouseMiddleClick(QWidget*) in /usr/src/kde5/src/kde/kdepim/messagelist/pane.cpp:187 kf5.kxmlgui: Registering action add_addr_book under new name add_to_existing_contact kf5.kxmlgui: Registering action openin_addr_book under new name edit_contact codecForName: ucnv_open failed ISO-8859-16 U_FILE_ACCESS_ERROR ASSERT: false in file /usr/src/kde5/src/kde/kdepimlibs/akonadi-mime/src/standardmailactionmanager.cpp, line 872 *** KMail got signal 6 (Exiting) *** Dead letters dumped. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = /usr/local/kde5/bin pid = 13738 KCrash: Arguments: /usr/local/kde5/bin/kontact KCrash: Attempting to start /usr/local/kde5/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000
[kontact] [Bug 348304] New: Starting Kontact or kmail results in a crash
https://bugs.kde.org/show_bug.cgi?id=348304 Bug ID: 348304 Summary: Starting Kontact or kmail results in a crash Product: kontact Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com Application: kontact (4.73 pre) Qt Version: 5.4.0 Operating System: Linux 4.0.4 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Every time I start the kontact/kmail I get this crash. I tried wiping out all the configuration without any difference. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f17ca3c0800 (LWP 24751))] Thread 10 (Thread 0x7f17c64ac700 (LWP 24753)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f17e61226b0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f17e61226d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f17db2f10a4 in start_thread (arg=0x7f17c64ac700) at pthread_create.c:309 #4 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 9 (Thread 0x7f177f324700 (LWP 24754)): #0 0x7ffecd432cce in clock_gettime () #1 0x7f17db653c9d in __GI___clock_gettime (clock_id=optimized out, tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f17dc286436 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f17dc463329 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f17dc4650ee in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f17d97c68c1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f17d97c6e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f17d97c6fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f17dc46595c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f17dc40b0e2 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f17dc1cbaa4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f17dc1d0a5e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f17db2f10a4 in start_thread (arg=0x7f177f324700) at pthread_create.c:309 #13 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 8 (Thread 0x7f177d7aa700 (LWP 24755)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f17e5e2464d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f17e61535c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f17db2f10a4 in start_thread (arg=0x7f177d7aa700) at pthread_create.c:309 #4 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 7 (Thread 0x7f177cf8a700 (LWP 24756)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f17e5e25663 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f17e61535c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f17db2f10a4 in start_thread (arg=0x7f177cf8a700) at pthread_create.c:309 #4 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f1777fff700 (LWP 24757)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f17e5e25663 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f17e61535c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f17db2f10a4 in start_thread (arg=0x7f1777fff700) at pthread_create.c:309 #4 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f1fe700 (LWP 24758)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f17e5e25663 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f17e61535c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f17db2f10a4 in start_thread (arg=0x7f1fe700) at pthread_create.c:309 #4 0x7f17db64704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f1776ffd700 (LWP 24759)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1
[kontact] [Bug 343856] New: Kontact crashed when starting Plasma
https://bugs.kde.org/show_bug.cgi?id=343856 Bug ID: 343856 Summary: Kontact crashed when starting Plasma Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com Application: kontact (4.14.4) KDE Platform Version: 4.14.4 Qt Version: 4.8.6 Operating System: Linux 3.18.3-1-desktop x86_64 Distribution: openSUSE 20150203 (Tumbleweed) (x86_64) -- Information about the crash: - What I was doing when the application crashed: I just logged in, the app crashed when launching Plasma with the apps. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f340efb4800 (LWP 2041))] Thread 7 (Thread 0x7f33f1708700 (LWP 2049)): #0 0x7f34065e485f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f340b763806 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f340b763839 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f33b0e05700 (LWP 2053)): #0 0x7f34065e485f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f340b4d633d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f340b78b376 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f339ce53700 (LWP 2299)): #0 0x7f3406013339 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f3406013b03 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3406013cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f340ccc301e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #4 0x7f340cc94daf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #5 0x7f340cc950a5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #6 0x7f340cb9249f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f340cb94b7f in () at /usr/lib64/libQtCore.so.4 #8 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f3395d6b700 (LWP 2415)): #0 0x7f340c54651d in read () at /lib64/libc.so.6 #1 0x7f3406054750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3406013714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3406013b7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3406013cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f340ccc301e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #6 0x7f340cc94daf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #7 0x7f340cc950a5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #8 0x7f340cb9249f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7f340cc766b3 in () at /usr/lib64/libQtCore.so.4 #10 0x7f340cb94b7f in () at /usr/lib64/libQtCore.so.4 #11 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f3385788700 (LWP 2427)): #0 0x7f340c54651d in read () at /lib64/libc.so.6 #1 0x7f3406054750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3406013714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3406013b7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3406013f0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7f338d6fd576 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7f3406038b85 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f3384c41700 (LWP 2430)): #0 0x7f340c54a44d in poll () at /lib64/libc.so.6 #1 0x7f3406013be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3406013cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3406013d29 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3406038b85 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f34065e03a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f340c5529ed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f340efb4800 (LWP 2041)): [KCrash
[Akonadi] [Bug 341073] New: Owncloud resource crashes after resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=341073 Bug ID: 341073 Summary: Owncloud resource crashes after resuming from suspend Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com Application: akonadi_davgroupware_resource (4.14) KDE Platform Version: 4.14.3 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.17-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I hibernated the laptop and after resuming the service crashed. I observed that this also happens sometimes after resuming from suspend to RAM. The crash can be reproduced sometimes. -- Backtrace: Application: ownCloud of type DAV groupware resource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x7fad30110107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7fad301114e8 in __GI_abort () at abort.c:89 #8 0x7fad34ef779a in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fad34ef7b09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fad34ef83f1 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fad3331f68c in Akonadi::ResourceBase::collectionsRetrieved (this=0x2140e20, collections=...) at /usr/src/kde/src/kdepimlibs/akonadi/resourcebase.cpp:789 #12 0x0044c8f1 in DavGroupwareResource::onRetrieveCollectionsFinished (this=0x2140e20, job=0x217ec50) at /usr/src/kde/src/kdepim-runtime/resources/dav/resource/davgroupwareresource.cpp:671 #13 0x0046cc28 in DavGroupwareResource::qt_static_metacall (_o=0x2140e20, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fff0b888210) at /usr/src/kde/build/kdepim-runtime/resources/dav/resource/moc_davgroupwareresource.cpp:105 #14 0x7fad35020f4c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7fad33d55593 in KJob::result (this=0x217ec50, _t1=0x217ec50) at /usr/src/kde/build/kdelibs/kdecore/kjob.moc:207 #16 0x7fad33d54a5d in KJob::emitResult (this=0x217ec50) at /usr/src/kde/src/kdelibs/kdecore/jobs/kjob.cpp:318 #17 0x0041b7af in DavCollectionsMultiFetchJob::davJobFinished (this=0x217ec50, job=0x215e860) at /usr/src/kde/src/kdepim-runtime/resources/dav/common/davcollectionsmultifetchjob.cpp:60 #18 0x0046b53f in DavCollectionsMultiFetchJob::qt_static_metacall (_o=0x217ec50, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff0b888400) at /usr/src/kde/build/kdepim-runtime/resources/dav/resource/moc_davcollectionsmultifetchjob.cpp:55 #19 0x7fad35020f4c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x7fad33d55593 in KJob::result (this=0x215e860, _t1=0x215e860) at /usr/src/kde/build/kdelibs/kdecore/kjob.moc:207 #21 0x7fad33d54a5d in KJob::emitResult (this=0x215e860) at /usr/src/kde/src/kdelibs/kdecore/jobs/kjob.cpp:318 #22 0x00416ef5 in DavCollectionsFetchJob::collectionsFetchFinished (this=0x215e860, job=0x1f7b730) at /usr/src/kde/src/kdepim-runtime/resources/dav/common/davcollectionsfetchjob.cpp:305 #23 0x0046b323 in DavCollectionsFetchJob::qt_static_metacall (_o=0x215e860, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fff0b888de0) at /usr/src/kde/build/kdepim-runtime/resources/dav/resource/moc_davcollectionsfetchjob.cpp:58 #24 0x7fad35020f4c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7fad33d55593 in KJob::result (this=0x1f7b730, _t1=0x1f7b730) at /usr/src/kde/build/kdelibs/kdecore/kjob.moc:207 #26 0x7fad33d54a5d in KJob::emitResult (this=0x1f7b730) at /usr/src/kde/src/kdelibs/kdecore/jobs/kjob.cpp:318 #27 0x7fad337b638c in KIO::SimpleJob::slotFinished (this=0x1f7b730) at /usr/src/kde/src/kdelibs/kio/kio/job.cpp:496 #28 0x7fad337b94d6 in KIO::TransferJob::slotFinished (this=0x1f7b730) at /usr/src/kde/src/kdelibs/kio/kio/job.cpp:1110 #29 0x7fad337967e9 in KIO::DavJob::slotFinished (this=0x1f7b730) at /usr/src/kde/src/kdelibs/kio/kio/davjob.cpp:138 #30 0x7fad33796c3b in KIO::DavJob::qt_static_metacall (_o=0x1f7b730, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff0b8893b0) at /usr/src/kde/build/kdelibs/kio/davjob.moc:50 #31 0x7fad35020f4c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #32 0x7fad33878615 in KIO::SlaveInterface::finished (this=0x2179b40) at
[kmail2] [Bug 335820] New: Unable to move mails from an imported folder to another one: Unable to retrieve item from resource: Invalid item retrieved
https://bugs.kde.org/show_bug.cgi?id=335820 Bug ID: 335820 Summary: Unable to move mails from an imported folder to another one: Unable to retrieve item from resource: Invalid item retrieved Classification: Unclassified Product: kmail2 Version: 4.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com I have a Local Folders resource in Akonadi used in KMail. Akonadi runs in a separate MySQL/MariaDB database. After importing thousands of mails from Thunderbird I tried to reorganize them a bit. Unfortunately, I'm unable to move a lot mails (not all) from an the imported folders to another one create new in KMail. It fails with a messagebox: Unable to retrieve item from resource: Invalid item retrieved. From the user's point of view, I cannot recognize any problem with the original mail to move, no broken header, all intact. After some search, I'm able to find single mails which break this move action, but I don't know what is so special about them compared against the mails I moved successfully. Maybe one of you guys can give me a hint what else information could be useful for analyzing this. Reproducible: Sometimes Steps to Reproduce: 1. Import a folder structure from Thunderbird (I had 1 or more mails there) 2. Create another target folder structure in KMail under Local Folders 3. Move mails in several folders to the newly created folders Actual Results: Unable to retrieve item from resource: Invalid item retrieved during moving several mails in several folders Expected Results: Moving should succeed. -- 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 335820] Unable to move mails from an imported folder to another one: Unable to retrieve item from resource: Invalid item retrieved
https://bugs.kde.org/show_bug.cgi?id=335820 --- Comment #1 from René Krell renda.kr...@gmail.com --- What I haven't seen in KMail, the bodies of mails which cannot be moved aren't really shown in KMail on clicking at their headers, but there is show the header of the last mail that could be really retrieved. The message window isn't even cleared, it just gets stuck on old contents if a message cannot be retrieved. -- 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 335457] New: Kontact/KMail crash when deleting a folder with subfolders imported from Thunderbird to a Local Folders Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=335457 Bug ID: 335457 Summary: Kontact/KMail crash when deleting a folder with subfolders imported from Thunderbird to a Local Folders Akonadi resource Classification: Unclassified Product: kontact Version: 4.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com Application: kontact (4.13.1) KDE Platform Version: 4.13.1 Qt Version: 4.8.6 Operating System: Linux 3.14.4-30.gbebeb6f-desktop x86_64 Distribution: openSUSE 13.1 (Bottle) (x86_64) -- Information about the crash: - What I was doing when the application crashed: I tried to delete a folder with several subfolders recursively in the KMail view of Kontact. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. gobject.py: gdb was not built with custom backtrace support, disabling. [Current thread is 1 (Thread 0x7fa86695d880 (LWP 16194))] Thread 7 (Thread 0x7fa84915d700 (LWP 16195)): #0 0x7fa85df2d0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa8616cdf56 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fa8616cdf89 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fa85df290db in start_thread () from /lib64/libpthread.so.0 #4 0x7fa863ea990d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fa808842700 (LWP 16196)): #0 0x7fa85df2d0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa8614402ad in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fa8616f5ab6 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fa85df290db in start_thread () from /lib64/libpthread.so.0 #4 0x7fa863ea990d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fa7f577b700 (LWP 16200)): #0 0x7fa85df2c560 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x7fa85d9a0a11 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa85d95e690 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa85d95ef23 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa85d95f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fa864629986 in QEventDispatcherGlib::processEvents (this=0x7fa7f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x7fa8645fb79f in QEventLoop::processEvents (this=this@entry=0x7fa7f577ad60, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fa8645fba95 in QEventLoop::exec (this=this@entry=0x7fa7f577ad60, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fa8644f82ff in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #9 0x7fa8644fa9cf in QThreadPrivate::start (arg=0x1ae07f0) at thread/qthread_unix.cpp:349 #10 0x7fa85df290db in start_thread () from /lib64/libpthread.so.0 #11 0x7fa863ea990d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fa7ed04e700 (LWP 16210)): #0 0x7fa863ea0b3d in poll () from /lib64/libc.so.6 #1 0x7fa85d95f004 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa85d95f10c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa864629986 in QEventDispatcherGlib::processEvents (this=0x7fa7e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7fa8645fb79f in QEventLoop::processEvents (this=this@entry=0x7fa7ed04dd20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fa8645fba95 in QEventLoop::exec (this=this@entry=0x7fa7ed04dd20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fa8644f82ff in QThread::exec (this=this@entry=0x22ae550) at thread/qthread.cpp:538 #7 0x7fa8645dcfa3 in QInotifyFileSystemWatcherEngine::run (this=0x22ae550) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7fa8644fa9cf in QThreadPrivate::start (arg=0x22ae550) at thread/qthread_unix.cpp:349 #9 0x7fa85df290db in start_thread () from /lib64/libpthread.so.0 #10 0x7fa863ea990d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fa7d6ae0700 (LWP 16463)): #0 0x7fa85d9a06ca in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7fa85d9a09d9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa85d95e567 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa85d95ef23 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa85d95f32a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #5 0x7fa7dbde71f6 in ?? () from /usr/lib64/libgio-2.0.so.0 #6 0x7fa85d983fa5 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fa85df290db in start_thread () from /lib64/libpthread.so.0 #8 0x7fa863ea990d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa7d62df700 (LWP 16464)): #0 0x7fa863ea0b3d in poll () from /lib64/libc.so.6 #1
[kontact] [Bug 335457] Kontact/KMail crash when deleting a folder with subfolders imported from Thunderbird to a Local Folders Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=335457 --- Comment #1 from René Krell renda.kr...@gmail.com --- After that crash, KMail does not come up but hangs in background. After launching 'akonadictl restart' it comes up immediately. The folder I wanted to delete initially is still there in the Local Folders resource. -- 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
[kaddressbook] [Bug 324339] Google contacts gone after deleting addressbook
https://bugs.kde.org/show_bug.cgi?id=324339 René Fritz r...@colorcube.de changed: What|Removed |Added CC||r...@colorcube.de --- Comment #6 from René Fritz r...@colorcube.de --- I can confirm this problem. I have multiple groups named 'Starred in Android'. I guess this is because I have multiple Android devices. Therefore the groups appear again shortly after removing them (due to syncing). This means there's no workaround available for my szenario. The log looks similar for me. -- 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 316723] New: Google Contacts resource crashes upon contact creation
https://bugs.kde.org/show_bug.cgi?id=316723 Bug ID: 316723 Summary: Google Contacts resource crashes upon contact creation Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: rser...@gmail.com CC: kdepim-bugs@kde.org Application: akonadi_googlecontacts_resource (4.10) KDE Platform Version: 4.10.1 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.8.2 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: I just inserted a new contact to my addressbook, and after selecting a nepomuk category it crashed. Since then on every start of the resource I get the crash as attached on the backtrace. I observed that modifying a contact adding the category also causes the crash. The crash can be reproduced sometimes. -- Backtrace: Application: Google Contacts (akonadi_googlecontacts_resource), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x7f91f4abc475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f91f4abf6f0 in *__GI_abort () at abort.c:92 #8 0x7f91f4af752b in __libc_message (do_abort=optimized out, fmt=optimized out) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #9 0x7f91f4b00d76 in malloc_printerr (action=3, str=0x7f91f4bd9228 double free or corruption (out), ptr=optimized out) at malloc.c:6283 #10 0x7f91f4b05aac in *__GI___libc_free (mem=optimized out) at malloc.c:3738 #11 0x7f91f73f36d4 in KGAPI::Objects::Contact::~Contact (this=0x7fff5843e090, __in_chrg=optimized out) at /media/kdesvn/kde4svn/src/libkgapi/common/contact.inc.cpp:84 #12 0x7f91f74071b9 in QtSharedPointer::ExternalRefCountKGAPI2::Contact::deref (d=0xb046c0, value=0x7fff5843e090) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:342 #13 0x7f91f7406e20 in QtSharedPointer::ExternalRefCountKGAPI2::Contact::deref (this=0x7fff5843e030) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:336 #14 0x7f91f740697c in QtSharedPointer::ExternalRefCountKGAPI2::Contact::~ExternalRefCount (this=0x7fff5843e030, __in_chrg=optimized out) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:401 #15 0x7f91f7406880 in QSharedPointerKGAPI2::Contact::~QSharedPointer (this=0x7fff5843e030, __in_chrg=optimized out) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:466 #16 0x7f91f7404fac in KGAPI::Services::Contacts::objectToXML (this=0x7fff5843e0c0, object=0x7fff5843e090) at /media/kdesvn/kde4svn/src/libkgapi/libkgapi/services/contacts.cpp:64 #17 0x0040e584 in ContactsResource::itemChanged (this=0xae8310, item=..., partIdentifiers=...) at /media/kdesvn/kde4svn/src/kdepim-runtime/resources/google/contacts/contactsresource.cpp:363 #18 0x7f91f90ede74 in Akonadi::AgentBasePrivate::itemChanged (this=0xaab520, item=..., partIdentifiers=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/agentbase.cpp:327 #19 0x7f91f91cb26a in Akonadi::ResourceBasePrivate::itemChanged (this=0xaab520, item=..., partIdentifiers=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/resourcebase.cpp:226 #20 0x7f91f91c9785 in Akonadi::ResourceBasePrivate::qt_static_metacall (_o=0xaab520, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7fff5843e420) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/resourcebase.moc:89 #21 0x7f91f8a4954f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7f91f91adc6f in Akonadi::Monitor::itemChanged (this=0xaa71d0, _t1=..., _t2=...) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/moc_monitor.cpp:189 #23 0x7f91f91b1eb4 in Akonadi::MonitorPrivate::emitItemNotification (this=0xab2050, msg=..., item=..., collection=..., collectionDest=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/monitor_p.cpp:554 #24 0x7f91f91b06a3 in Akonadi::MonitorPrivate::emitNotification (this=0xab2050, msg=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/monitor_p.cpp:296 #25 0x7f91f910f562 in Akonadi::ChangeRecorderPrivate::emitNotification (this=0xab2050, msg=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/changerecorder_p.cpp:54 #26 0x7f91f91b1351 in Akonadi::MonitorPrivate::flushPipeline (this=0xab2050) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/monitor_p.cpp:457 #27 0x7f91f91b13cc in Akonadi::MonitorPrivate::dataAvailable (this=0xab2050) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/monitor_p.cpp:466 #28 0x7f91f91adaaf in Akonadi::Monitor::qt_static_metacall (_o=0xaa71d0, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0x7fff5843e9b0) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/moc_monitor.cpp:137 #29 0x7f91f8a4954f in
[kmail2] [Bug 315518] New: Moving IMAP folders not working
https://bugs.kde.org/show_bug.cgi?id=315518 Bug ID: 315518 Summary: Moving IMAP folders not working Classification: Unclassified Product: kmail2 Version: 4.10 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com When I try to move an IMAP subfolder to another IMAP folder within the same account it doesn't work displaying a message: Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. However reading mails, sending, browsing works as expected. Reproducible: Always Steps to Reproduce: 1. Drag an IMAP directory to a different location 2. Select move from the popup Actual Results: Error message displayed Expected Results: Actually moving the directory -- 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 313235] New: Restarting akonadi crashes kontact
https://bugs.kde.org/show_bug.cgi?id=313235 Bug ID: 313235 Summary: Restarting akonadi crashes kontact Classification: Unclassified Product: kontact Version: unspecified Hardware: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com Application: kontact (4.10 rc2) KDE Platform Version: 4.9.97 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.7.1 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: - What I was doing when the application crashed: Most of the times, when I run from a console: akonadictl restart Kontact (and plasma-desktop) crash with the attached backtrace. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f02c943d780 (LWP 21905))] Thread 5 (Thread 0x7f02c20fd700 (LWP 22064)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f02debfbebd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f02debfbfc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f02dab8db50 in start_thread (arg=optimized out) at pthread_create.c:304 #4 0x7f02d8c99a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f02c17fc700 (LWP 22070)): #0 0x7f02dab9162e in __pthread_mutex_unlock_usercnt (mutex=0x7f02bc0008b0, decr=optimized out) at pthread_mutex_unlock.c:52 #1 0x7f02d74a5451 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f02d7468e1d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f02d746954b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f02d7469744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f02daf4e296 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f02daf1e8af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f02daf1eb38 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f02dae21d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f02dae24d0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f02dab8db50 in start_thread (arg=optimized out) at pthread_create.c:304 #11 0x7f02d8c99a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 3 (Thread 0x7f026894a700 (LWP 18575)): #0 0x7f02d8c8ee33 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f02d7469624 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f02d7469744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f02daf4e296 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f02daf1e8af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f02daf1eb38 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f02dae21d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f02daeff1bf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f02dae24d0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f02dab8db50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f02d8c99a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f026cd99700 (LWP 18581)): #0 0x7f02dab9518d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f02d74a477f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f02d74691a9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f02d74695c2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f02d7469744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f02daf4e296 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f02daf1e8af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f02daf1eb38 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
[Bug 312528] New: Pressing f to forward doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=312528 Bug ID: 312528 Summary: Pressing f to forward doesn't work anymore Classification: Unclassified Product: kmail2 Version: 4.9.95 RC1 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com I updated to 4.10 recent git and now the shortcut F to forward e-mails is not working anymore. In fact in the list of shortcuts it does not appear. The other shortcuts seem to work correctly. -- 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
[Bug 312528] Pressing f to forward doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=312528 --- Comment #2 from René Serral rser...@gmail.com --- Mmmm, Alt+F in my configuration conflicts with As Attachment... and the file menu Anyhow the option to change Forwarding shorcut in the Configure Shortcuts is not present. Best René On Thursday 03 January 2013 10:40:33 Laurent Montel wrote: https://bugs.kde.org/show_bug.cgi?id=312528 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel mon...@kde.org --- yes was replace by ALT+F. It conflicted before so I replaced by ALT+F -- 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
[Bug 312114] New: Crash while adding a folder in Kmail
https://bugs.kde.org/show_bug.cgi?id=312114 Bug ID: 312114 Summary: Crash while adding a folder in Kmail Classification: Unclassified Product: kontact Version: 4.9.3 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: waterfront5...@gmail.com Application: kontact (4.9.3) KDE Platform Version: 4.9.3 Qt Version: 4.8.3 Operating System: Linux 3.5.0-19-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: I right-clicked on my Google IMAP mailbox in the sidepane and selected 'Add folder', then typed the name of my new folder. When I clicked 'OK', Kontact crashed. The behaviour does not seem to be systematic: this is the first time I notice this, and I've added folders like this before. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff390ce97c0 (LWP 1721))] Thread 4 (Thread 0x7ff3898af700 (LWP 1723)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7ff3a225fb2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ff3a225fc39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ff39d7aae9a in start_thread (arg=0x7ff3898af700) at pthread_create.c:308 #4 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7ff3890ae700 (LWP 1724)): #0 0x7ff39d318c31 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff39d2db623 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff39d2dbcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff39d2dbea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff3a36ffc16 in QEventDispatcherGlib::processEvents (this=0x7ff3840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7ff3a36d02bf in QEventLoop::processEvents (this=this@entry=0x7ff3890addc0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7ff3a36d0548 in QEventLoop::exec (this=0x7ff3890addc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7ff3a35d1b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7ff3a35d4aec in QThreadPrivate::start (arg=0x1bca1f0) at thread/qthread_unix.cpp:338 #9 0x7ff39d7aae9a in start_thread (arg=0x7ff3890ae700) at pthread_create.c:308 #10 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7ff33b2b7700 (LWP 2035)): #0 0x7fff5cdff827 in clock_gettime () #1 0x7ff39bb0d15d in __GI_clock_gettime (clock_id=optimized out, tp=optimized out) at ../sysdeps/unix/clock_gettime.c:116 #2 0x7ff3a362a9c4 in do_gettime (frac=0x7ff33b2b6ae8, sec=0x7ff33b2b6ae0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7ff3a370041d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7ff334002660) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7ff3a3700763 in QTimerInfoList::timerWait (this=0x7ff334002660, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7ff3a36ff2cc in timerSourcePrepareHelper (src=optimized out, timeout=0x7ff33b2b6bd4) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7ff3a36ff375 in timerSourcePrepare (source=optimized out, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7ff39d2db618 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7ff39d2dbcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7ff39d2dbea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7ff3a36ffc16 in QEventDispatcherGlib::processEvents (this=0x7ff3340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7ff3a36d02bf in QEventLoop::processEvents (this=this@entry=0x7ff33b2b6d90, flags=...) at kernel/qeventloop.cpp:149 #13 0x7ff3a36d0548 in QEventLoop::exec (this=0x7ff33b2b6d90, flags=...) at kernel/qeventloop.cpp:204 #14 0x7ff3a35d1b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #15 0x7ff3a36b09af in QInotifyFileSystemWatcherEngine::run (this=0x21b9910) at io/qfilesystemwatcher_inotify.cpp:248 #16 0x7ff3a35d4aec in QThreadPrivate::start (arg=0x21b9910) at thread/qthread_unix.cpp:338 #17 0x7ff39d7aae9a in start_thread (arg=0x7ff33b2b7700) at pthread_create.c:308 #18 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #19 0x in ?? () Thread 1 (Thread 0x7ff390ce97c0 (LWP 1721)): [KCrash Handler] #6
[Bug 312139] New: Crash editing recurring event on kontact
https://bugs.kde.org/show_bug.cgi?id=312139 Bug ID: 312139 Summary: Crash editing recurring event on kontact Classification: Unclassified Product: kontact Version: unspecified Hardware: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com Application: kontact (4.10 rc1) KDE Platform Version: 4.9.95 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.7.1 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: I'm using google calendar resource, and while editing a recurring event, just double clicking on the event I get a kontact crash with the attached backtrace. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fc4780b6780 (LWP 19301))] Thread 3 (Thread 0x7fc470757700 (LWP 19302)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fc48d873ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc48d873fc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc489805b50 in start_thread (arg=optimized out) at pthread_create.c:304 #4 0x7fc487911a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7fc46fe56700 (LWP 19303)): #0 0x7fc48980d18d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fc48611c77f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4860e11a9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4860e15c2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc4860e1744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc489bc6296 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fc489b968af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fc489b96b38 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fc489a99d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fc489a9cd0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fc489805b50 in start_thread (arg=optimized out) at pthread_create.c:304 #11 0x7fc487911a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7fc4780b6780 (LWP 19301)): [KCrash Handler] #6 0x7fc487869475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7fc48786c6f0 in *__GI_abort () at abort.c:92 #8 0x7fc489a92722 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fc489a92a98 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fc489a92c24 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fc46cc59a5c in IncidenceEditorNG::CombinedIncidenceEditor::load (this=0x3f68280, incidence=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/combinedincidenceeditor.cpp:108 #12 0x7fc46cc9e1d7 in IncidenceEditorNG::EventOrTodoDialogPrivate::load (this=0x3f5ae00, item=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/eventortododialog.cpp:532 #13 0x7fc46cc5665b in IncidenceEditorNG::EditorItemManager::load (this=0x3f68440, item=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/editoritemmanager.cpp:282 #14 0x7fc46cc9f630 in IncidenceEditorNG::EventOrTodoDialog::load (this=0x45fde30, item=..., activeDate=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/eventortododialog.cpp:693 #15 0x7fc46da2335f in CalendarView::editIncidence (this=0x2d62ee0, item=..., isCounter=false) at /media/kdesvn/kde4svn/src/kdepim/korganizer/calendarview.cpp:2524 #16 0x7fc46da282fe in CalendarView::qt_static_metacall (_o=0x2d62ee0, _c=QMetaObject::InvokeMetaMethod, _id=50, _a=0x7fff00621640) at /media/kdesvn/kde4svn/build/kdepim/korganizer/calendarview.moc:439 #17 0x7fc489bad54f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7fc46c548957 in KOrg::BaseView::editIncidenceSignal (this=0x2f24a60, _t1=...) at /media/kdesvn/kde4svn/build/kdepim/korganizer/interfaces/korganizer/baseview.moc:202 #19 0x7fc46c548379 in KOrg::BaseView::qt_static_metacall (_o=0x2f24a60, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fff006217d0) at
[Bug 311938] New: Random crashes on one of my IMAP accounts
https://bugs.kde.org/show_bug.cgi?id=311938 Bug ID: 311938 Severity: crash Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Random crashes on one of my IMAP accounts Classification: Unclassified OS: Linux Reporter: rser...@gmail.com Hardware: Compiled Sources Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.9) KDE Platform Version: 4.9.95 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.7.1 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: I just upgraded to a 4.10 git branch, and since then one of my IMAP accounts crashes, the other one seems stable. This behaviour was not experienced in my last 4.9.4 installation (also from sources) The crash can be reproduced every time. -- Backtrace: Application: Matpol of type IMAP E-Mail Server (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f9198d60760 (LWP 4733))] Thread 2 (Thread 0x7f9183f10700 (LWP 4735)): #0 0x7f9193acce33 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f9192a77624 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9192a77744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9198120296 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f91980f08af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f91980f0b38 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f9197ff3d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f9196b2763f in KIMAP::SessionThread::run (this=0xc0dcd0) at /media/kdesvn/kde4svn/src/kdepimlibs/kimap/sessionthread.cpp:182 #8 0x7f9197ff6d0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f9197d5fb50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f9193ad7a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f9198d60760 (LWP 4733)): [KCrash Handler] #6 0x7f9193a2f475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f9193a326f0 in *__GI_abort () at abort.c:92 #8 0x7f9197fec722 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f9197feca98 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f9197fecc24 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f9196b23db1 in KIMAP::SessionPrivate::startSocketTimer (this=0xc0dae0) at /media/kdesvn/kde4svn/src/kdepimlibs/kimap/session.cpp:462 #12 0x7f9196b2275b in KIMAP::SessionPrivate::doStartNext (this=0xc0dae0) at /media/kdesvn/kde4svn/src/kdepimlibs/kimap/session.cpp:166 #13 0x7f9196b240e5 in KIMAP::Session::qt_static_metacall (_o=0xc0d9f0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xea63a0) at /media/kdesvn/kde4svn/build/kdepimlibs/kimap/moc_session.cpp:88 #14 0x7f9198106a2e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7f919727f70c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x7f9197283b8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x7f9194f7cd4a in KApplication::notify (this=0x7fff33d85600, receiver=0xc0d9f0, event=0xd87ee0) at /media/kdesvn/kde4svn/src/kdelibs/kdeui/kernel/kapplication.cpp:311 #18 0x7f91980f1b5e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #19 0x7f91980f59e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x7f91981200e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #21 0x7f9192a77355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f9192a77688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f9192a77744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f9198120276 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7f919732083e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x7f91980f08af in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #27
[Bug 311496] New: Contacts Autocompletion list is difficult to use
https://bugs.kde.org/show_bug.cgi?id=311496 Bug ID: 311496 Severity: normal Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Contacts Autocompletion list is difficult to use Classification: Unclassified OS: Linux Reporter: rser...@gmail.com Hardware: Other Status: UNCONFIRMED Component: composer Product: kmail2 I'm using two external addressbook, Google and LDAP. When I type a name of a contact in composer (now it works!) i get a list of my contacts LDAP + Google however in my preferences I have that first I want to see my google contacts. Besides, when autocompletion shows if I move the cursor down to select an entry it keeps going up to the first entry, making it very difficult to select the contact using the keyboard, I have either to wait a while to be able to select it, or be really fast pressing down and enter to select the desired entry rather than the first one. Reproducible: Always Steps to Reproduce: 1. Enter a contact name in the To or CC fields 2. Wait for autocompletion to show 3. Try to select fourth entry, cursor keeps going to the first for a while Actual Results: If you are not careful you'll select the wrong recipient Expected Results: Actually keep the focus on the desired entry -- 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
[Bug 132515] Chiasmus support: File /usr/local/bin/chiasmus does not exist or is not executable
https://bugs.kde.org/show_bug.cgi?id=132515 René Mérou rene.me...@kdemail.net changed: What|Removed |Added CC||rene.me...@kdemail.net --- Comment #4 from René Mérou rene.me...@kdemail.net --- I use debian kernel 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux kde 4.8.4 and kmail 1.13.7 and i have same problem. I try to use signature but i cant because there is not that chiasmus file and i cant configure it. I tried to install kleopatra but it did not fixed it. It seems this bug was resolved some years ago but I cant find the way to fix it. Regards -- René -- 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
[Bug 132515] Chiasmus support: File /usr/local/bin/chiasmus does not exist or is not executable
https://bugs.kde.org/show_bug.cgi?id=132515 --- Comment #5 from René Mérou rene.me...@kdemail.net --- It seems now i solved it. It keeps saying it cant find chiasmus but i managed to use opengpg with kleopatra. i installed aptitude install kgpg gpgsm kleopatra gnupg-agent pinentry-qt I dont know if that was necessary. I selected my key in kleopatra. I selected it in my kmail users identities. And now a normal email can be signed. Regards -- René -- 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
[Bug 295983] New: KMail crash shortly after startup when navigating between mail folders
https://bugs.kde.org/show_bug.cgi?id=295983 Bug ID: 295983 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail crash shortly after startup when navigating between mail folders Classification: Unclassified OS: Linux Reporter: renda.kr...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.2.9-14-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I changed some EMail-folder by clicking on the new one. KMail has been launched after quite a long time. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7f84267a5780 (LWP 3783))] Thread 4 (Thread 0x7f840639e700 (LWP 3793)): #0 0x7f84218f5e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8417fabc12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f8417fabc49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f84218f1f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8423aea10d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8405a9d700 (LWP 3794)): #0 0x7f84218f511f in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x7f841bcc7b14 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f841bcc892d in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f841bcc8f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8425146956 in QEventDispatcherGlib::processEvents (this=0x7f8408c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f8425116682 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f84251168d7 in QEventLoop::exec (this=0x7f8405a9ce00, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f8425017537 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f842501a55b in QThreadPrivate::start (arg=0xa4fb50) at thread/qthread_unix.cpp:298 #9 0x7f84218f1f05 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8423aea10d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f83b7fff700 (LWP 3818)): [KCrash Handler] #9 0x7f8423a85a0a in malloc_consolidate () from /lib64/libc.so.6 #10 0x7f8423a86bf3 in _int_malloc () from /lib64/libc.so.6 #11 0x7f8423a8983e in malloc () from /lib64/libc.so.6 #12 0x7f842501c558 in QByteArray::realloc (this=0x7f83ac0028a8, alloc=65504) at tools/qbytearray.cpp:1452 #13 0x7f842501c679 in QByteArray::resize (this=0x7f83ac0028a8, size=32768) at tools/qbytearray.cpp:1420 #14 0x7f8422b0e986 in reserve (bytes=2, this=0x7f83ac002d70) at ../../src/corelib/tools/qringbuffer_p.h:158 #15 QAbstractSocket::writeData (this=optimized out, data=0x7f83b7ffe62c \021, size=2) at socket/qabstractsocket.cpp:2315 #16 0x7f84250aa82f in QIODevice::write (this=0x7f83ac0023e0, data=0x7f83b7ffe62c \021, maxSize=optimized out) at io/qiodevice.cpp:1370 #17 0x7f84156d7b25 in Soprano::DataStream::writeUnsignedInt16 (this=0x7f83b7ffe650, v=17) at /usr/src/debug/soprano-2.7.5/server/datastream.cpp:95 #18 0x7f84156decba in Soprano::Client::ClientConnection::executeQuery (this=0xd56a30, modelId=1686213856, query=..., type=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:263 #19 0x7f84156e0803 in Soprano::Client::ClientModel::executeQuery (this=optimized out, query=optimized out, language=optimized out, userQueryLanguage=optimized out) at /usr/src/debug/soprano-2.7.5/client/clientmodel.cpp:101 #20 0x7f841c8cd64c in Nepomuk::MainModel::executeQuery (this=0xd37b10, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/nepomukmainmodel.cpp:212 #21 0x7f841c8b9eb3 in Nepomuk::ResourceData::load (this=0x7f83ac00df00) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resourcedata.cpp:417 #22 0x7f841c8ba7bc in Nepomuk::ResourceData::property (this=0x7f83ac00df00, uri=...) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resourcedata.cpp:265 #23 0x7f841c8d07e3 in Nepomuk::Resource::property (this=0x7f83b7ffed00, uri=...) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resource.cpp:301 #24 0x7f841fc370ca in ?? () from /usr/lib64/libmessagecore.so.4 #25 0x7f842500dd12 in QThreadPoolThread::run (this=0x127d8b0) at concurrent/qthreadpool.cpp:107 #26 0x7f842501a55b in QThreadPrivate::start (arg=0x127d8b0) at thread/qthread_unix.cpp:298 #27 0x7f84218f1f05 in start_thread () from /lib64/libpthread.so.0 #28 0x7f8423aea10d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f84267a5780 (LWP
[Bug 278020] KMail cannot send e-mail via SMTP
https://bugs.kde.org/show_bug.cgi?id=278020 René Krell renda.kr...@gmail.com changed: What|Removed |Added CC||renda.kr...@gmail.com --- Comment #28 from René Krell renda krell gmail com 2011-10-25 07:09:40 --- I can confirm this, sent mails are physically sent, but remain in state Sending succeeded, but failed to finalize message. Unknown error. (No items found) locally. - KDE 4.7.2 - KMail2 1.99.0 - OS: Linux (x86_64) release 3.0.7-45-desktop - Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 284440] New: Akregator crash when fetching feeds
https://bugs.kde.org/show_bug.cgi?id=284440 Summary: Akregator crash when fetching feeds Product: akregator Version: 4.7.2 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: renda.kr...@gmail.com Application: akregator (4.7.2) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.6-44-desktop x86_64 Distribution: openSUSE 11.4 (x86_64) -- Information about the crash: After adding a new feed and repeatedly fetching all feeds Akregator crashed with the appended trace. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #6 0x7f13c9311f28 in Akregator::Article::setStatus(int) () from /usr/lib64/libakregatorprivate.so.4 #7 0x7f13c9317b3f in Akregator::Feed::appendArticles(boost::shared_ptrSyndication::Feed) () from /usr/lib64/libakregatorprivate.so.4 #8 0x7f13c9318f2a in Akregator::Feed::fetchCompleted(Syndication::Loader*, boost::shared_ptrSyndication::Feed, Syndication::ErrorCode) () from /usr/lib64/libakregatorprivate.so.4 #9 0x7f13c9319270 in Akregator::Feed::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakregatorprivate.so.4 #10 0x7f13c827de8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #11 0x7f13c3c32412 in Syndication::Loader::loadingComplete(Syndication::Loader*, boost::shared_ptrSyndication::Feed, Syndication::ErrorCode) () from /usr/lib64/libsyndication.so.4 #12 0x7f13c3c5304c in Syndication::Loader::slotRetrieverDone(QByteArray const, bool) () from /usr/lib64/libsyndication.so.4 #13 0x7f13c3c5335d in Syndication::Loader::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsyndication.so.4 #14 0x7f13c827de8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #15 0x7f13c3c32683 in Syndication::DataRetriever::dataRetrieved(QByteArray const, bool) () from /usr/lib64/libsyndication.so.4 #16 0x7f13c3c328df in Syndication::FileRetriever::slotResult(KJob*) () from /usr/lib64/libsyndication.so.4 #17 0x7f13c3c32aa3 in Syndication::FileRetriever::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsyndication.so.4 #18 0x7f13c827de8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #19 0x7f13c86d3f92 in KJob::result(KJob*) () from /usr/lib64/libkdecore.so.5 #20 0x7f13c86d3fd0 in KJob::emitResult() () from /usr/lib64/libkdecore.so.5 #21 0x7f13c659eb9d in KIO::SimpleJob::slotFinished() () from /usr/lib64/libkio.so.5 #22 0x7f13c65a2b82 in KIO::TransferJob::slotFinished() () from /usr/lib64/libkio.so.5 #23 0x7f13c65a7561 in KIO::TransferJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #24 0x7f13c827de8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #25 0x7f13c6649541 in KIO::SlaveInterface::dispatch(int, QByteArray const) () from /usr/lib64/libkio.so.5 #26 0x7f13c6646543 in KIO::SlaveInterface::dispatch() () from /usr/lib64/libkio.so.5 #27 0x7f13c66395be in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5 #28 0x7f13c6639cfc in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #29 0x7f13c827de8f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #30 0x7f13c6570f27 in ?? () from /usr/lib64/libkio.so.5 #31 0x7f13c6570fdd in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #32 0x7f13c827d7aa in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #33 0x7f13c73b5264 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #34 0x7f13c73bd81a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #35 0x7f13c8cb1ae6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #36 0x7f13c82697cc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #37 0x7f13c826cfc5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #38 0x7f13c8294443 in ?? () from /usr/lib64/libQtCore.so.4 #39 0x7f13c0c9bbd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #40 0x7f13c0c9c3b0 in ?? () from /lib64/libglib-2.0.so.0 #41 0x7f13c0c9c650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #42 0x7f13c82945df in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #43 0x7f13c745b38e in ?? () from /usr/lib64/libQtGui.so.4 #44 0x7f13c8268c22 in
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #15 from René Krell renda krell gmail com 2011-10-12 08:03:21 --- Got KMail working after removing all Akonadi user data and recreating the database (just don't know for how long): $ akonadictl stop $ rm -rf $HOME/.local/share/akonadi/ $ mysql -u root -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 43 Server version: 5.5.16-log Source distribution Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql drop database akonadi; Query OK, 11 rows affected (0.47 sec) mysql create database akonadi; Query OK, 1 row affected (0.00 sec) mysql exit Bye $ cat $HOME/.config/akonadi/akonadiserverrc [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host=localhost StartServer=false Options=UNIX_SOCKET=/var/run/mysql/mysql.sock ServerPath=/usr/bin/mysqld User=root Password=do_not_tell [Debug] Tracer=null $ akonadictl start After those actions KMail shows the selected messages. Will tell you, if it will go wrong again. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #16 from René Krell renda krell gmail com 2011-10-12 08:40:46 --- KMail hung again with Retrieving Folder Contents For me it looks like KMail deadlocks when viewing messages while resyncing resources, even if clicking on messages from other resources. In my case it was a resync of a Local KMail folders resource. After resyncing was done KMail displays all messages again, but very slowly, it takes up to a few seconds to view messages. I still don't overlook how to best reproduce it, maybe you got a hint for me. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #17 from René Krell renda krell gmail com 2011-10-12 09:00:38 --- Furthermore there isn't any mail marked as read and even Mark all as read over some folder doesn't mark messages read, regardless in which resource (IMAP, local folders, local KMail folders). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #5 from René Krell renda krell gmail com 2011-10-04 07:52:13 --- Interesting: After restart I always get 6 - 7 messages shown, but after clicking through them it hangs again with Retrieving folder contents, please wait and doesn't return. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #6 from René Krell renda krell gmail com 2011-10-04 07:55:49 --- Using MYSQL Server 5.5.16 from the openSUSE server:database repository, QtSQL client linked with MYSQL client r16 instead of r18. Maybe a bad combination, because OpenSUSE 11.4 still ships with 5.1.53? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #8 from René Krell renda krell gmail com 2011-10-04 09:24:49 --- I returned to the default MYSQL server in openSUSE 11.4 and, for being sure, uninstalled all r18 client libraries. Running ldd /usr/lib64/qt4/plugins/sqldrivers/libqsqlmysql.so |grep mysql returns: libmysqlclient_r.so.16 = /usr/lib64/libmysqlclient_r.so.16 (0x7fedb1395000) What I've done: - Quit KMail - Stop Akonadi server - Stop MySQLd - Reinstalled MySQL 5.1 as described above - Added to my.cnf in section [mysqld] a line wait_timeout = 31536000 - Start MySQLd - Start Akonadi server - Start KMail Unfortunately It is still hanging. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #10 from René Krell renda krell gmail com 2011-10-04 09:52:13 --- Created an attachment (id=64194) -- (http://bugs.kde.org/attachment.cgi?id=64194) 'akonadictl start' output -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #11 from René Krell renda krell gmail com 2011-10-04 09:55:02 --- See attachment and current error log doesn't exist in ~/.local/share/akonadi/db_data. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #12 from René Krell renda krell gmail com 2011-10-04 10:06:48 --- Currently KMail doesn't hang, I've aöready opened dozens of messages from different Akonadi resources. Strange, but the term: Reproducible: Sometimes seems to fit also for me. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #13 from René Krell renda krell gmail com 2011-10-04 10:09:42 --- ... now it is hanging again, but no new error log has appeared. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 77862] kio_imap processes hang when connection status changes
https://bugs.kde.org/show_bug.cgi?id=77862 René Krell rkr...@gmx.net changed: What|Removed |Added CC||rkr...@gmx.net -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 René Krell renda.kr...@gmail.com changed: What|Removed |Added CC||renda.kr...@gmail.com --- Comment #1 from René Krell renda krell gmail com 2011-10-03 11:14:53 --- I get a similar problem, but generally on all kinds of Akonadi resources immediately after KMail starts. KMail version 4.7.1. Akonadi uses an external, but local MYSQL server. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 77862] kio_imap processes hang when connection status changes
https://bugs.kde.org/show_bug.cgi?id=77862 --- Comment #91 from René Krell renda krell gmail com 2011-10-03 11:19:13 --- Similar to me: KMail 4.7.1 doesn not show message contents, but just a Retrieving Folder Contents Please wait ... Interesting: This happens on all kinds of Akonadi resources, not just on IMAP. Akonadi uses an external MYSQL server here and does not report to have problems with it. Messages seem to be retrieved and filters executed, just displaying messages doesn't work. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 283037] Unable to connect to akonadi after laptop resume
https://bugs.kde.org/show_bug.cgi?id=283037 --- Comment #4 from René Krell renda krell gmail com 2011-10-03 12:24:41 --- No, I left the default settings in /etc/my.conf, connecting to localhost as root (regardless whether using TCP/IP and UNIX socket): # The following options will be passed to all MySQL clients [client] #password= your_password port= 3306 socket= /var/run/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port= 3306 socket= /var/run/mysql/mysql.sock # Change following line if you want to store your database elsewhere datadir= /var/lib/mysql skip-external-locking key_buffer_size = 16M max_allowed_packet = 1M table_open_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the enable-named-pipe option) will render mysqld useless! # #skip-networking # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # binary logging format - mixed recommended binlog_format=mixed # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id= 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - #the syntax is: # #CHANGE MASTER TO MASTER_HOST=host, MASTER_PORT=port, #MASTER_USER=user, MASTER_PASSWORD=password ; # #where you replace host, user, password by quoted strings and #port by the master's port number (3306 by default). # #Example: # #CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, #MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then #start replication for the first time (even unsuccessfully, for example #if you mistyped the password in master-password and the slave fails to #connect), the slave will create a master.info file, and any later #change in this file to the variables' values below will be ignored and #overridden by the content of the master.info file, unless you shutdown #the slave server, delete master.info and restart the slaver server. #For that reason, you may want to leave the lines below untouched #(commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = hostname # # The username the slave will use for authentication when connecting # to the master - required #master-user = username # # The password the slave will authenticate with when connecting to # the master - required #master-password = password # # The port the master is listening on. # optional - defaults to 3306 #master-port = port # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /var/lib/mysql #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = /var/lib/mysql # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 16M #innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 # The safe_mysqld script [safe_mysqld] log-error= /var/log/mysql/mysqld.log socket= /var/run/mysql/mysql.sock [mysqldump] socket= /var/run/mysql/mysql.sock quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [myisamchk] key_buffer_size = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout [mysqld_multi] mysqld = /usr/bin/mysqld_safe mysqladmin = /usr/bin/mysqladmin log= /var/log/mysqld_multi.log # user = multi_admin # password = secret # If you want to use mysqld_multi uncomment 1 or more mysqld sections # below or add your own ones. # WARNING # # If you uncomment mysqld1 than make absolutely sure, that database mysql, # configured above, is not started. This may result in corrupted data! # [mysqld1] # port
[Bug 282613] New: Message tag settings not stored properly
https://bugs.kde.org/show_bug.cgi?id=282613 Summary: Message tag settings not stored properly Product: kmail2 Version: 4.7 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rser...@gmail.com Version: 4.7 (using KDE 4.7.1) OS:Linux When entering the Message Tags tab in kmail2 configuration dialog, when changing the configuration of one specific tag, the configuration of the rest of tags is reset to a default, the only kept settings are keyboard shortcut and icon, but Font Color, Font, BG color are disabled and reset. However the one just edited is stored properly. Reproducible: Always Steps to Reproduce: - Go to the message tag dialog, change the settings of a tag, e.g., bg color, save. - Tag a message in the message list - Enter again, edit a setting of a different tag - Save - The last tagged message has, once again the default bg color instead of the new selected one. Actual Results: The message tag configuration is not stored, thus not properly applied Expected Results: Each tag with its particular configuration -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 René Serral rser...@gmail.com changed: What|Removed |Added CC||rser...@gmail.com --- Comment #11 from René Serral rserral gmail com 2011-09-08 08:24:39 --- I'm experiencing the same issue with KDE 4.7.1 and a calendar using akonadi-google resource -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 René Serral rser...@gmail.com changed: What|Removed |Added CC||rser...@gmail.com --- Comment #19 from René Serral rserral gmail com 2011-09-01 08:51:14 --- I experience the same behavior with KDE-PIM 4.7.0, I only have one addressbook using akonadi-google resource -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 259924] New: Crash at the end of automatic Akonadi migration from KDE 4.5
https://bugs.kde.org/show_bug.cgi?id=259924 Summary: Crash at the end of automatic Akonadi migration from KDE 4.5 Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: rkr...@gmx.net CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (0.1) KDE Platform Version: 4.5.85 (4.6 Beta2) Qt Version: 4.7.1 Operating System: Linux 2.6.34.7-0.5-desktop x86_64 Distribution: openSUSE 11.3 (x86_64) -- Information about the crash: After starting Kontact with KMail the migration tool was automatically launched, reporting a successful migration. Even before that report windows of the migration tool closes I get this crash. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f50bb914760 (LWP 22039))] Thread 2 (Thread 0x7f50a953d710 (LWP 22041)): #0 0x7f50b74886b3 in __poll (fds=value optimized out, nfds=value optimized out, timeout=value optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f50b5df3fd4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f50b5df4510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f50badbfae6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #4 0x7f50bad94262 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #5 0x7f50bad94475 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #6 0x7f50baca71a4 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7f50b9a25c43 in ?? () from /usr/lib64/libkimap.so.4 #8 0x7f50baca9a1e in ?? () from /usr/lib64/libQtCore.so.4 #9 0x7f50b6d4fa4f in start_thread (arg=0x7f50a953d710) at pthread_create.c:297 #10 0x7f50b749182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f50bb914760 (LWP 22039)): [KCrash Handler] #6 QSharedDataPointer (one=..., other=...) at /usr/include/QtCore/qshareddata.h:93 #7 assignEntityPrivate (one=..., other=...) at /usr/src/debug/kdepimlibs-4.5.85/akonadi/entity.cpp:49 #8 0x7f50bb3d4da4 in Akonadi::Entity::Entity (this=value optimized out, other=value optimized out) at /usr/src/debug/kdepimlibs-4.5.85/akonadi/entity.cpp:56 #9 0x00421a26 in _start () Possible duplicates by query: bug 258684, bug 258430, bug 253031, bug 250078. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 246847] cannot send smtp messages
https://bugs.kde.org/show_bug.cgi?id=246847 René Fritz r...@colorcube.de changed: What|Removed |Added CC||r...@colorcube.de --- Comment #2 from René Fritz rene colorcube de 2010-09-06 20:16:49 --- I have the same problem. I used beta 1 kubuntu lucid packages to convert mails. Now I used beta 3 maverik packages. Same behaviour. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 243843] New: Akonadi Resource crash on adding new calendar
https://bugs.kde.org/show_bug.cgi?id=243843 Summary: Akonadi Resource crash on adding new calendar Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: vkra...@kde.org ReportedBy: rser...@gmail.com CC: kdepim-bugs@kde.org Application: akonadi_kcal_resource (0.1) KDE Platform Version: 4.5.60 (KDE 4.5.60 (KDE 4.6 = 20100627)) (Compiled from sources) Qt Version: 4.7.0 Operating System: Linux 2.6.34-toi i686 Distribution: Debian GNU/Linux 5.0.5 (lenny) -- Information about the crash: I just updated to the last trunk version of kdesupport, kdelibs, kdebase and kdepimlibs. While using kdepim 4.4. After a system restart akonadi didn't start properly anymore without any changes on the configuration. It complained about not possible to alter table: DBUpdater: query error: ERROR: syntax error at or near CONVERT LINE 1: ALTER TABLE CollectionAttributeTable CONVERT TO CHARACTER SE... ^ QPSQL: Unable to create query Query was: ALTER TABLE CollectionAttributeTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE CollectionMimeTypeRelation CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE CollectionPimItemRelation CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE CollectionTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE FlagTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE MimeTypeTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE PartTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE PimItemFlagRelation CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE PimitemTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE ResourceTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; ALTER TABLE SchemaVersionTable CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; Target version was: 16 Mandatory: false Failed to commit transaction for database update I'm using posgresql backend. - What I was doing when the application crashed: Akonadi seems to work, but my calendar entries are all gone, hence I tried to reconfigure the calendar source by removing my previous calendar. When inserting the new one akonadi resource crashes all the time. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_kcal_resource), signal: Segmentation fault [KCrash Handler] #7 0xb7535794 in QBasicAtomicInt::ref (this=0xb0a48000) at /usr/include/qt4/QtCore/qatomic_i386.h:120 #8 0xb7535934 in QString (this=0xbfc34614, other=...) at /usr/include/qt4/QtCore/qstring.h:727 #9 0xb7534f6f in Akonadi::Entity::remoteId (this=0x8fb9654) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/entity.cpp:85 #10 0xb75894c4 in Akonadi::CollectionSync::Private::createRemoteNode (this=0x91c4908, col=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/collectionsync.cpp:148 #11 0xb75883da in Akonadi::CollectionSync::setRemoteCollections (this=0x8bb6c50, remoteCollections=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/collectionsync.cpp:551 #12 0xb75fafbe in Akonadi::ResourceBase::collectionsRetrieved (this=0x8b98248, collections=...) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/resourcebase.cpp:385 #13 0x080517f1 in KCalResource::retrieveCollections (this=0x8b98248) at /media/kdesvn/kde4svn/src/kdepim/runtime/resources/kcal/kcalresource.cpp:223 #14 0xb75fd242 in Akonadi::ResourceBase::qt_metacall (this=0x8b98248, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfc3498c) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/moc_resourcebase.cpp:111 #15 0x08055252 in KCalResource::qt_metacall (this=0x8b98248, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0xbfc3498c) at /media/kdesvn/kde4svn/build/kdepim/runtime/resources/kcal/kcalresource.moc:91 #16 0xb73742da in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb738384b in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb760135f in Akonadi::ResourceScheduler::executeFullSync (this=0x8ba6440) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/resourcescheduler_p.moc:124 #19 0xb75ff4b7 in Akonadi::ResourceScheduler::executeNext (this=0x8ba6440) at /media/kdesvn/kde4svn/src/kdepimlibs/akonadi/resourcescheduler.cpp:241 #20 0xb7601319 in Akonadi::ResourceScheduler::qt_metacall (this=0x8ba6440, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x92b19a8) at /media/kdesvn/kde4svn/build/kdepimlibs/akonadi/resourcescheduler_p.moc:113 #21 0xb73742da in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb737f6a6 in
[Bug 236286] New: Kontact crashing on KDE startup
https://bugs.kde.org/show_bug.cgi?id=236286 Summary: Kontact crashing on KDE startup Product: kontact Version: 4.4.3 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rser...@gmail.com Application: kontact (4.4.3) KDE Platform Version: 4.4.3 (KDE 4.4.3) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.33.3-tuxonice i686 Distribution: Debian GNU/Linux 5.0.4 (lenny) -- Information about the crash: When kontact is automatically loaded on system startup it always crashes. However, running it manually afterwards always succeeds. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #6 0xb7755424 in __kernel_vsyscall () #7 0xb489c8e0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb489fe15 in *__GI_abort () at abort.c:88 #9 0xb5611b64 in qt_message_output(QtMsgType, char const*) () from /usr/lib/libQtCore.so.4 #10 0xb5611d1a in ?? () from /usr/lib/libQtCore.so.4 #11 0xb5611e29 in qFatal(char const*, ...) () from /usr/lib/libQtCore.so.4 #12 0xb5611eb5 in qt_assert(char const*, char const*, int) () from /usr/lib/libQtCore.so.4 #13 0xb617036a in KDBusServiceStarter (this=0x8e18ae8) at /media/kdesvn/kde4svn/src/kdelibs/kio/kio/kdbusservicestarter.cpp:54 #14 0xb6e2ecdd in ServiceStarter (this=0x8e18ae8, pluginList=0x93d66b8) at /media/kdesvn/kde4svn/src/kdepim/kontact/src/mainwindow.cpp:91 #15 0xb6e2577d in MainWindow (this=0x93d6670, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /media/kdesvn/kde4svn/src/kdepim/kontact/src/mainwindow.cpp:136 #16 0x0804ac9b in KontactApp::newInstance (this=0xbfce46e4) at /media/kdesvn/kde4svn/src/kdepim/kontact/src/main.cpp:136 #17 0xb5d2fd87 in KUniqueApplicationAdaptor::newInstance (this=0x8cfac50, asn_id=..., args=...) at /media/kdesvn/kde4svn/src/kdelibs/kdeui/kernel/kuniqueapplication.cpp:454 #18 0xb5d2ffe1 in KUniqueApplicationAdaptor::qt_metacall (this=0x8cfac50, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfce2ca8) at /media/kdesvn/kde4svn/build/kdelibs/kdeui/kuniqueapplication_p.moc:81 #19 0xb5854d61 in ?? () from /usr/lib/libQtDBus.so.4 #20 0xb5855f3f in ?? () from /usr/lib/libQtDBus.so.4 #21 0xb58569e0 in ?? () from /usr/lib/libQtDBus.so.4 #22 0xb5856c7a in ?? () from /usr/lib/libQtDBus.so.4 #23 0xb572d0de in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #24 0xb571c3bb in QCoreApplication::event(QEvent*) () from /usr/lib/libQtCore.so.4 #25 0xb4c4e556 in QApplication::event(QEvent*) () from /usr/lib/libQtGui.so.4 #26 0xb4c49bec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #27 0xb4c5075e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #28 0xb5d2565c in KApplication::notify (this=0xbfce46e4, receiver=0xbfce46e4, event=0x9500330) at /media/kdesvn/kde4svn/src/kdelibs/kdeui/kernel/kapplication.cpp:302 #29 0xb571c8eb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #30 0xb571f2c3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #31 0xb571f42d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #32 0xb57487ff in ?? () from /usr/lib/libQtCore.so.4 #33 0xb3a2b2f5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #34 0xb3a2efd8 in ?? () from /lib/libglib-2.0.so.0 #35 0xb3a2f1b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #36 0xb57482f5 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #37 0xb4d08255 in ?? () from /usr/lib/libQtGui.so.4 #38 0xb571af09 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #39 0xb571b35a in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #40 0xb5dc2893 in KWallet::Wallet::openWallet (name=..., w=100663306, ot=KWallet::Wallet::Synchronous) at /media/kdesvn/kde4svn/src/kdelibs/kdeui/util/kwallet.cpp:260 #41 0xaf9cb24c in KMKernel::wallet (this=0x903d8c8) at /media/kdesvn/kde4svn/src/kdepim/kmail/kmkernel.cpp:2498 #42 0xaf94dd3a in KMail::NetworkAccount::readPassword (this=0x9254048) at /media/kdesvn/kde4svn/src/kdepim/kmail/networkaccount.cpp:338 #43 0xaf8ea456 in KMail::AccountManager::readPasswords (this=0x90b86a0) at /media/kdesvn/kde4svn/src/kdepim/kmail/accountmanager.cpp:438 #44 0xaf94be25 in KMail::NetworkAccount::passwd (this=0x9254048) at /media/kdesvn/kde4svn/src/kdepim/kmail/networkaccount.cpp:95 #45 0xaf952562 in KMail::ImapAccountBase::makeConnection (this=0x9254048) at /media/kdesvn/kde4svn/src/kdepim/kmail/imapaccountbase.cpp:306 #46 0xaf9623a0 in KMAcctImap::makeConnection (this=0x9254048) at
[Bug 222155] Akonadi crash when I start the session [qBadAlloc, QX11PixmapData::toImage, QPixmap, KPixmapCache, KIconLoader]
https://bugs.kde.org/show_bug.cgi?id=222155 --- Comment #12 from René Krell rkrell gmx net 2010-02-23 10:36:31 --- Another one: There isn't any longer reported this crash after updating Qt from 4.6.2 to 4.6.1+4.6.20100223 (latest patches). I'm not sure, whether this solves the potential problem, and whether it will not happen again, but obviously there is a change. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 228003] New: Akonadi crash announcecd on KDE login, but Akonadi is working
https://bugs.kde.org/show_bug.cgi?id=228003 Summary: Akonadi crash announcecd on KDE login, but Akonadi is working Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Mail Dispatcher Agent AssignedTo: cber...@gmail.com ReportedBy: rkr...@gmx.net CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_maildispatcher_agent (0.1) KDE Platform Version: 4.4.00 (KDE 4.4.0) release 2 Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-0.1-desktop x86_64 Distribution: openSUSE 11.2 (x86_64) -- Information about the crash: After login to KDE I was told that akonadi crashed with the appended backtrace. Akonadictrl told me after that, that Akonadi is running. A subsequent start of Kontact with all Akonadi resources worked without problems. -- Backtrace: Application: Akonadi Agent (akonadi_maildispatcher_agent), signal: Aborted [KCrash Handler] #5 0x7f153f5e14e5 in raise () from /lib64/libc.so.6 #6 0x7f153f5e29b0 in abort () from /lib64/libc.so.6 #7 0x7f153fbe7dc5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #8 0x7f153fbe61f6 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7f153fbe6223 in std::terminate() () from /usr/lib64/libstdc++.so.6 #10 0x7f153fbe631e in __cxa_throw () from /usr/lib64/libstdc++.so.6 #11 0x7f15410951e2 in qBadAlloc () at global/qglobal.cpp:2004 #12 0x7f153dae24ad in QX11PixmapData::toImage (this=0x7e5540) at image/qpixmap_x11.cpp:1494 #13 0x7f153dac9bc0 in QPixmap::toImage (this=0x7fffbdac59d0) at image/qpixmap.cpp:486 #14 0x7f154010cef3 in KPixmapCache::Private::writeData (this=0x735800, key=value optimized out, pix=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/util/kpixmapcache.cpp:1444 #15 0x7f154010dc9b in KPixmapCache::insert (this=0x73bd50, key=..., pix=...) at /usr/src/debug/kdelibs-4.4.0/kdeui/util/kpixmapcache.cpp:1410 #16 0x7f154010b604 in KIconLoader::loadIcon (this=0x63fc30, _name=value optimized out, group=value optimized out, size=64, state=value optimized out, overlays=..., path_store=0x0, canReturnNull=true) at /usr/src/debug/kdelibs-4.4.0/kdeui/icons/kiconloader.cpp:1005 #17 0x7f154010b344 in KIconLoader::loadIcon (this=0x63fc30, _name=value optimized out, group=value optimized out, size=64, state=value optimized out, overlays=..., path_store=0x0, canReturnNull=false) at /usr/src/debug/kdelibs-4.4.0/kdeui/icons/kiconloader.cpp:1130 #18 0x7f154010c88d in KIconEngine::pixmap (this=value optimized out, size=..., mode=value optimized out, state=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/icons/kiconengine.cpp:119 #19 0x7f153da996c5 in QIcon::pixmap (this=value optimized out, size=..., mode=4294967295, state=10) at image/qicon.cpp:669 #20 0x7f153da85dd4 in QWidgetPrivate::setWindowIcon_sys (this=value optimized out, forceReset=value optimized out) at kernel/qwidget_x11.cpp:1458 #21 0x7f153da40418 in QWidget::create (this=0x745940, window=0, initializeWindow=value optimized out, destroyOldWindow=value optimized out) at kernel/qwidget.cpp:1351 #22 0x7f153da7 in setupOwner () at kernel/qclipboard_x11.cpp:131 #23 0x7f153da781a1 in QClipboard::QClipboard (this=0x7453e0, parent=0x10c) at kernel/qclipboard_x11.cpp:458 #24 0x7f153d9e9047 in QApplication::clipboard () at kernel/qapplication.cpp:3090 #25 0x7f1540014f5e in KClipboardSynchronizer::Private::setupSignals (this=0xebd) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kclipboard.cpp:94 #26 0x7f1540015262 in KClipboardSynchronizer::KClipboardSynchronizer (this=0x745210, parent=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kclipboard.cpp:84 #27 0x7f1540015410 in operator- (this=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kclipboard.cpp:73 #28 operator KClipboardSynchronizer* (this=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kclipboard.cpp:73 #29 KClipboardSynchronizer::self (this=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kclipboard.cpp:74 #30 0x7f154011ce71 in KApplicationPrivate::init (this=0x732d60, GUIenabled=true) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:463 #31 0x7f154011e809 in KApplication::KApplication (this=0x7fffbdac6d50, GUIenabled=value optimized out) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:343 #32 0x00408df7 in _start () Possible duplicates by query: bug 226625, bug 225168, bug 224295, bug 222155. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org
[Bug 183393] Lost tags in KMail messages
https://bugs.kde.org/show_bug.cgi?id=183393 --- Comment #2 from René Serral rserral gmail com 2010-02-06 10:09:29 --- It still happens in my system with 4.3.5. If you tag a message i.e. as Business in your IMAP inbox, and afterwards you move it to another imap folder the tag disappears. While if you move it to you local inbox then it is still there. (however if you move it back to your inbox in the imap folder it disappears again). Hope this helps René On Saturday 06 February 2010 01:12:03 Björn Ruberg wrote: https://bugs.kde.org/show_bug.cgi?id=183393 Björn Ruberg bjo...@ruberg-wegener.de changed: What|Removed |Added --- - CC||bjo...@ruberg-wegener.de --- Comment #1 from Björn Ruberg bjoern ruberg-wegener de 2010-02-06 01:12:00 --- What do you mean with tags? Do you mean states like important maybe? It so, I cannot reproduce the problem in KDE 4.3.5 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 222170] kmail freezes when displaying mails where my address is in the from header
https://bugs.kde.org/show_bug.cgi?id=222170 René Krell rkr...@gmx.net changed: What|Removed |Added CC||rkr...@gmx.net --- Comment #2 from René Krell rkrell gmx net 2010-01-11 19:22:50 --- akonadictl status shows for me: Akonadi Control: running Akonadi Server: running Akonadi Server Search Support: available (backend: Virtuoso) I'm at KDE 4.4 RC1 now. Sending a single small mail takes minimum 20 - 30 seconds. My hardware: Processor (CPU): Intel(R) Pentium(R) D CPU 3.00GHz Speed: 3,000.00 MHz Cores: 2 Total memory (RAM): 1.8 GiB This is not a hardware I would expect such a delay from. In KDE 4.3.X this problem didn't exist. I have done a straight upgrade on them using the OpenSUSE 11.2 KDE4 Desktop Factory packages. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 221791] New: Knotes crash on deleting some old notes [KDialog::setButtons, QMetaObject::activate, QAction::triggered]
https://bugs.kde.org/show_bug.cgi?id=221791 Summary: Knotes crash on deleting some old notes [KDialog::setButtons, QMetaObject::activate, QAction::triggered] Product: kontact Version: 4.4 pre Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Application: kontact (4.4 pre) KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) release 203 Qt Version: 4.6.1 Operating System: Linux 2.6.31.8-0.1-desktop x86_64 Distribution: openSUSE 11.2 (x86_64) -- Information about the crash: Deleting some old notes from the knotes plugin Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f509fdca7f0 (LWP 3029))] Thread 2 (Thread 0x7f5082e50910 (LWP 6646)): #0 0x7f509cf31712 in select () from /lib64/libc.so.6 #1 0x7f509e282bc3 in QProcessManager::run (this=0x7f509e5b9f40) at io/qprocess_unix.cpp:245 #2 0x7f509e1b3355 in QThreadPrivate::start (arg=0x7f509e5b9f40) at thread/qthread_unix.cpp:248 #3 0x7f5098c4d65d in start_thread (arg=value optimized out) at pthread_create.c:297 #4 0x7f509cf3814d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7f509fdca7f0 (LWP 3029)): [KCrash Handler] #5 0x7f5088b4ca47 in KDialog::setButtons(QFlagsKDialog::ButtonCode) () from /usr/lib64/kde4/kontact_knotesplugin.so #6 0x7f5088b5b629 in ?? () from /usr/lib64/kde4/kontact_knotesplugin.so #7 0x7f5088b5c590 in ?? () from /usr/lib64/kde4/kontact_knotesplugin.so #8 0x7f509e2b894f in QMetaObject::activate (sender=0x19d8860, m=value optimized out, local_signal_index=value optimized out, argv=0x19cda00) at kernel/qobject.cpp:3267 #9 0x7f509d684722 in QAction::triggered (this=0x0, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #10 0x7f509d68679b in QAction::activate (this=0x19d8860, event=value optimized out) at kernel/qaction.cpp:1251 #11 0x7f509daa4e2d in QMenuPrivate::activateCausedStack (this=value optimized out, causedStack=..., action=0x19d8860, action_e=Trigger, self=true) at widgets/qmenu.cpp:1011 #12 0x7f509daaa99a in QMenuPrivate::activateAction (this=0x2076dd0, action=0x19d8860, action_e=Trigger, self=value optimized out) at widgets/qmenu.cpp:1103 #13 0x7f509ed41f8e in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libkdeui.so.5 #14 0x7f509d6e0a62 in QWidget::event (this=0x19cd950, event=0x7fff61ba3240) at kernel/qwidget.cpp:7978 #15 0x7f509daacb5b in QMenu::event (this=0x19cd950, e=0x7fff61ba3240) at widgets/qmenu.cpp:2415 #16 0x7f509d68a77c in QApplicationPrivate::notify_helper (this=0x652060, receiver=0x19cd950, e=0x7fff61ba3240) at kernel/qapplication.cpp:4297 #17 0x7f509d69153b in QApplication::notify (this=0x7fff61ba3f50, receiver=0x19cd950, e=0x7fff61ba3240) at kernel/qapplication.cpp:3862 #18 0x7f509ec65a76 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #19 0x7f509e2a5b6c in QCoreApplication::notifyInternal (this=0x7fff61ba3f50, receiver=0x19cd950, event=0x7fff61ba3240) at kernel/qcoreapplication.cpp:704 #20 0x7f509d690716 in sendEvent (event=value optimized out, receiver=value optimized out) at ../../src/corelib/kernel/qcoreapplication.h:215 #21 QApplicationPrivate::sendMouseEvent (event=value optimized out, receiver=value optimized out) at kernel/qapplication.cpp:2962 #22 0x7f509d710085 in QETWidget::translateMouseEvent (this=0x19cd950, event=value optimized out) at kernel/qapplication_x11.cpp:4302 #23 0x7f509d70e95a in QApplication::x11ProcessEvent (this=value optimized out, event=0x7fff61ba3b60) at kernel/qapplication_x11.cpp:3501 #24 0x7f509d738b52 in x11EventSourceDispatch (s=0x655480, callback=value optimized out, user_data=value optimized out) at kernel/qguieventdispatcher_glib.cpp:146 #25 0x7f5095af2dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7f5095af67a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7f5095af68d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7f509e2cf0f3 in QEventDispatcherGlib::processEvents (this=0x610970, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:412 #29 0x7f509d73873e in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #30 0x7f509e2a4482 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #31 0x7f509e2a485c in QEventLoop::exec (this=0x7fff61ba3e90, flags=) at kernel/qeventloop.cpp:201 #32 0x7f509e2a85ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #33 0x00403ed7 in _start () Reported using DrKonqi --
[Bug 185544] closing a 2nd instance crashes kontact with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=185544 --- Comment #34 from René Krell rkrell gmx net 2010-01-07 10:12:21 --- Problem confirmed for KDE 4.3.85, kmail 1.13.0. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 221546] New: Kontact crashes after starting two instances by mistake and closing them
https://bugs.kde.org/show_bug.cgi?id=221546 Summary: Kontact crashes after starting two instances by mistake and closing them Product: kontact Version: 4.4 pre Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 4.4 pre (using Devel) Compiler: gcc OS:Linux Installed from:Compiled sources For some unknown reason, the last few weeks I get always two instances of Kontact launched after login to KDE 4.4. Today I chose Start Kontact on the appearing messagebox that informs about the double instance. So I got two Kontact instances running. After closing them both I get the following crash: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fc6bf5e07f0 (LWP 13181))] Thread 2 (Thread 0x7fc6a0d6f910 (LWP 13399)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220 #1 0x7fc6bd9ca272 in wait (time=value optimized out, this=value optimized out) at thread/qwaitcondition_unix.cpp:85 #2 QWaitCondition::wait (time=value optimized out, this=value optimized out) at thread/qwaitcondition_unix.cpp:159 #3 0x7fc6bd9bf6d9 in QThreadPoolThread::run (this=0x1b67660) at concurrent/qthreadpool.cpp:140 #4 0x7fc6bd9c9355 in QThreadPrivate::start (arg=0x1b67660) at thread/qthread_unix.cpp:248 #5 0x7fc6b846365d in start_thread (arg=value optimized out) at pthread_create.c:297 #6 0x7fc6bc74e14d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 1 (Thread 0x7fc6bf5e07f0 (LWP 13181)): [KCrash Handler] #5 0x7fc6a73371e1 in KMMainWidget::initializeFilterActions() () from /usr/lib64/libkmailprivate.so.4 #6 0x7fc6a7908fe1 in ?? () from /usr/lib64/kde4/kmailpart.so #7 0x7fc6bdacb8e4 in QObject::event (this=0x944140, e=0x7fffb7665410) at kernel/qobject.cpp:1271 #8 0x7fc6bcea077c in QApplicationPrivate::notify_helper (this=0x63a610, receiver=0x944140, e=0x7fffb7665410) at kernel/qapplication.cpp:4297 #9 0x7fc6bcea6d5b in QApplication::notify (this=0x7fffb76662c0, receiver=0x944140, e=0x7fffb7665410) at kernel/qapplication.cpp:4180 #10 0x7fc6be47ba76 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #11 0x7fc6bdabbb6c in QCoreApplication::notifyInternal (this=0x7fffb76662c0, receiver=0x944140, event=0x7fffb7665410) at kernel/qcoreapplication.cpp:704 #12 0x7fc6bc45cc97 in KParts::MainWindow::createGUI(KParts::Part*) () from /usr/lib64/libkparts.so.4 #13 0x7fc6bf1fc97c in Kontact::MainWindow::~MainWindow() () from /usr/lib64/libkontactprivate.so.4 #14 0x7fc6bdacb8ad in QObject::event (this=0x7d2810, e=0xf73a00) at kernel/qobject.cpp:1223 #15 0x7fc6bcef60bf in QWidget::event (this=0x7d2810, event=0xf73a00) at kernel/qwidget.cpp:8435 #16 0x7fc6bd29863b in QMainWindow::event (this=0x7d2810, event=0xf73a00) at widgets/qmainwindow.cpp:1435 #17 0x7fc6be592a83 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libkdeui.so.5 #18 0x7fc6bcea077c in QApplicationPrivate::notify_helper (this=0x63a610, receiver=0x7d2810, e=0xf73a00) at kernel/qapplication.cpp:4297 #19 0x7fc6bcea6d5b in QApplication::notify (this=0x7fffb76662c0, receiver=0x7d2810, e=0xf73a00) at kernel/qapplication.cpp:4180 #20 0x7fc6be47ba76 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x7fc6bdabbb6c in QCoreApplication::notifyInternal (this=0x7fffb76662c0, receiver=0x7d2810, event=0xf73a00) at kernel/qcoreapplication.cpp:704 #22 0x7fc6bdabe2e7 in sendEvent (event=value optimized out, receiver=value optimized out) at kernel/qcoreapplication.h:215 #23 QCoreApplicationPrivate::sendPostedEvents (event=value optimized out, receiver=value optimized out) at kernel/qcoreapplication.cpp:1345 #24 0x7fc6bdae55b3 in sendPostedEvents () at kernel/qcoreapplication.h:220 #25 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #26 0x7fc6b5308dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7fc6b530c7a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x7fc6b530c8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7fc6bdae50f3 in QEventDispatcherGlib::processEvents (this=0x610970, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:412 #30 0x7fc6bcf4e73e in QGuiEventDispatcherGlib::processEvents (this=0x7fffb7664a40, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x7fc6bdaba482 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #32 0x7fc6bdaba85c in QEventLoop::exec (this=0x7fffb7666200, flags=) at kernel/qeventloop.cpp:201 #33
[Bug 221546] Kontact crashes after starting two instances by mistake and closing them
https://bugs.kde.org/show_bug.cgi?id=221546 --- Comment #1 from René Krell rkrell gmx net 2010-01-06 17:18:35 --- Sorry, next time with kmail debuginfo, I already added them, but cannot reproduce it another time. Maybe you already know the problem. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 220380] New: Copy and paste contact from addressbook to composer crashes kmail
https://bugs.kde.org/show_bug.cgi?id=220380 Summary: Copy and paste contact from addressbook to composer crashes kmail Product: kmail Version: 1.13.0 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 1.13.0 (using 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) release 203, KDE:KDE4:Factory:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (x86_64) release 2.6.31.5-0.1-desktop I tried to copy a contact from addressbook and paste it into the composer window. After confirming the popup menu to add it as attachment kmail crashes. Unfortunately without a useful backtrace, hopefully you can easily reproduce it. Thanks. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 220380] Copy and paste contact from addressbook to composer crashes kmail
https://bugs.kde.org/show_bug.cgi?id=220380 --- Comment #1 from René Krell rkrell gmx net 2009-12-28 12:24:38 --- Used Qt4 4.6.0+4.6.20091222 (patched) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 205356] Kontact unresponsive/hanging on IMAP fetching in kmail
https://bugs.kde.org/show_bug.cgi?id=205356 --- Comment #2 from René Krell rkrell gmx net 2009-12-28 12:29:28 --- In version 1.13.0 (KDE 4.4 Beta2) the behaviour is slightly better. KMail is far more responsive during IMAP fetching and I'm thinking about to mark this as working for me. Commenters, please tell your opinion about that. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 219687] New: Sending a message takes a lot of time and resources eaten by Nepomuk/Virtuoso
https://bugs.kde.org/show_bug.cgi?id=219687 Summary: Sending a message takes a lot of time and resources eaten by Nepomuk/Virtuoso Product: kmail Version: 1.13.0 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 1.13.0 (using 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) release 203, KDE:KDE4:Factory:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (x86_64) release 2.6.31.5-0.1-desktop Each time I Press Send in the composer window sending a message takes about 1 minute. The composer elements gets grayed out after about half of this time, but are immediately inaccessible (as it should be, of course). During those ages of sending a message the CPU is eaten by the nepomukserver and virtuoso processes. If the system is under a wanted high load sending a message takes more time than normally. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 219687] Sending a message takes a lot of time and resources eaten by Nepomuk/Virtuoso
https://bugs.kde.org/show_bug.cgi?id=219687 --- Comment #1 from René Krell rkrell gmx net 2009-12-22 15:39:12 --- This happens also on short text format messages without attachments. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 212304] New: No background color when tagging messages
https://bugs.kde.org/show_bug.cgi?id=212304 Summary: No background color when tagging messages Product: kmail Version: 1.12.90 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rser...@gmail.com Version: 1.12.90 (using Devel) OS:Linux Installed from:Compiled sources When creating a Tag in the Appearance - Message Tags option, if you specify a background color for the tag it is not applied to the message list. When I go back to the menu, the option has the default values (white color without the check mark). I tried several times to no avail. Just in case: I'm using a regular IMAP account. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 209187] New: Composer: Focus jumps in auto-completion drilldown when matching results from LDAP search are added later
https://bugs.kde.org/show_bug.cgi?id=209187 Summary: Composer: Focus jumps in auto-completion drilldown when matching results from LDAP search are added later Product: kmail Version: 1.12.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 1.12.2 (using 4.3.1 (KDE 4.3.1) release 168, KDE:KDE4:Factory:Desktop / openSUSE_Factory) Compiler: gcc OS:Linux (i686) release 2.6.31-10-desktop In composer, when I type addresses in the To:/CC:/Bcc: edit fields by typing the first letters of an address quickly and the drilldown with auto-completed addresses opens, the currently marked address from the auto-completion changes when additional matching results from an LDAP search come in. If I mark an entry and don't press enter to choose it before the LDAP matches come in occasionally, that entry is shift one or more positions towards the end, while the marking changes too (which is bad). For instance, assume typing ab in the To: field gives me three addresses in the offered dropdown: - a...@domain.com - a...@domain.com chosen mark - a...@domain.com I choose the second one, a...@domain.com with the up/down keys. While that, additional entries are searched in background from LDAP. Now, assume there is an additional matching entry from the LDAP search: - a...@domain.com which is inserted at the beginning of the drilldown box. Thus, the drilldown list is now: - a...@domain.com - a...@domain.com new mark - a...@domain.com - a...@domain.com Currently, the original marking of a...@domain.com gets lost and the new second entry, a...@domain.com, is marked instead, which is confusing. I would expect the entry I marked already to stay marked in that case, and the mark is shifted together with the entry. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 180741] crash in kmail (typeinfo name for, KMReaderWin::parseMsg)
https://bugs.kde.org/show_bug.cgi?id=180741 René Krell rkr...@gmx.net changed: What|Removed |Added CC|rkr...@gmx.net | -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 205989] New: Message filter don't apply immediately, but on opening IMAP Inbox
https://bugs.kde.org/show_bug.cgi?id=205989 Summary: Message filter don't apply immediately, but on opening IMAP Inbox Product: kmail Version: 1.12.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 1.12.1 (using 4.3.1 (KDE 4.3.1) release 163, KDE:KDE4:Factory:Desktop / openSUSE_Factory) Compiler: gcc OS:Linux (i686) release 2.6.31-rc7-4-desktop In case the IMAP Inbox is not actually open, message filtering doesn't apply immediately, as expected, but as soon as I open the Inbox. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 195190] KMail composer ignores initial dictionary on default identity after opening
https://bugs.kde.org/show_bug.cgi?id=195190 --- Comment #2 from René Krell rkrell gmx net 2009-06-24 10:08:25 --- Important detail: The problem appears only on REPLYING, not on composing a new mail. @Frank: Can you retry this, too, please? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 195190] New: KMail composer ignores initial dictionary on default identity after opening
https://bugs.kde.org/show_bug.cgi?id=195190 Summary: KMail composer ignores initial dictionary on default identity after opening Product: kmail Version: 1.11.90 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rkr...@gmx.net Version: 1.11.90 (using 4.2.88 (KDE 4.2.88 (KDE 4.3 = 20090527)) release 135, KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS:Linux (i686) release 2.6.27.21-0.1-pae My KDE and system is set to english language settings. In the KMail settings, I have two identies. One of them is default and has a changed Dictionary in its settings: Edit identity - Tab Advanced - Dictionary: Czech. If I open the composer with the default identity and the overloaded dictionary, the dictionary is ignored. In composer, I have to explicitly click on the Identity dropdown field and make an action there (either only open it without changing the current value or changing it to another identity and back) for getting the right dictionary activated, instead. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 163609] Wordwrap breaks up URLs with dashes ('-')
https://bugs.kde.org/show_bug.cgi?id=163609 --- Comment #13 from René rkrell gmx net 2009-03-17 10:15:22 --- Update: The problem still exists in version 1.11.1 (KDE 4.2.1 / openSUSE_11.1 / x86_64) using Qt 4.5. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 163609] Wordwrap breaks up URLs with dashes ('-')
http://bugs.kde.org/show_bug.cgi?id=163609 --- Comment #12 from René rkrell gmx net 2009-02-02 10:16:17 --- (In reply to comment #10) Hi René, thanks for looking into this. Do you happen to know if there are plans to improve the Qt word wrapping in a future version? Should we file a bug/feature whish for Qt? Or do you think it is better to add some kind of wrapper around the Qt word-wrapping which handles cases like this? Hi Gerd, I do not have any idea what's the best address for this issue, I'm not familar with neither KDE nor Qt programming and leave the decision on experts. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 163609] Wordwrap breaks up URLs with dashes ('-')
http://bugs.kde.org/show_bug.cgi?id=163609 --- Comment #8 from René rkrell gmx net 2009-01-12 15:25:06 --- Yes, it is still there for 4.1.87 (upcoming 4.2), too. Long URLs with dashes are broken as normal text when having Wordwrap on, Qt word wrapping doesn't recognize them in the composer text. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- 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
