[kmail2] [Bug 326672] selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 Arne Babenhauserheide changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Arne Babenhauserheide --- I no longer see this. Thank you for curating the bugs! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 342600] gnupg: Answer to encrypted mail should by default be encrypted
https://bugs.kde.org/show_bug.cgi?id=342600 --- Comment #2 from Arne Babenhauserheide <arne_...@web.de> --- I still didn’t manage to get all of KDE 5 to build, so I cannot check that yet (I’ve been working for month to fix cruft which accumulated on my system, but I rarely have enough uninterrupted computer time to let large re-emerges finish). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 --- Comment #8 from Arne Babenhauserheide <arne_...@web.de> --- (In reply to Sandro Knauß from comment #7) > Please - still awnser my question: Are the recipients are hidden in the > mail? This is a feature of gpg and than gpg has to test every private key ( > in worst case scenario), because I can be that only the last key is the one > that decrypts the email. If gpg can see the keyIds it should only ask for > these keys to enter the passphrase. There are hidden recipients, yes. That might explain the issue… Sorry for being so slow to answer - and thank you for persisting! A possibility to improve this might be to first try the key for the email address with which I received the email. I cannot currently test this with a kmail based on kde5, because akonadi currently does not work at all for me (fails to start and the error logs says that all old accounts are missing). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Arne Babenhauserheide <arne_...@web.de> changed: What|Removed |Added CC||arne_...@web.de --- Comment #42 from Arne Babenhauserheide <arne_...@web.de> --- Hi Daniel, Thank you very much! I only now discovered the error message after wondering for 3 months why I got no updates, and thanks to you searching for the solution found the best answer: “fixed two weeks ago, will be included in the next release”. Best wishes, Arne -- You are receiving this mail because: You are the assignee for the bug. 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
[kmail2] [Bug 342599] I have to select an address book for a new contact even though I only have a single address book
https://bugs.kde.org/show_bug.cgi?id=342599 --- Comment #5 from Arne Babenhauserheide arne_...@web.de --- no probs - I’m glad that you still have it on your plan! -- 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 342599] I have to select an address book for a new contact even though I only have a single address book
https://bugs.kde.org/show_bug.cgi?id=342599 --- Comment #2 from Arne Babenhauserheide arne_...@web.de --- (In reply to Laurent Montel from comment #1) Indeed it will be better. I don't know if it's possible I will investigate. Thank you! -- 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 342600] New: gnupg: Answer to encrypted mail should by default be encrypted
https://bugs.kde.org/show_bug.cgi?id=342600 Bug ID: 342600 Summary: gnupg: Answer to encrypted mail should by default be encrypted Product: kmail2 Version: 4.14.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de I just answered an encrypted email. KMail asked me ”do you want to encrypt+sign or only sign”. I clicked “only sign”. This already hit me for the third time, now, and if it happened in the wrong moment, it could get someone into grave danger (spilling potentially sensitive private information with the quoted answer). In the KMail preferences-security-send message, I ticked all boxes (for me the most important reads „Nachrichten möglichst automatisch verschlüsseln“ ← something like try to encrypt automatically whenever possible). Wish: When answering to an encrypted message, KMail should automatically select “encrypt message”. And not ask me about that. Reproducible: Always -- 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 342599] New: I have to select an address book for a new contact even though I only have a single address book
https://bugs.kde.org/show_bug.cgi?id=342599 Bug ID: 342599 Summary: I have to select an address book for a new contact even though I only have a single address book Product: kmail2 Version: 4.14.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de Whenever I add a new contact, KMail requires me to select the address book. But I only have one address book, so that additional click conveys no information at all. Wish: If I only have one single address book, automatically use it to store my contact (and don’t ask me about it). Reproducible: Always -- 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 335854] missing option: always sign
https://bugs.kde.org/show_bug.cgi?id=335854 --- Comment #3 from Arne Babenhauserheide arne_...@web.de --- It works - thank you! It just was an annoyance, because my setting got lost and I had to reenable it (and first find out where to enable it). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 335854] New: missing option: always sign
https://bugs.kde.org/show_bug.cgi?id=335854 Bug ID: 335854 Summary: missing option: always sign Classification: Unclassified Product: kmail2 Version: 4.13.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de Since a few weeks, KMail does not GPG sign automatically anymore and I did not find the option for that anymore. Can I find it somewhere else? Signing automatically is my basic precaution and I really need it. Reproducible: Always -- 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 331870] New: kmail creates thousands of empty messages in the maildir
https://bugs.kde.org/show_bug.cgi?id=331870 Bug ID: 331870 Summary: kmail creates thousands of empty messages in the maildir Classification: Unclassified Product: kmail2 Version: 4.12.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de I have a setup where two computers update the maildir asynchronously and merge the changes via DVCS. For a few weeks now kmail (or akonadi) has been creating thousands of empty messages per day and created error messages saying that some emails could not be deleted. The new messages are named something like lists-and-forums/new/1393578315.R355.fluss (fluss is my hostname, but not the hostname of the computer which actually fetches the mails. the number after R has gone up to 997, but can also be 5. Many of the messages only differ in the number after the R - and they are empty) I guess that it can happen that some mail gets moved by one computer from maildir/new to maildir/cur while the other computer still sees it in maildir/new, giving me a clash in maildir/new. Reproducible: Always -- 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 331870] kmail creates thousands of empty messages in the maildir
https://bugs.kde.org/show_bug.cgi?id=331870 --- Comment #1 from Arne Babenhauserheide arne_...@web.de --- I’m currently killing all those empty messages with cd .local/share/mail for i in */*/*; do if ! grep -q @ $i; then echo XXX $i ; rm $i; fi; done -- 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 209319] GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management)
https://bugs.kde.org/show_bug.cgi?id=209319 --- Comment #6 from Arne Babenhauserheide arne_...@web.de --- At Sat, 04 Jan 2014 20:24:53 +0100, Arne Babenhauserheide wrote: At Sat, 04 Jan 2014 10:42:20 +, Hauke Laging wrote: In other words: If I get 100 emails from you then I get 100 copies of your certificate, making the search for emails with an attachment completely useless? Are you serious about that, do you want to get rid of your friends...? This is a non-issue for me: I also sign all email I send (attaches a *.asc file), so another attachment does not affect the search for mails with attachments. The lternative is an inline-signature - which might actually get some people to stop reading my mails. It would be nice, if most mail clients would show signatures differently than regular attachments, but for that to become a reality, more people need to sign their emails. The only problem I see is the possibly large size of the keys with all their signatures. And this could be resolved by simply keeping a list of people whio already received the current version of my key. Then you would not get 100 copies of my key but rather 3 or 4: Only those where the signatures changed from the last time you got my key. Best wishes, Arne -- 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 327986] when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 --- Comment #5 from Arne Babenhauserheide arne_...@web.de --- At Sat, 04 Jan 2014 08:27:02 +, Hauke Laging wrote: When I now click on one of my sent mails (or receive one of the mails - I always BCC myself) I have to enter multiple passwords: at least one for each key. Are that more than two keys and are you sure that you are asked the passphrase for different keys (check the pinentry message!)? Yes, I checked that multiple times. Are you sure this is different from the bug you reported two weeks earlier? There are two issues: Being asked for different keys and being ask twice for the same. I am not 100% sure that I did not miss a different key ID in the earlier bug, though I think it was the same (I cannot test right now: I'll only be able to access my KDE machine again in a few days). Best wishes, Arne -- 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 209319] GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management)
https://bugs.kde.org/show_bug.cgi?id=209319 --- Comment #5 from Arne Babenhauserheide arne_...@web.de --- At Sat, 04 Jan 2014 10:42:20 +, Hauke Laging wrote: In other words: If I get 100 emails from you then I get 100 copies of your certificate, making the search for emails with an attachment completely useless? Are you serious about that, do you want to get rid of your friends...? This is a non-issue for me: I also sign all email I send (attaches a *.asc file), so another attachment does not affect the search for mails with attachments. The lternative is an inline-signature - which might actually get some people to stop reading my mails. It would be nice, if most mail clients would show signatures differently than regular attachments, but for that to become a reality, more people need to sign their emails. The only problem I see is the possibly large size of the keys with all their signatures. And you are aware that only the key owner should change public versions of his certificate? Maybe he doesn't want your certification to be seen on his key. Of course, you can avoid this problem with some above average crypto knowledge... You could just encrypt the recipients keys to the recipients automatically. Then they can decide whether they want to spread your signature. Note, though, that every signature is effectively public except if both participants already have crypto-knowledge. The others keys could be stripped, so they only contain my signature (reducing the size of those keys). Along with the option to automatically import any attached GnuPG key, that would open the possiblity of using GnuPG without the need for central keyservers: If I sign a key, its owner will automatically get the updated version once he gets an email from me. Why not act like the rest of the world and send the certificate to the key owner immediately after creating it? 99% of the users don't care about this problem. The 1% can send you a mail and ask for the others' certificates. Because that currently does not work. How many people actually use GnuPG? I'd be happy to see another solution, though. The problem you mention does exist but has to be solved at another layer. This will probably be done by moving the responsibility for keyservers to the mail server owner (who knows that you send the mail anyway). Will the mail-servers I currently use support this? I fear that without legislative action, this will only increase the incompatibility problems - because the public does not know crypto. What I wish for is a seamless GnuPG experience: Setup the key once, the maybe say yes, I want to include this signature from time to time and otherwise just get encrypted email wherever both participants have GnuPG - starting at least from the first *answer*. An advantage here is, that I am not dependent on the mail provider to supply the feature (there are far less mail-clients that mail-providers) and that there is no need for a public list of existing keys. Best wishes, Arne -- 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 327986] New: when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password
https://bugs.kde.org/show_bug.cgi?id=327986 Bug ID: 327986 Summary: when I GnuPG encrypt to several receivers and I have more than one of the receiving keys myself, I am asked multiple times for my password Classification: Unclassified Product: kmail2 Version: 4.11.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de I have multiple GnuPG keys and I regularly encrypt to all of them in addition to other receivers. When I now click on one of my sent mails (or receive one of the mails - I always BCC myself) I have to enter multiple passwords: at least one for each key. Instead i would expect that if one of the keys succeeds in decrypting the message, the others should not be queried (so I should only have to enter the password for a single key successfully). (it took me quite some time to track down why I have to enter my password twice, but I *think* that this is the reason) Reproducible: Always -- 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 326672] selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 --- Comment #6 from Arne Babenhauserheide arne_...@web.de --- Thank you! I can test the fix once 4.11.4 made its way into Gentoo testing. -- 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 327357] New: Why do I have to enter the GnuPG key password twice when decrypting?
https://bugs.kde.org/show_bug.cgi?id=327357 Bug ID: 327357 Summary: Why do I have to enter the GnuPG key password twice when decrypting? Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de When decrypting a message in KMail, I am asked twice to enter the password, but I do not see why (and it makes me wary - does it decrypt for two different services, only one under my control?). Reproducible: Always Steps to Reproduce: 1. click on encrypted message 2. 3. Actual Results: message shows as encrypted. I am asked twice to enter my gnupg password. Expected Results: message shows as encrypted. I am asked once to enter my gnupg password or I get information why I am asked twice. -- 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 327357] Why do I have to enter the GnuPG key password twice when decrypting?
https://bugs.kde.org/show_bug.cgi?id=327357 --- Comment #1 from Arne Babenhauserheide arne_...@web.de --- Steps to Reproduce (additional info): 1. click on encrypted message *in the list of messages* 2. 3. -- 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 326672] selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 --- Comment #4 from Arne Babenhauserheide arne_...@web.de --- Created attachment 83145 -- https://bugs.kde.org/attachment.cgi?id=83145action=edit kmail-encrypt-all-crash-backtrace.txt Backtrace from the KMail Crash (thank you for the info how to create it!) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 326672] New: selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 Bug ID: 326672 Summary: selecting encrypt all in the unencrypted warning does not work and causes a crash Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de see the steps to reproduce and the result: Reproducible: Didn't try Steps to Reproduce: 1. Set KMail to warn on sending unencrypted mail (maybe also to always sign - that’s my setting) 2. Write a mail, try to send it unencrypted (in my case signed) 3. In the unencrypted-warning click “encrypt all” Actual Results: The key selection dialog shows the receiver keys (mine and the recipients) but not *my key* at the top (as it does in the regular encryption key selection). Then a message pops up, telling me that I do not encrypt to myself, so I won’t be able to read the message (that’s wrong: my key is in the list of encryption keys - I *guess* that the message box does not get told what is my key). When I tell it to encrypt anyway, KMail dies. Expected Results: After clicking “encrypt all”, it should encrypt as usual. -- 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 326672] selecting encrypt all in the unencrypted warning does not work and causes a crash
https://bugs.kde.org/show_bug.cgi?id=326672 --- Comment #2 from Arne Babenhauserheide arne_...@web.de --- Dr. Konqui did not appear (I just reproduced it). On the shell it prints this: *** KMail got signal 11 (Exiting) kmail2(7351) KMKernel::dumpDeadLetters: Danger, using an event loop, this should no longer be happening! `gdb kmail` does not give me a backtrace, either. -- 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
[kleopatra] [Bug 325563] Send key via E-Mail (menu-entry)
https://bugs.kde.org/show_bug.cgi?id=325563 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de -- 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
[kleopatra] [Bug 325563] New: Send key via E-Mail (menu-entry)
https://bugs.kde.org/show_bug.cgi?id=325563 Bug ID: 325563 Summary: Send key via E-Mail (menu-entry) Classification: Unclassified Product: kleopatra Version: 2.1.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de CC: m...@kde.org Hi, It would be nice, if Kleopatra would contain an option to send a mail via E-Mail to support schemes, in which we send the signed key encrypted to the sender to ensure that he actually controls the private key. Best wishes, Arne Reproducible: Always -- 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
[kleopatra] [Bug 317019] New: Show photos for already Trusted keys
https://bugs.kde.org/show_bug.cgi?id=317019 Bug ID: 317019 Summary: Show photos for already Trusted keys Classification: Unclassified Product: kleopatra Version: 2.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: arne_...@web.de CC: m...@kde.org I think it would be nice to support showing photos for trusted keys, because that would offer an additional visual cue that the key is safe. This does not invalidate the argument that keys with images are bigger, but it counters the argument, that images give a false sense of security: If the key is trusted, images cannot give an additional false sense of security, because the key is already regarded as secure. Reproducible: Always -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #13 from Arne Babenhauserheide arne_...@web.de --- Note: The embedded emacs still has issues, but these seem to come from emacs, not KMail: http://lists.gnu.org/archive/html/bug-gnu-emacs/2013-01/msg00623.html -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #11 from Arne Babenhauserheide arne_...@web.de --- Strangely it does not work for me… I set emacs via emacs --parent-id=%w %f And it still openes a new emacs window instead of embedding it. How exactly do you define emacs as editor? Viesion is 4.9.5 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #12 from Arne Babenhauserheide arne_...@web.de --- … there I write and the next moment I find the answer myself: The correct command line is emacs --parent-id %w %f Thank you very much! -- 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 310927] New: shows no mails for missing subdir
https://bugs.kde.org/show_bug.cgi?id=310927 Bug ID: 310927 Severity: normal Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: shows no mails for missing subdir Classification: Unclassified OS: Linux Reporter: arne_...@web.de Hardware: Other Status: UNCONFIRMED Component: Maildir Resource Product: Akonadi A tree of maildirs: $MAILDIR_ROOT/maildir To replicate: rm -r $MAILDIR/tmp Result: No folders are shown (not even the ones with correct subdirs) I hit this issue because I transfer my maildirs with Mercurial. My workaround is adding a .keep file into every subdir, but that’s not nice. Reproducible: Always -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #8 from Arne Babenhauserheide arne_...@web.de --- That’s great! Thank you! You can test the embedding with emacs 23 by using emacs proper instead of emacsclient: emacs --parent-id %w %f that should embed emacs directly in the editor-window. The only advantages of emacsclient is that it starts faster and that it has all the open files I used in other editing sessions. I don’t see in the diff if you create a QX11EmbedContainer for generating the winid. It looks as if you just give it the ID of the editor window, and I don’t know if that can be used for embedding via xembed. (I hope my example python code helped a bit :) ) -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #10 from Arne Babenhauserheide arne_...@web.de --- Nice! I’m really anxious to test it in KDE 4.9.1! A thousand times thank you! -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version|1.13.5 |unspecified Resolution|WAITINGFORINFO |--- --- Comment #5 from Arne Babenhauserheide arne_...@web.de --- The bug is still valid: currently I can only specify “emacsclient -c %f”. That means a new Window gets opened. With the implemented wish I would be able to specify “emacsclient --parent-id=%w -c %f”. That would mean, that emacs would be opened inside the text frame of the kmail editor window. xembed for emacsclient has been implemented in the meantime (in emacs 24.x), so embedding is fast (if you run an emacs server - as recommended). -- 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 222701] new filter action: save all attachments to
https://bugs.kde.org/show_bug.cgi?id=222701 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Arne Babenhauserheide arne_...@web.de --- it’s still valid, yes. -- 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 209319] GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management)
https://bugs.kde.org/show_bug.cgi?id=209319 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Arne Babenhauserheide arne_...@web.de --- it’s still valid, yes. -- 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 176845] Occasional crash when hitting 'a' (Reply to All)
https://bugs.kde.org/show_bug.cgi?id=176845 --- Comment #20 from Arne Babenhauserheide arne_...@web.de --- I did not get this anymore with kmail2. -- 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 299739] New: password prompt is easy to miss because it appears behind the main window
https://bugs.kde.org/show_bug.cgi?id=299739 Bug ID: 299739 Severity: normal Version: 4.8.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: password prompt is easy to miss because it appears behind the main window Classification: Unclassified OS: Linux Reporter: arne_...@web.de Hardware: Other Status: UNCONFIRMED Component: UI Product: kmail2 For a new account the password prompt appears behind the main window (for me and for a user whom I migrated to kmail2 last week). Due to that it is easy to miss that it was shown at all. When trying to get mail multiple times, more and more password prompts are opened, but don’t get in front. At home I don’t get that, but here at work, it happens on my system (Gentoo) and on my collegues’ system (OpenSuse 12.1). Reproducible: Sometimes Steps to Reproduce: 1. create a new user account for fetching mail and/or one retrieving mail 2. check mail/try to send a mail 3. does not work (password dialogs in background) Actual Results: password dialogs in background Expected Results: password dialogs which are clearly visible I did not check every step again. This happened twice (once for the collegue and once 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
[Bug 293251] With Nepomuk disabled, setting an email as action item and then removing that mark removes the email
https://bugs.kde.org/show_bug.cgi?id=293251 --- Comment #4 from Arne Babenhauserheide arne_bab web de 2012-02-23 16:13:16 --- I do not know the exact message, becaue it only flashed briefly in the messages (and I did not think about clicking at the info icon in the doc :/ ) Is there something I cancheck to make this easier to debug? I can risk some spam messages for debugging, I think :) Best wishes, Arne At Wed, 22 Feb 2012 07:35:11 +, Laurent Montel wrote: https://bugs.kde.org/show_bug.cgi?id=293251 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #2 from Laurent Montel montel kde org 2012-02-22 07:35:11 --- could not modify message this is the exact message ? I can find it in source. -- 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. You reported the bug. -- 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 293251] With Nepomuk disabled, setting an email as action item and then removing that mark removes the email
https://bugs.kde.org/show_bug.cgi?id=293251 --- Comment #5 from Arne Babenhauserheide arne_bab web de 2012-02-23 16:13:43 --- Great, thanks! At Wed, 22 Feb 2012 07:40:02 +, Laurent Montel wrote: https://bugs.kde.org/show_bug.cgi?id=293251 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.8.1 Resolution||FIXED --- Comment #3 from Laurent Montel montel kde org 2012-02-22 07:40:02 --- It's duplicate from 289428 so it's fixed in 4.8.1 -- 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. You reported the bug. -- 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 292145] Crash on marking 10 000 mails in multiple folders as read
https://bugs.kde.org/show_bug.cgi?id=292145 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de -- 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 292145] Crash on marking 10 000 mails in multiple folders as read
https://bugs.kde.org/show_bug.cgi?id=292145 --- Comment #1 from Arne Babenhauserheide arne_bab web de 2012-02-20 13:52:43 --- Created an attachment (id=68952) -- (http://bugs.kde.org/attachment.cgi?id=68952) New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4 - What I was doing when the application crashed: Marking about 5 mails in different folders as read. Not all mails loaded, yet (the folders showed the loading sign). -- Backtrace (Reduced): #6 Akonadi::EntityTreeModel::setData (this=0x9ae640, index=..., value=..., role=53) at /var/tmp/portage/kde-base/kdepimlibs-4.8.0/work/kdepimlibs-4.8.0/akonadi/entitytreemodel.cpp:714 #7 0x7f0133881752 in rootIndexAboutToBeRemoved (removedRootIndex=optimized out, this=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.0/work/kdepimlibs-4.8.0/akonadi/selectionproxymodel.cpp:59 #8 Akonadi::SelectionProxyModel::qt_metacall (this=0x3b29920, _c=optimized out, _id=1, _a=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.0/work/kdepimlibs-4.8.0_build/akonadi/selectionproxymodel.moc:76 [...] #10 0x7f01396e27c2 in KSelectionProxyModel::rootIndexAboutToBeRemoved (this=0x9ae640, _t1=optimized out) at /var/tmp/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0_build/kdeui/moc_kselectionproxymodel.cpp:147 #11 0x7f01396edbc7 in KSelectionProxyModelPrivate::removeRangeFromProxy (this=0x14c55660, range=optimized out) at /var/tmp/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/kdeui/itemviews/kselectionproxymodel.cpp:1691 -- 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 293251] With Nepomuk disabled, setting an email as action item and then removing that mark removes the email
https://bugs.kde.org/show_bug.cgi?id=293251 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #1 from Arne Babenhauserheide arne_bab web de 2012-02-09 19:57:14 --- Update: This also happens with Nepomuk enabled. Just set a mail as “action item” (right click, mark message, action item) and it disappears with the error message “could not modify message”. Does not seem to happen for mails which are not in a group (means: which are not part of a thread). -- 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 293251] New: With Nepomuk disabled, setting an email as action item and then removing that mark removes the email
https://bugs.kde.org/show_bug.cgi?id=293251 Summary: With Nepomuk disabled, setting an email as action item and then removing that mark removes the email Product: kmail2 Version: 1.99.0 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.99.0 (using KDE 4.8.0) OS:Linux Not much to add to the title, sadly. I access my email through a local maildir folder filled by fetchmail and procmail, and it seems that the email is gone there, too (emacs wanderlust also does not see it anymore). I don’t know if it also happens with Nepomuk enabled. Reproducible: Always Steps to Reproduce: see title Expected Results: just mark and unmark. OS: Linux (x86_64) release 3.0.6-gentoo Compiler: x86_64-pc-linux-gnu-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 293255] New: crash while waiting for the GnuPG password window to appear and restarting nepomuk
https://bugs.kde.org/show_bug.cgi?id=293255 Summary: crash while waiting for the GnuPG password window to appear and restarting nepomuk Product: kmail2 Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kmail (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 3.0.6-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I clicked on sent in an email. It took 5min without showing the GnuPG password window. Then I increased the memory for nepomuk to 1000 MiB and terminated nepomuk. KMail crashed shortly thereafter. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7fd46cdb7760 (LWP 17872))] Thread 3 (Thread 0x7fd44e9fc700 (LWP 17875)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fd45edf06bd in WTF::TCMalloc_PageHeap::scavengerThread (this=optimized out) at wtf/FastMalloc.cpp:2378 #2 0x7fd45edf07e9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fd45f5c2f34) at wtf/FastMalloc.cpp:1497 #3 0x7fd467eb9cba in start_thread (arg=optimized out) at pthread_create.c:301 #4 0x7fd46a04ea4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fd44e0fb700 (LWP 17876)): #0 0x7fd46a045c93 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fd462c08960 in g_main_context_poll (n_fds=optimized out, fds=optimized out, priority=optimized out, timeout=optimized out, context=optimized out) at gmain.c:3402 #2 g_main_context_iterate (context=0xd3dde0, block=optimized out, dispatch=optimized out, self=optimized out) at gmain.c:3084 #3 0x7fd462c08d40 in g_main_context_iteration (context=0xd3dde0, may_block=1) at gmain.c:3152 #4 0x7fd46a9c3bce in QEventDispatcherGlib::processEvents (this=0xc62a50, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fd46a996732 in QEventLoop::processEvents (this=optimized out, flags=) at kernel/qeventloop.cpp:149 #6 0x7fd46a996afd in QEventLoop::exec (this=0x7fd44e0fae20, flags=) at kernel/qeventloop.cpp:201 #7 0x7fd46a8a3d92 in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #8 0x7fd46a8a6d45 in QThreadPrivate::start (arg=0xc51460) at thread/qthread_unix.cpp:331 #9 0x7fd467eb9cba in start_thread (arg=optimized out) at pthread_create.c:301 #10 0x7fd46a04ea4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fd46cdb7760 (LWP 17872)): [KCrash Handler] #6 0x7fd469fa9b75 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7fd469faaeff in *__GI_abort () at abort.c:92 #8 0x7fd469fa2abd in *__GI___assert_fail (assertion=0x7fd467ec4a98 robust || (oldval 0x4000) == 0, file=optimized out, line=321, function=0x7fd467ec4b10 __pthread_mutex_lock_full) at assert.c:81 #9 0x7fd467ebc3cd in __pthread_mutex_lock_full (mutex=0x5c430c0) at pthread_mutex_lock.c:321 #10 0x7fd46a8a5e43 in QMutexPrivate::wait (this=0x5c430a0, timeout=17872) at thread/qmutex_unix.cpp:80 #11 0x7fd46a8a1985 in QMutex::lock (this=0x77015f8) at thread/qmutex.cpp:167 #12 0x7fd45c63652e in QMutexLocker (m=optimized out, this=optimized out) at /usr/include/qt4/QtCore/qmutex.h:102 #13 Soprano::Client::SocketHandler::~SocketHandler (this=0x633e060, __in_chrg=optimized out) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/clientconnection.cpp:58 #14 0x7fd46a8a56fb in QThreadStorageData::set (this=optimized out, p=0x9b9d990) at thread/qthreadstorage.cpp:165 #15 0x7fd45c63680e in qThreadStorage_setLocalDataSoprano::Client::SocketHandler (t=optimized out, d=optimized out) at /usr/include/qt4/QtCore/qthreadstorage.h:92 #16 setLocalData (t=optimized out, this=optimized out) at /usr/include/qt4/QtCore/qthreadstorage.h:148 #17 Soprano::Client::ClientConnection::socketForCurrentThread (this=0x9850730) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/clientconnection.cpp:95 #18 0x7fd45c636849 in Soprano::Client::ClientConnection::connectInCurrentThread (this=0x45d0) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/clientconnection.cpp:800 #19 0x7fd45c63582c in Soprano::Client::LocalSocketClient::connect (this=0xd34be8, name=...) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/localsocketclient.cpp:141 #20 0x7fd463230378 in (anonymous namespace)::GlobalModelContainer::init (this=0xd34bc0, forced=optimized out) at
[Bug 292145] New: Crash on marking 10 000 mails in multiple folders as read
https://bugs.kde.org/show_bug.cgi?id=292145 Summary: Crash on marking 10 000 mails in multiple folders as read Product: kmail2 Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kmail (4.7.4) KDE Platform Version: 4.7.4 (4.7.4) (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 3.0.6-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I selected an account (legacy KMail Maildir) and all its subfolders. It contains over 100 000 emails. Then I rightclicked. It took about 5 minutes till the menu appeared. In that I then selected “mark all as read”. After almost all folders showed no more unread mail (all but the one with subfolders), KMail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7ff466064760 (LWP 15438))] Thread 4 (Thread 0x7ff447b82700 (LWP 15540)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7ff4581106bd in WTF::TCMalloc_PageHeap::scavengerThread (this=optimized out) at wtf/FastMalloc.cpp:2378 #2 0x7ff4581107e9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7ff4588e2f34) at wtf/FastMalloc.cpp:1497 #3 0x7ff461143cba in start_thread (arg=optimized out) at pthread_create.c:301 #4 0x7ff4632d8a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7ff447281700 (LWP 15541)): #0 0x7ff4632e59a6 in pthread_mutex_lock (mutex=0xd227a8) at forward.c:182 #1 0x7ff45bc2a0d1 in g_main_context_check (context=0xd227a0, max_priority=2147483647, fds=optimized out, n_fds=optimized out) at gmain.c:2961 #2 0x7ff45bc2a97a in g_main_context_iterate (context=0xd227a0, block=optimized out, dispatch=optimized out, self=optimized out) at gmain.c:3086 #3 0x7ff45bc2ad40 in g_main_context_iteration (context=0xd227a0, may_block=1) at gmain.c:3152 #4 0x7ff463c4dbce in QEventDispatcherGlib::processEvents (this=0xce5fd0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7ff463c20732 in QEventLoop::processEvents (this=optimized out, flags=) at kernel/qeventloop.cpp:149 #6 0x7ff463c20afd in QEventLoop::exec (this=0x7ff447280e20, flags=) at kernel/qeventloop.cpp:201 #7 0x7ff463b2dd92 in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #8 0x7ff463b30d45 in QThreadPrivate::start (arg=0xc30c00) at thread/qthread_unix.cpp:331 #9 0x7ff461143cba in start_thread (arg=optimized out) at pthread_create.c:301 #10 0x7ff4632d8a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7ff44459e700 (LWP 22050)): #0 0x7ff4611464b5 in __pthread_mutex_lock (mutex=0x24d3048) at pthread_mutex_lock.c:61 #1 0x7ff45bc2a0d1 in g_main_context_check (context=0x24d3040, max_priority=2147483647, fds=optimized out, n_fds=optimized out) at gmain.c:2961 #2 0x7ff45bc2a97a in g_main_context_iterate (context=0x24d3040, block=optimized out, dispatch=optimized out, self=optimized out) at gmain.c:3086 #3 0x7ff45bc2ad40 in g_main_context_iteration (context=0x24d3040, may_block=1) at gmain.c:3152 #4 0x7ff463c4dbce in QEventDispatcherGlib::processEvents (this=0x1fcaae0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7ff463c20732 in QEventLoop::processEvents (this=optimized out, flags=) at kernel/qeventloop.cpp:149 #6 0x7ff463c20afd in QEventLoop::exec (this=0x7ff44459dde0, flags=) at kernel/qeventloop.cpp:201 #7 0x7ff463b2dd92 in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #8 0x7ff463c005e0 in QInotifyFileSystemWatcherEngine::run (this=0x1e77690) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7ff463b30d45 in QThreadPrivate::start (arg=0x1e77690) at thread/qthread_unix.cpp:331 #10 0x7ff461143cba in start_thread (arg=optimized out) at pthread_create.c:301 #11 0x7ff4632d8a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7ff466064760 (LWP 15438)): [KCrash Handler] #6 Akonadi::EntityTreeModel::setData (this=0x695740, index=..., value=..., role=53) at /var/tmp/portage/kde-base/kdepimlibs-4.7.4-r1/work/kdepimlibs-4.7.4/akonadi/entitytreemodel.cpp:708 #7 0x7ff45fbe0d32 in rootIndexAboutToBeRemoved (removedRootIndex=optimized out, this=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.7.4-r1/work/kdepimlibs-4.7.4/akonadi/selectionproxymodel.cpp:59 #8 Akonadi::SelectionProxyModel::qt_metacall (this=0xfd9e7f0, _c=optimized out, _id=1, _a=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.7.4-r1/work/kdepimlibs-4.7.4_build/akonadi/selectionproxymodel.moc:76 #9
[Bug 41514] KMail freezes the UI when checking for new mail
https://bugs.kde.org/show_bug.cgi?id=41514 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #209 from Arne Babenhauserheide arne_bab web de 2011-09-22 07:22:34 --- *Happy*! -- 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 282595] New: Akonadi-Crash on sending E-Mail with attachment
https://bugs.kde.org/show_bug.cgi?id=282595 Summary: Akonadi-Crash on sending E-Mail with attachment Product: Akonadi Version: 4.7 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: to...@kde.org ReportedBy: arne_...@web.de CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_nepomuk_email_feeder (4.7) KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources) Qt Version: 4.7.2 Operating System: Linux 2.6.39-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Akonadi crashed, when I sent a GnuPG signed E-Mail with an image as attachment. -- Backtrace: Application: Akonadi Agent (akonadi_nepomuk_email_feeder), signal: Segmentation fault [KCrash Handler] #6 0x7f2f22bedf53 in QListQIODevice*::removeAll(QIODevice* const) () from /usr/lib64/libsopranoclient.so.1 #7 0x7f2f22beb542 in Soprano::Client::SocketHandler::~SocketHandler() () from /usr/lib64/libsopranoclient.so.1 #8 0x7f2f214e4350 in QThreadStorageData::set (this=value optimized out, p=0x3c02fd0) at thread/qthreadstorage.cpp:165 #9 0x7f2f22beb80e in Soprano::Client::ClientConnection::socketForCurrentThread() () from /usr/lib64/libsopranoclient.so.1 #10 0x7f2f22beb849 in Soprano::Client::ClientConnection::connectInCurrentThread() () from /usr/lib64/libsopranoclient.so.1 #11 0x7f2f22bea82c in Soprano::Client::LocalSocketClient::connect(QString const) () from /usr/lib64/libsopranoclient.so.1 #12 0x7f2f20f61b35 in (anonymous namespace)::GlobalModelContainer::init (this=0x84db90, forced=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/nepomuk/core/nepomukmainmodel.cpp:102 #13 0x7f2f20f62300 in Nepomuk::MainModel::init (this=0x84cd30) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/nepomuk/core/nepomukmainmodel.cpp:176 #14 0x7f2f20f5ad20 in Nepomuk::ResourceManager::init (this=0x84c3f0) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/nepomuk/core/resourcemanager.cpp:331 #15 0x7f2f20f5baa4 in Nepomuk::ResourceManagerPrivate::_k_storageServiceInitialized (this=0x84b5e0, success=value optimized out) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/nepomuk/core/resourcemanager.cpp:221 #16 0x7f2f20f5bba5 in Nepomuk::ResourceManager::qt_metacall (this=0x84c3f0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb2b76170) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1_build/nepomuk/resourcemanager.moc:90 #17 0x7f2f2120df29 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=value optimized out, slotIdx=value optimized out) at qdbusintegrator.cpp:941 #18 0x7f2f21218bbf in QDBusCallDeliveryEvent::placeMetaCall (this=0x68546e6565422d58, object=0x35e2568) at qdbusintegrator_p.h:103 #19 0x7f2f215f8cae in QObject::event (this=0x84c3f0, e=0x354b590) at kernel/qobject.cpp:1217 #20 0x7f2f1f71d2dc in QApplicationPrivate::notify_helper (this=0x67ea00, receiver=0x84c3f0, e=0x340e930) at kernel/qapplication.cpp:4462 #21 0x7f2f1f7255e7 in QApplication::notify (this=0x7fffb2b76e40, receiver=0x84c3f0, e=0x340e930) at kernel/qapplication.cpp:4341 #22 0x7f2f22735810 in KApplication::notify (this=0x7fffb2b76e40, receiver=0x84c3f0, event=0x340e930) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/kdeui/kernel/kapplication.cpp:311 #23 0x7f2f215e5e0b in QCoreApplication::notifyInternal (this=0x7fffb2b76e40, receiver=0x84c3f0, event=0x340e930) at kernel/qcoreapplication.cpp:731 #24 0x7f2f215e738b in sendEvent (receiver=0x0, event_type=value optimized out, data=0x65d050) at kernel/qcoreapplication.h:215 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x65d050) at kernel/qcoreapplication.cpp:1372 #26 0x7f2f21615b93 in sendPostedEvents (s=0x682180) at kernel/qcoreapplication.h:220 #27 postEventSourceDispatch (s=0x682180) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7f2f182c3cd9 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x7f2f182c8218 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #30 0x7f2f182c83be in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #31 0x7f2f2161575e in QEventDispatcherGlib::processEvents (this=0x65cc50, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:422 #32 0x7f2f1f7dbd26 in QGuiEventDispatcherGlib::processEvents (this=0x354b590, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #33 0x7f2f215e4a12 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #34 0x7f2f215e4ddd in
[Bug 282454] New: crash on save in browser
https://bugs.kde.org/show_bug.cgi?id=282454 Summary: crash on save in browser Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: akonadiconsole AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: akonadiconsole (0.99) KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources) Qt Version: 4.7.2 Operating System: Linux 2.6.39-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Akonadi-Konsole just crashed when I hit the save button in its browser. I changed the ACL of the KMail Folders (they were readonly). Then I hit save - crash. I hope the backtrace helps! Best wishes, Arne -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Aborted [Current thread is 1 (Thread 0x7f89a5f56760 (LWP 3726))] Thread 2 (Thread 0x7f898ba93700 (LWP 3730)): #0 0x7f899b1d483c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f899d2c47ac in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f899d2c47e9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f899b1cfd9a in start_thread () from /lib64/libpthread.so.0 #4 0x7f89a0b4200d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f89a5f56760 (LWP 3726)): [KCrash Handler] #6 0x7f89a0aa2775 in raise () from /lib64/libc.so.6 #7 0x7f89a0aa3aff in abort () from /lib64/libc.so.6 #8 0x7f89a2f860c4 in qt_message_output (msgType=QtFatalMsg, buf=value optimized out) at global/qglobal.cpp:2282 #9 0x7f89a2f8625e in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f89a30ff7b0 ASSERT: \%s\ in file %s, line %d, ap=0x7fffe85718d0) at global/qglobal.cpp:2328 #10 0x7f89a2f86415 in qFatal (msg=0xe8e Address 0xe8e out of bounds) at global/qglobal.cpp:2511 #11 0x00428cca in BrowserWidget::save (this=0x9489a0) at /var/tmp/portage/kde-base/akonadiconsole-4.7.1/work/akonadiconsole-4.7.1/akonadiconsole/browserwidget.cpp:370 #12 0x0042a524 in BrowserWidget::qt_metacall (this=0x9489a0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffe8571d30) at /var/tmp/portage/kde-base/akonadiconsole-4.7.1/work/akonadiconsole-4.7.1_build/akonadiconsole/browserwidget.moc:91 #13 0x7f89a30ab60a in QMetaObject::activate (sender=0x905bd0, m=value optimized out, local_signal_index=value optimized out, argv=0x) at kernel/qobject.cpp:3278 #14 0x7f89a1c0f992 in QAbstractButton::clicked (this=0xe8e, _t1=false) at .moc/debug-shared/moc_qabstractbutton.cpp:206 #15 0x7f89a18dac30 in QAbstractButtonPrivate::emitClicked (this=0xac24c0) at widgets/qabstractbutton.cpp:546 #16 0x7f89a18dc380 in QAbstractButtonPrivate::click (this=0xac24c0) at widgets/qabstractbutton.cpp:539 #17 0x7f89a18dc5ac in QAbstractButton::mouseReleaseEvent (this=0x905bd0, e=0x7fffe8572890) at widgets/qabstractbutton.cpp:1121 #18 0x7f89a152cd8b in QWidget::event (this=0x905bd0, event=0x7fffe8572890) at kernel/qwidget.cpp:8259 #19 0x7f89a14cf2dc in QApplicationPrivate::notify_helper (this=0x695820, receiver=0x905bd0, e=0x7fffe8572890) at kernel/qapplication.cpp:4462 #20 0x7f89a14d822c in QApplication::notify (this=0x7fffe85733e0, receiver=0x905bd0, e=0x7fffe8572890) at kernel/qapplication.cpp:4023 #21 0x7f89a27f0810 in KApplication::notify (this=0x7fffe85733e0, receiver=0x905bd0, event=0x7fffe8572890) at /var/tmp/portage/kde-base/kdelibs-4.7.1/work/kdelibs-4.7.1/kdeui/kernel/kapplication.cpp:311 #22 0x7f89a3090e0b in QCoreApplication::notifyInternal (this=0x7fffe85733e0, receiver=0x905bd0, event=0x7fffe8572890) at kernel/qcoreapplication.cpp:731 #23 0x7f89a14d3ea9 in sendEvent (receiver=0x905bd0, event=0x7fffe8572890, alienWidget=0x0, nativeWidget=0x905bd0, buttonDown=value optimized out, lastMouseReceiver=value optimized out, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #24 QApplicationPrivate::sendMouseEvent (receiver=0x905bd0, event=0x7fffe8572890, alienWidget=0x0, nativeWidget=0x905bd0, buttonDown=value optimized out, lastMouseReceiver=value optimized out, spontaneous=true) at kernel/qapplication.cpp:3122 #25 0x7f89a1563ab3 in QETWidget::translateMouseEvent (this=0x905bd0, event=value optimized out) at kernel/qapplication_x11.cpp:4461 #26 0x7f89a1562ad9 in QApplication::x11ProcessEvent (this=value optimized out, event=0x7fffe8573010) at kernel/qapplication_x11.cpp:3587 #27 0x7f89a158e3e2 in x11EventSourceDispatch (s=0x6990c0, callback=value optimized out, user_data=value optimized out) at kernel/qguieventdispatcher_glib.cpp:146 #28 0x7f8999ed2cd9 in g_main_context_dispatch () from
[Bug 282401] New: Can’t send messages anymore :(
https://bugs.kde.org/show_bug.cgi?id=282401 Summary: Can’t send messages anymore :( Product: kmail2 Version: 4.7 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 4.7 (using KDE 4.7.1) OS:Linux Since I updated to kde 4.7.1, I cannot send mails anymore. KMail now has a new cathegory (Local Folders, side by side with the folder “mail”) and my mails sit in the outbox there. Right-clicking the outbox and selecting “send queued messages” does not help - and also does not get kmail to do any action. This problem is critical, because it actually stops the main function of KMail to work. Reproducible: Didn't try Steps to Reproduce: Use kmail 4.7.0, downgrade to 4.4.10, use that for a moment till you realize that it’s wrong, upgrade to 4.7.1. Actual Results: mails sit in outbox and there is a new cathegory “local folders”. Expected Results: mails get sent and the old “KMail Folders” continue to get used. OS: Linux (x86_64) release 2.6.39-gentoo-r3 Compiler: x86_64-pc-linux-gnu-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 282401] Can’t send messages anymore :(
https://bugs.kde.org/show_bug.cgi?id=282401 --- Comment #2 from Arne Babenhauserheide arne_bab web de 2011-09-20 13:30:54 --- “FIX”: akonadi-konsole: set kmail folders ACL to read+write+exec -- 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 282430] New: signing an imported certificate
https://bugs.kde.org/show_bug.cgi?id=282430 Summary: signing an imported certificate Product: kleopatra Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de CC: m...@kde.org Application: kleopatra (2.1.1) KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources) Qt Version: 4.7.2 Operating System: Linux 2.6.39-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I signed the certificate of gscrivano ät gnu.org (search it on the keyserver) - it crashed after checking the verified-fingerprint box and hitting next . -- Backtrace: Application: Kleopatra (kleopatra), signal: Aborted [Current thread is 1 (Thread 0x7fe4f55a5760 (LWP 3168))] Thread 4 (Thread 0x7fe4df741700 (LWP 3169)): #0 0x7fe4f1180273 in poll () from /lib64/libc.so.6 #1 0x7fe4ecff3f81 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe4ecff43be in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe4f2b007ae in QEventDispatcherGlib::processEvents (this=0xc4a5b0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fe4f2acfa12 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7fe4f2acfddd in QEventLoop::exec (this=0x7fe4df740de0, flags=) at kernel/qeventloop.cpp:201 #6 0x7fe4f29ce6b8 in QThread::exec (this=value optimized out) at thread/qthread.cpp:492 #7 0x7fe4f2aad2d5 in QInotifyFileSystemWatcherEngine::run (this=0xc3ab00) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fe4f29d138a in QThreadPrivate::start (arg=0xc3ab00) at thread/qthread_unix.cpp:320 #9 0x7fe4f4926d9a in start_thread () from /lib64/libpthread.so.0 #10 0x7fe4f118900d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe4dd877700 (LWP 3350)): #0 0x7fe4f492 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe4f29d1f7d in wait (this=value optimized out, mutex=0xa99ca0, time=2000) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=value optimized out, mutex=0xa99ca0, time=2000) at thread/qwaitcondition_unix.cpp:160 #3 0x006ab5ec in (anonymous namespace)::ReaderStatusThread::run (this=value optimized out) at /var/tmp/portage/kde-base/kleopatra-4.7.1/work/kleopatra-4.7.1/kleopatra/smartcard/readerstatus.cpp:542 #4 0x7fe4f29d138a in QThreadPrivate::start (arg=0xa99c90) at thread/qthread_unix.cpp:320 #5 0x7fe4f4926d9a in start_thread () from /lib64/libpthread.so.0 #6 0x7fe4f118900d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe4def40700 (LWP 4578)): #0 0x7fe4f1180273 in poll () from /lib64/libc.so.6 #1 0x7fe4ecff3f81 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe4ecff43be in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe4f2b007ae in QEventDispatcherGlib::processEvents (this=0x1018be0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fe4f2acfa12 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7fe4f2acfddd in QEventLoop::exec (this=0x7fe4def3fde0, flags=) at kernel/qeventloop.cpp:201 #6 0x7fe4f29ce6b8 in QThread::exec (this=value optimized out) at thread/qthread.cpp:492 #7 0x7fe4f2aad2d5 in QInotifyFileSystemWatcherEngine::run (this=0xe97c00) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fe4f29d138a in QThreadPrivate::start (arg=0xe97c00) at thread/qthread_unix.cpp:320 #9 0x7fe4f4926d9a in start_thread () from /lib64/libpthread.so.0 #10 0x7fe4f118900d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe4f55a5760 (LWP 3168)): [KCrash Handler] #6 0x7fe4f10e9775 in raise () from /lib64/libc.so.6 #7 0x7fe4f10eaaff in abort () from /lib64/libc.so.6 #8 0x7fe4f10e26bd in __assert_fail () from /lib64/libc.so.6 #9 0x0067e320 in Kleo::Commands::CertifyCertificateCommand::Private::createJob (this=0x116b640) at /var/tmp/portage/kde-base/kleopatra-4.7.1/work/kleopatra-4.7.1/kleopatra/commands/certifycertificatecommand.cpp:261 #10 0x0067e573 in Kleo::Commands::CertifyCertificateCommand::Private::slotCertificationPrepared (this=0x116b640) at /var/tmp/portage/kde-base/kleopatra-4.7.1/work/kleopatra-4.7.1/kleopatra/commands/certifycertificatecommand.cpp:221 #11 0x0067e954 in Kleo::Commands::CertifyCertificateCommand::qt_metacall (this=0x10e3980, _c=QMetaObject::InvokeMetaMethod, _id=-1, _a=0x7fff9032d490) at /var/tmp/portage/kde-base/kleopatra-4.7.1/work/kleopatra-4.7.1_build/kleopatra/moc_certifycertificatecommand.cpp:78 #12 0x7fe4f2aeb60a in QMetaObject::activate
[Bug 32400] Sort by last / newest mail in thread
https://bugs.kde.org/show_bug.cgi?id=32400 --- Comment #29 from Arne Babenhauserheide arne_bab web de 2011-08-30 14:22:22 --- Stéphane: You can enable threading by newest in thread, now. -- 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 276186] Crash on startup while loading mail
https://bugs.kde.org/show_bug.cgi?id=276186 --- Comment #5 from Arne Babenhauserheide arne_bab web de 2011-07-27 11:19:24 --- Many 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 277828] New: Crash on quit (error reading folder Spam)
https://bugs.kde.org/show_bug.cgi?id=277828 Summary: Crash on quit (error reading folder Spam) Product: kmail2 Version: 2.1.1 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kmail (2.1.1) KDE Platform Version: 4.6.5 (4.6.5) (Compiled from sources) Qt Version: 4.7.3 Operating System: Linux 2.6.36-gentoo-r5 x86_64 Distribution: Gentoo Base System release 2.0.3 -- Information about the crash: - What I was doing when the application crashed: I told kmail to quit (ctrl-q). It did not close directly but first synced some more. Then it popped up the system notification “cen’t read meil from folder Spam” (huge folder) and died (Dr. Konqui showed up). The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fbeb9e4c760 (LWP 11444))] Thread 2 (Thread 0x7fbe9b3f0700 (LWP 11455)): #0 0x7fbeb4f9d85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbeabd7e81d in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fbeabd7e949 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fbeb4f98dba in start_thread () from /lib64/libpthread.so.0 #4 0x7fbeb712606d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fbeb9e4c760 (LWP 11444)): [KCrash Handler] #6 0x7fbeb375fe87 in QListQString::free(QListData::Data*) () from /usr/lib64/libakonadi-kde.so.4 #7 0x7fbeb378646a in Akonadi::Collection::contentMimeTypes() const () from /usr/lib64/libakonadi-kde.so.4 #8 0x7fbeb29e78fb in MailCommon::FolderCollection::isStructural() const () from /usr/lib64/libmailcommon.so.4 #9 0x7fbeb8ba1065 in KMMainWidget::updateFolderMenu() () from /usr/lib64/libkmailprivate.so.4 #10 0x7fbeb8bb1072 in KMMainWidget::slotEndCheckMail() () from /usr/lib64/libkmailprivate.so.4 #11 0x7fbeb8bb3641 in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #12 0x7fbeb7a6f487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7fbeb8b5dd0c in KMKernel::slotProgressItemCompletedOrCanceled(KPIM::ProgressItem*) () from /usr/lib64/libkmailprivate.so.4 #14 0x7fbeb8b6c45a in KMKernel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #15 0x7fbeb7a6f487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7fbeb11b0792 in KPIM::ProgressManager::progressItemCanceled(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #17 0x7fbeb11b239b in KPIM::ProgressManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 #18 0x7fbeb7a6f487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #19 0x7fbeb11b0a32 in KPIM::ProgressItem::progressItemCanceled(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #20 0x7fbeb11b203f in KPIM::ProgressItem::cancel() () from /usr/lib64/libkdepim.so.4 #21 0x7fbeb11b32b2 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libkdepim.so.4 #22 0x7fbeb11b3462 in KPIM::AgentProgressMonitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 #23 0x7fbeb7a6f487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7fbeb3773ba5 in Akonadi::AgentManager::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libakonadi-kde.so.4 #25 0x7fbeb3779808 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #26 0x7fbeb3779fb3 in Akonadi::AgentManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #27 0x7fbeb7a6f487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #28 0x7fbeb388d57b in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #29 0x7fbeb388dbaf in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #30 0x7fbeb51d57a9 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const, QListint const, int) () from /usr/lib64/qt4/libQtDBus.so.4 #31 0x7fbeb51df53f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib64/qt4/libQtDBus.so.4 #32 0x7fbeb7a695ae in QObject::event(QEvent*) () from
[Bug 276186] Crash on startup while loading mail
https://bugs.kde.org/show_bug.cgi?id=276186 --- Comment #2 from Arne Babenhauserheide arne_bab web de 2011-06-27 12:41:55 --- Created an attachment (id=61365) -- (http://bugs.kde.org/attachment.cgi?id=61365) New crash information added by DrKonqi kmail (2.1.0) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3 - What I was doing when the application crashed: On startup it begins getting mail, then it starts filtering and shows many messages that there where mails it could not read from the folder. After filtering, it dies. Trying to abort the filtering did not help (and did not work: it said “aborting” in the progress indicator (bottom right), but then started the filtering and died nontheless). I had some disk-full errors some time ago, so this might be related. PS: Dr. Konqui to append to the bugreport is extremely useful. I hope my reports help… -- Backtrace (Reduced): #6 0x7f4b9768cfd2 in KPIM::ProgressItem::removeChild(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #7 0x7f4b9768d131 in KPIM::ProgressItem::setComplete() () from /usr/lib64/libkdepim.so.4 #8 0x7f4b9768eba7 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libkdepim.so.4 #9 0x7f4b9768ecc2 in KPIM::AgentProgressMonitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 [...] #11 0x7f4b99c48ba5 in Akonadi::AgentManager::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libakonadi-kde.so.4 -- 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 276186] Crash on startup while loading mail
https://bugs.kde.org/show_bug.cgi?id=276186 --- Comment #3 from Arne Babenhauserheide arne_bab web de 2011-06-27 13:34:59 --- Created an attachment (id=61367) -- (http://bugs.kde.org/attachment.cgi?id=61367) valgrind report valgrind report (because that was asked for in bug 265076 ): valgrind kmail --nofork report -- 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 276186] Crash on startup while loading mail
https://bugs.kde.org/show_bug.cgi?id=276186 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de -- 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 276382] New: Selected email suddenly changes to old email on update
https://bugs.kde.org/show_bug.cgi?id=276382 Summary: Selected email suddenly changes to old email on update Product: kmail2 Version: 2.1.0 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 2.1.0 (using KDE 4.6.4) OS:Linux While browsing my mails, the selected mail often jumps to very old emails of a sudden, when kmail updates ist message list (which disturbs my “I’m now going to look at my mails in order of appearance” workflow, because I have to find the place in the message list again, where I left off). Reproducible: Didn't try OS: Linux (x86_64) release 2.6.36-gentoo-r5 Compiler: x86_64-pc-linux-gnu-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 276404] New: crash when clicking “keep both” in a conflict resolution
https://bugs.kde.org/show_bug.cgi?id=276404 Summary: crash when clicking “keep both” in a conflict resolution Product: kmail2 Version: 2.1.0 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kmail (2.1.0) KDE Platform Version: 4.6.4 (4.6.4) (Compiled from sources) Qt Version: 4.7.3 Operating System: Linux 2.6.36-gentoo-r5 x86_64 Distribution: Gentoo Base System release 2.0.3 -- Information about the crash: - What I was doing when the application crashed: I clicked “keep both” in a conflict resolution dialog. The dialog disappeared and a moment later Dr. Konqui came up. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f9ec6c77760 (LWP 25936))] Thread 2 (Thread 0x7f9ea79e5700 (LWP 25946)): #0 0x7f9ec137685c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9eb7f1a9dd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f9eb7f1ab09 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f9ec1371dba in start_thread () from /lib64/libpthread.so.0 #4 0x7f9ec3f4306d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f9ec6c77760 (LWP 25936)): [KCrash Handler] #6 0x7f9ec488c205 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f9ebd3799f2 in KPIM::ProgressItem::progressItemCompleted(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #8 0x7f9ebd37a058 in KPIM::ProgressItem::removeChild(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #9 0x7f9ebd37a131 in KPIM::ProgressItem::setComplete() () from /usr/lib64/libkdepim.so.4 #10 0x7f9ebd37bb75 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libkdepim.so.4 #11 0x7f9ebd37bcc2 in KPIM::AgentProgressMonitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 #12 0x7f9ec488c487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7f9ebf934ba5 in Akonadi::AgentManager::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libakonadi-kde.so.4 #14 0x7f9ebf93a808 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #15 0x7f9ebf93afb3 in Akonadi::AgentManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #16 0x7f9ec488c487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #17 0x7f9ebfa4e57b in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #18 0x7f9ebfa4ebaf in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #19 0x7f9ec15ae7a9 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const, QListint const, int) () from /usr/lib64/qt4/libQtDBus.so.4 #20 0x7f9ec15b853f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib64/qt4/libQtDBus.so.4 #21 0x7f9ec48865ae in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f9ec4d7320c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #23 0x7f9ec4d786cd in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #24 0x7f9ec66a81a8 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #25 0x7f9ec487486b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #26 0x7f9ec48777e9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x7f9ec48a0d33 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #28 0x7f9ebba61c39 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x7f9ebba66178 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #30 0x7f9ebba6631e in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #31 0x7f9ec48a081e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7f9ec4e25a66 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #33 0x7f9ec48735b2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #34
[Bug 276186] New: Crash on startup while loading mail
https://bugs.kde.org/show_bug.cgi?id=276186 Summary: Crash on startup while loading mail Product: kmail2 Version: 2.1.0 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kmail (2.1.0) KDE Platform Version: 4.6.4 (4.6.4) (Compiled from sources) Qt Version: 4.7.3 Operating System: Linux 2.6.36-gentoo-r5 x86_64 Distribution: Gentoo Base System release 2.0.3 -- Information about the crash: - What I was doing when the application crashed: I started kmail. It took a few minutes while loading mail (blocked GUI), then it crashed. It does not crash every time, but I did not find out when it crashes. Before this crash it had worked without problems, then I used quit and restarted a few minutes later. That second start (after the clean quit) le to the crash. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fcd97e7f760 (LWP 18387))] Thread 2 (Thread 0x7fcd78bed700 (LWP 18401)): #0 0x7fcd9257e85c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcd891229dd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fcd89122b09 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fcd92579dba in start_thread () from /lib64/libpthread.so.0 #4 0x7fcd9514b06d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcd97e7f760 (LWP 18387)): [KCrash Handler] #6 0x7fcd8e581fce in KPIM::ProgressItem::removeChild(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #7 0x7fcd8e582131 in KPIM::ProgressItem::setComplete() () from /usr/lib64/libkdepim.so.4 #8 0x7fcd8e583ba7 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libkdepim.so.4 #9 0x7fcd8e583cc2 in KPIM::AgentProgressMonitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 #10 0x7fcd95a94487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #11 0x7fcd90b3cba5 in Akonadi::AgentManager::instanceStatusChanged(Akonadi::AgentInstance const) () from /usr/lib64/libakonadi-kde.so.4 #12 0x7fcd90b42808 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #13 0x7fcd90b42fb3 in Akonadi::AgentManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #14 0x7fcd95a94487 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7fcd90c5657b in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged(QString const, int, QString const) () from /usr/lib64/libakonadi-kde.so.4 #16 0x7fcd90c56baf in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #17 0x7fcd927b67a9 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const, QListint const, int) () from /usr/lib64/qt4/libQtDBus.so.4 #18 0x7fcd927c053f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib64/qt4/libQtDBus.so.4 #19 0x7fcd95a8e5ae in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7fcd95f7b20c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #21 0x7fcd95f806cd in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #22 0x7fcd978b01a8 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #23 0x7fcd95a7c86b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7fcd95a7f7e9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7fcd95aa8d33 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #26 0x7fcd8cc69c39 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7fcd8cc6e178 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #28 0x7fcd8cc6e31e in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7fcd95aa881e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7fcd9602da66 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #31 0x7fcd95a7b5b2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7fcd95a7b97d in
[Bug 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #13 from Arne Babenhauserheide arne_bab web de 2011-06-15 00:29:30 --- This happens a lot for me, too - much more, since I updated from VCS version to 4.6.4 - and it disturbs my workflow a lot, even while I’m in other programs. I understand that conflicts might be hard (if not impossible) to avoid in a concurrent system, but I don’t really look at the messages myself but just click them away. So I’d need a way to say “always keep both”. Means: Just make sure I don’t lose data, and otherwise don’t disturb me. Besides: I use bogofilter, too. -- 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 265968] New: The last letter of a line is counted as the next line
https://bugs.kde.org/show_bug.cgi?id=265968 Summary: The last letter of a line is counted as the next line Product: kmail2 Version: 2.0.89 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 2.0.89 (using KDE 4.6.0) OS:Linux To reproduce: Type a paragraph and move the point to the last letter. Now go forward one letter (next line). The “line” number in the status bar does not change. Reproducible: Always OS: Linux (x86_64) release 2.6.34-gentoo-r6 Compiler: x86_64-pc-linux-gnu-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 263622] New: When opening kmail shortly after closing it, I see “failed to get lock”, the next day it works again
https://bugs.kde.org/show_bug.cgi?id=263622 Summary: When opening kmail shortly after closing it, I see “failed to get lock”, the next day it works again Product: kmail2 Version: 2.0.89 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 2.0.89 (using KDE 4.5.95) OS:Linux When opening kmail shortly after closing it, I get the error “failed to get lock” and kmail asks me to close it (works, though). The next day it works again, so I assume there might be a clock problem. I live in Germany, GMT+1, currently NOT daylight saving time. I did not yet check it thoroughly, only noticed that when I wail long enough after closing kmail2, I can start it again. Reproducible: Sometimes OS: Linux (x86_64) release 2.6.34-gentoo-r6 Compiler: x86_64-pc-linux-gnu-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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock.
https://bugs.kde.org/show_bug.cgi?id=246027 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #4 from Arne Babenhauserheide arne_bab web de 2011-01-16 12:11:41 --- I was getting this, too. Removing my akonadi and nepomuk folders (after doing a backup) fixed it for me (more precisely: at least I can now open it again, and I see mails). -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #1 from Arne Babenhauserheide arne_bab web de 2010-11-23 16:34:27 --- Some info I found: Discussion in the emacs list: - http://osdir.com/ml/general/2010-04/msg38048.html - http://osdir.com/ml/general/2010-04/msg36121.html qtxembeddedcontainer: - http://doc.trolltech.com/solutions/qtxembed/qtxembedcontainer.html A more general solution would be an emacs kpart. Possible TODO on the emacs-side: xembed also for emacsclient. Best wishes, Arne -- 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 255008] external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 --- Comment #2 from Arne Babenhauserheide arne_bab web de 2010-11-23 19:05:31 --- I wrote a proof of concept embedding script. It’s very simple (only opens a qt window and embeds emacs), but it works: http://bitbucket.org/ArneBab/kembed-emacs/src/tip/qxembed-emacs.py -- 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 230072] pop3: mails are often not deleted on the server (web.de) - I get many duplicate messages
https://bugs.kde.org/show_bug.cgi?id=230072 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #17 from Arne Babenhauserheide arne_bab web de 2010-10-31 13:53:30 --- I get no more duplicate emails since the last update. Many 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 255008] New: external editor: string replace for the window id to be used with xembed
https://bugs.kde.org/show_bug.cgi?id=255008 Summary: external editor: string replace for the window id to be used with xembed Product: kmail Version: 1.13.5 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.13.5 (using KDE 4.5.2) OS:Linux I’ve been experimenting with emacs as standard-editor for the composer, and I stumbled upon xembed: http://www.emacswiki.org/emacs/EmacsXembed By passing emacs the window ID of the parent window, it seems that it can be embedded in the window. So I’d like to see an option to not only add the file to the command via %f, but also to add the window ID of the composer text-area (or an overlay) via %w or similar. With that, any external editor should be embeddable as if it were the native one. Well, I could also spell this bug as „I’d like to embed emacs directly into kmail instead of opening it in a seperate window or switching to a running emacs window“ :) Reproducible: Didn't try OS: Linux (x86_64) release 2.6.34-gentoo-r6 Compiler: x86_64-pc-linux-gnu-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 252024] New: akonadi and akonadi resources crash at startup
https://bugs.kde.org/show_bug.cgi?id=252024 Summary: akonadi and akonadi resources crash at startup Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: akonadi_kabc_resource (0.1) KDE Platform Version: 4.5.1 (KDE 4.5.1) (Compiled from sources) Qt Version: 4.6.3 Operating System: Linux 2.6.34-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Just starting KDE shows repeated crash reports from akonadi. Also plasma crashes repeatedly but then stops crashing after some time. This might be my systems fault, though: I’ve been getting repeated (but not consistent) segfaults when compiling a huge C++ library for about a week, so I assume my memory might be faulty. What bugs me is that many akonadi resources crash, too, so the problem isn’t quite isolated. akonadiconsole runs but doesn’t show data (shows the loading wheel in front of the entry in the list to the left for a minute or so before I quit the program — might also just be slow). Kontact froze two times while writing a message (after a few minutes). I think that might be connected. -- Backtrace: Application: Akonadi Resource (akonadi_kabc_resource), signal: Segmentation fault [KCrash Handler] #6 0x7fedecee7ca3 in Akonadi::NotificationMessage::operation() const () from /usr/lib/libakonadiprotocolinternals.so.1 #7 0x7fedf0ab3c40 in Akonadi::MonitorPrivate::invalidateCaches(Akonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #8 0x7fedf0ab41cd in Akonadi::MonitorPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #9 0x7fedf0a2ace2 in Akonadi::ChangeRecorderPrivate::slotNotify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #10 0x7fedf0aaed92 in Akonadi::Monitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #11 0x7fedf0a277d8 in Akonadi::ChangeRecorder::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #12 0x7fedf0698e2e in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7fedf0b065b2 in OrgFreedesktopAkonadiNotificationManagerInterface::notify(QListAkonadi::NotificationMessage const) () from /usr/lib/libakonadi-kde.so.4 #14 0x7fedf0b065fd in OrgFreedesktopAkonadiNotificationManagerInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libakonadi-kde.so.4 #15 0x7feded81b4b9 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const, QListint const, int) () from /usr/lib64/qt4/libQtDBus.so.4 #16 0x7feded82581f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib64/qt4/libQtDBus.so.4 #17 0x7fedf0695a79 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7fedeea752bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #19 0x7fedeea7b79b in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #20 0x7fedef766996 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #21 0x7fedf068602b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7fedf068964b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x7fedf06af163 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7fedec5f6993 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x7fedec5fa798 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #26 0x7fedec5fa954 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x7fedf06aecc3 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #28 0x7fedeeb221be in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #29 0x7fedf06849c2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7fedf0684d9d in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #31 0x7fedf0689903 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7fedf0abfbf9 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #33 0x0040c6f8 in main () Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because:
[Bug 252024] akonadi and akonadi resources crash at startup
https://bugs.kde.org/show_bug.cgi?id=252024 Arne Babenhauserheide arne_...@web.de changed: What|Removed |Added CC||arne_...@web.de --- Comment #1 from Arne Babenhauserheide arne_bab web de 2010-09-22 15:43:24 --- This could also either be a mysql error (amarok required the old version) or an outdated /etc/kdebugrc. -- 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 251396] New: akonadi crash when starting kopete in xmonad
https://bugs.kde.org/show_bug.cgi?id=251396 Summary: akonadi crash when starting kopete in xmonad Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Mail Dispatcher Agent AssignedTo: cber...@gmail.com ReportedBy: arne_...@web.de CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_maildispatcher_agent (0.1) KDE Platform Version: 4.5.1 (KDE 4.5.1) (Compiled from sources) Qt Version: 4.6.3 Operating System: Linux 2.6.34-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I started kopete. It didn’t show for some time. Then all akonadi resources showed me a Dr. Konqui, one for each (and one for kopete). - Unusual behavior I noticed: The resources keep crashing again and again. a...@fluss ~ $ pkill kopete a...@fluss ~ $ kopete kopete(28480) Kopete::Global::Properties::Properties: kopete(28480) Kopete::IdentityManager::load: Created identity XWlvYCOSPa kopete(28480) Kopete::IdleTimer::IdleTimer: Using platform idle timer QSystemTrayIcon::setVisible: No Icon set kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 org.freedesktop.DBus.Error.NameHasNoOwner Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name a...@fluss ~ $ kopete a...@fluss ~ $ kopete kopete(28598): Communication problem with kopete , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : 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. a...@fluss ~ $ a...@fluss ~ $ kopete(28480)/kdecore (KLibrary) kde4Factory: The library /usr/lib64/kde4/kopete_history.so does not offer a qt_plugin_instance function. kopete(28480) ChatWindowStyleManager::ChatWindowStyleManager: kopete(28480) ChatWindowStyleManager::loadStyles: /home/arne/.kde4.1/share/apps/kopete/styles/ kopete(28480) ChatWindowStyleManager::loadStyles: /usr/share/apps/kopete/styles/ kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28480) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) KCrash: Application 'kopete' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/arne/.kde4/socket-fluss/kdeinit4__1 a...@fluss ~ $ kopete kopete(28707) Kopete::Global::Properties::Properties: kopete(28707) Kopete::IdentityManager::load: Created identity XWlvYCOSPa kopete(28707) Kopete::IdleTimer::IdleTimer: Using platform idle timer QSystemTrayIcon::setVisible: No Icon set kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) ^[O4Q^[O4Rkopete(28706): Communication problem with kopete , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : 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. a...@fluss ~ $ a...@fluss ~ $ kopete kopete(28755): Communication problem with kopete , it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : 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. a...@fluss ~ $ kopete(28707)/kdecore (KLibrary) kde4Factory: The library /usr/lib64/kde4/kopete_history.so does not offer a qt_plugin_instance function. kopete(28707) ChatWindowStyleManager::ChatWindowStyleManager: kopete(28707) ChatWindowStyleManager::loadStyles: /home/arne/.kde4.1/share/apps/kopete/styles/ kopete(28707) ChatWindowStyleManager::loadStyles: /usr/share/apps/kopete/styles/ kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28707) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(28707) KopeteWindow::slotIdentityStatusIconChanged:
[Bug 248185] New: crash when pressing A (shift-a) while kmail assembles threads
https://bugs.kde.org/show_bug.cgi?id=248185 Summary: crash when pressing A (shift-a) while kmail assembles threads Product: kmail Version: 1.13.5 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.13.5 OS:Linux Hi, Shortly after starting, kmail first assembles the messages into threads. When I select a messages and hit A (shift-a) while kmail is still assembling the threads, it crashes. I could reproduce it once, but didn’t try a third time, so I selected „happens sometimes“ instead of „happens always“. Many thanks for writing kmail! And damn am I anxcious to try the akonadi-version! ;) Reproducible: Sometimes OS: Linux (x86_64) release 2.6.34-gentoo-r1 Compiler: x86_64-pc-linux-gnu-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 230072] pop3: mails are often not deleted on the server (web.de) - I get many duplicate messages
https://bugs.kde.org/show_bug.cgi?id=230072 --- Comment #11 from Arne Babenhauserheide arne_bab web de 2010-07-30 15:26:00 --- will the fix be backported into current kdepim, or will it go only into 4.5.1? -- 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 230072] New: pop3: mails are often not deleted on the server (web.de) - I get many duplicate messages
https://bugs.kde.org/show_bug.cgi?id=230072 Summary: pop3: mails are often not deleted on the server (web.de) - I get many duplicate messages Product: kmail Version: 1.13.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.13.1 (using 4.4.1 (KDE 4.4.1), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.31-gentoo-r6 I currently get about 1 to 5 copies of each mail, one more every time I check for new mail, until at some point I couldn't yet determine the mails are really deleted. I use pop3 and don't keep on server with pop3.web.de, but the messages get downloaded again and again, making my inbox quite unreadable. -- 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 229059] New: crash when trying to reply (hit “a”) while having another email open
https://bugs.kde.org/show_bug.cgi?id=229059 Summary: crash when trying to reply (hit “a”) while having another email open Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kontact (4.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.31-gentoo-r6 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Kmail crashed on me when I tried to reply while it was under high load (as it usually is :) ). IIRC It died when I hit “a” to reply. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7f8fbaf4c66e in KMCommand::slotStart() () from /usr/lib64/libkmailprivate.so.4 #6 0x7f8fbaf4551a in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #7 0x7f8fcdb60a47 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f8fcdb67b7f in QSingleShotTimer::timerEvent(QTimerEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f8fcdb5d563 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x7f8fce278dcd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #11 0x7f8fce280054 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #12 0x7f8fcf3eea3b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x7f8fcdb4d973 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #14 0x7f8fcdb7a38c in QTimerInfoList::activateTimers() () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7f8fcdb76d94 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7f8fc9763e61 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x7f8fc97673f8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #18 0x7f8fc97675ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #19 0x7f8fcdb76a8c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7f8fce327b4f in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #21 0x7f8fcdb4c2e2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f8fcdb4c6b4 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x7f8fcee28b96 in KJob::exec() () from /usr/lib64/libkdecore.so.5 #24 0x7f8fbaefc55c in KMail::FancyHeaderStyle::format(KMMessage const*, KMail::HeaderStrategy const*, QString const, bool, bool) const () from /usr/lib64/libkmailprivate.so.4 #25 0x7f8fbad90392 in KMReaderWin::writeMsgHeader(KMMessage*, partNode*, bool) () from /usr/lib64/libkmailprivate.so.4 #26 0x7f8fbada4e8c in KMReaderWin::parseMsg(KMMessage*) () from /usr/lib64/libkmailprivate.so.4 #27 0x7f8fbad96660 in KMReaderWin::displayMessage() () from /usr/lib64/libkmailprivate.so.4 #28 0x7f8fbad96845 in KMReaderWin::updateReaderWin() () from /usr/lib64/libkmailprivate.so.4 #29 0x7f8fbada7a5d in KMReaderWin::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #30 0x7f8fcdb60a47 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #31 0x7f8fcdb5d563 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7f8fce278dcd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #33 0x7f8fce280054 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #34 0x7f8fcf3eea3b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #35 0x7f8fcdb4d973 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #36 0x7f8fcdb7a38c in QTimerInfoList::activateTimers() () from /usr/lib64/qt4/libQtCore.so.4 #37 0x7f8fcdb76d94 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #38 0x7f8fc9763e61 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #39 0x7f8fc97673f8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #40 0x7f8fc97675ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #41 0x7f8fcdb76a8c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #42 0x7f8fce327b4f in
[Bug 227655] New: Crash when sending an E-Mail under high load
https://bugs.kde.org/show_bug.cgi?id=227655 Summary: Crash when sending an E-Mail under high load Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application: kontact (4.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.31-gentoo-r6 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: I just had my first Kontact crash since I switched to SC 4.4. I sent an email and switched to another program. I can't reproduce it, though, since it holds my private data and I'm scared of losing it. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7fa67e30a12d in QMapKEntryKey, KEntry::freeData(QMapData*) () from /usr/lib64/libkdecore.so.5 #6 0x7fa67e3060f4 in KConfig::reparseConfiguration() () from /usr/lib64/libkdecore.so.5 #7 0x7fa67e31e7b6 in KCoreConfigSkeleton::readConfig() () from /usr/lib64/libkdecore.so.5 #8 0x7fa66939101a in MailTransport::Transport::Transport(QString const) () from /usr/lib64/libmailtransport.so.4 #9 0x7fa66939110e in MailTransport::Transport::clone() const () from /usr/lib64/libmailtransport.so.4 #10 0x7fa669394870 in MailTransport::TransportManager::createTransportJob(int) () from /usr/lib64/libmailtransport.so.4 #11 0x7fa669394b93 in MailTransport::TransportManager::createTransportJob(QString const) () from /usr/lib64/libmailtransport.so.4 #12 0x7fa66a31eea6 in KMSender::doSendMsg() () from /usr/lib64/libkmailprivate.so.4 #13 0x7fa66a322069 in KMSender::doSendQueued(QString const) () from /usr/lib64/libkmailprivate.so.4 #14 0x7fa66a4ad5da in KMMainWidget::slotSendQueued() () from /usr/lib64/libkmailprivate.so.4 #15 0x7fa66a4c7168 in KMMainWidget::slotMailChecked(bool, bool, QMapQString, int const) () from /usr/lib64/libkmailprivate.so.4 #16 0x7fa66a4c974f in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #17 0x7fa67d0a29e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7fa66a30b812 in KMail::AccountManager::checkedMail(bool, bool, QMapQString, int const) () from /usr/lib64/libkmailprivate.so.4 #19 0x7fa66a30d510 in KMail::AccountManager::processNextCheck(bool) () from /usr/lib64/libkmailprivate.so.4 #20 0x7fa66a30d9e2 in KMail::AccountManager::singleCheckMail(KMAccount*, bool) () from /usr/lib64/libkmailprivate.so.4 #21 0x7fa66a28ca75 in KMAccount::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #22 0x7fa66a3dbe35 in KMail::PopAccount::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #23 0x7fa67d0a29e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7fa67d09f503 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7fa67d7badcd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #26 0x7fa67d7c2054 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #27 0x7fa67e930a3b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #28 0x7fa67d08f913 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #29 0x7fa67d0bc32c in QTimerInfoList::activateTimers() () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7fa67d0b8d34 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #31 0x7fa678ca8e61 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0x7fa678cac3f8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #33 0x7fa678cac5ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0x7fa67d0b8a2c in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #35 0x7fa67d869b4f in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #36 0x7fa67d08e282 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #37 0x7fa67d08e654 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #38 0x7fa67d090a46 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #39 0x00404af9 in main () Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 221231] very slow and dbus-daemon causing high load
https://bugs.kde.org/show_bug.cgi?id=221231 --- Comment #1 from Arne Babenhauserheide arne_bab web de 2010-01-15 22:28:04 --- I still have the problem after rebuilding everything without debug, so it seems debug wasn't the reason. To illustrate the severity of the problem: Sending a mail currently needs between 1 minute and 30 minutes between clicking send and seeing the GnuPG enter password for your key dialog (yes, minutes). -- 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 222701] New: new filter action: save all attachments to
https://bugs.kde.org/show_bug.cgi?id=222701 Summary: new filter action: save all attachments to Product: kmail Version: 1.13.0 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.13.0 (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.31-gentoo-r6 I now get my newspaper by email, and I'd like to tell KMail to automatically copy all attachments from the mails into an archive folder. I couldn't find an option for that in the filter dialog. -- 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 146805] General I want to contact person x workflow
https://bugs.kde.org/show_bug.cgi?id=146805 --- Comment #1 from Arne Babenhauserheide arne_bab web de 2010-01-13 09:02:51 --- Even simpler option: When rightclicking on a person *somewhere* the menu could offer a contact entry with subentries for the different ways I could use to contact the person. That would be similar to the drag-and-drop implementation (ask what I want to do). -- 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 222143] New: pop3 emails are downloaded and shown multiple times when leaving mail on server
https://bugs.kde.org/show_bug.cgi?id=222143 Summary: pop3 emails are downloaded and shown multiple times when leaving mail on server 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: arne_...@web.de Version: 1.13.0 (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.31-gentoo-r6 I had my mail account set to delete mails only one day after fetching them. I then received every mail multiple times. The problem first appeared when I used kmail under high load (dbus compiled with debug flags really kills off kmail performance for me) even though I then set the mails to be deleted upon retrieval. It isn't nice for usability, because the mails are also shown multiple times, so the list gets cluttered with multiple copies of the same mail(s). Best wishes, Arne -- 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 221231] New: very slow and dbus-daemon causing high load
https://bugs.kde.org/show_bug.cgi?id=221231 Summary: very slow and dbus-daemon causing high load 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: arne_...@web.de Version: 1.13.0 (using 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.31-gentoo-r6 Since two weeks ago or so (after the 4.4 eta2 update) Kontact often becomes dead slow and dbus-daemon takes all CPU time it can get. I think the change I did was disabling CONFIG_SYSFS_DEPRECATED in the kernel (KDE SC 4.4 beta 2 on GNU/Linux via Gentoo). The other option is that the 4.4 beta2 is the reason (though beta1 didn't create any performance problems). It mostly appears when downloading new mail or trying to write a mail - especially when I write to many people. Possibly also related: My nepomuk doesn't really work (indexer doesn't work) since I enabled redland in the compile again (via Gentoo USE flag redland). -- 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 219453] New: Kontact crashes in kmail in apply all filters to many mails [QEventLoop::processEvents, QEventLoop::exec, KJob::exec]
https://bugs.kde.org/show_bug.cgi?id=219453
Summary: Kontact crashes in kmail in apply all filters to
many mails [QEventLoop::processEvents,
QEventLoop::exec, KJob::exec]
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: arne_...@web.de
Application: kontact (4.4 pre)
KDE Platform Version: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) (Compiled from
sources)
Qt Version: 4.6.0
Operating System: Linux 2.6.30-gentoo-r5 x86_64
Distribution (Platform): Gentoo Packages
-- Information about the crash:
I tried to apply all filters to many mails (about 100 or so) and Kontact (with
KMail open) crashed instantly.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 QEventLoop::processEvents (this=0x1be5100, flags={i = 1721642608}) at
kernel/qeventloop.cpp:145
#6 0x7f5a0903e3b4 in QEventLoop::exec (this=0x1be5100, flags={i =
1721642672}) at kernel/qeventloop.cpp:201
#7 0x7f5a096d3912 in KJob::exec (this=0x15998c0) at
/var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdecore/jobs/kjob.cpp:202
#8 0x7f59f5ed014a in KMSearchRuleString::matchesInternal (this=value
optimized out, msgContents=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:475
#9 0x7f59f5ed194f in KMSearchRuleString::matches (this=0x159f060,
msg=0x1be2820) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:404
#10 0x7f59f5ece4fc in KMSearchPattern::matches (this=0x159f5b0,
msg=0x1be2820, ignoreBody=false) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:746
#11 0x7f59f5eba127 in KMFilterMgr::isMatching (this=value optimized out,
msg=0x1be2820, filter=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmfiltermgr.cpp:279
#12 0x7f59f5ebaa7e in KMFilterMgr::process (this=0xe25950, msg=0x1be2820,
set=value optimized out, account=false, accountId=0)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmfiltermgr.cpp:245
#13 0x7f59f5fe0bb7 in KMMainWidget::slotFilterMsg (this=value optimized
out, msg=0x1be2820) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmmainwidget.cpp:2555
#14 0x7f59f5fe124d in KMMainWidget::slotApplyFilters (this=0x15a9870) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmmainwidget.cpp:2537
#15 0x7f59f5ff6830 in KMMainWidget::qt_metacall (this=0x15a9870,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff669e3b40)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmmainwidget.moc:439
#16 0x7f5a090541bf in QMetaObject::activate (sender=0x1a71800, m=value
optimized out, local_signal_index=value optimized out, argv=0x3) at
kernel/qobject.cpp:3286
#17 0x7f5a08006b42 in QAction::triggered (this=0x1be5100, _t1=false) at
.moc/debug-shared/moc_qaction.cpp:263
#18 0x7f5a08007c30 in QAction::activate (this=0x1a71800, event=value
optimized out) at kernel/qaction.cpp:1245
#19 0x7f5a0841cd34 in QMenuPrivate::activateCausedStack (this=0x1b8ed50,
causedsta...@0x7fff669e3c60, action=0x1a71800, action_e=QAction::Trigger,
self=true) at widgets/qmenu.cpp:994
#20 0x7f5a084231fb in QMenuPrivate::activateAction (this=0x1b8ed50,
action=0x1a71800, action_e=27789184, self=true) at widgets/qmenu.cpp:1086
#21 0x7f5a09d37c85 in KMenu::mouseReleaseEvent (this=0x1a80780,
e=0x7fff669e49e0) at
/var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/widgets/kmenu.cpp:469
#22 0x7f5a08065ebc in QWidget::event (this=0x1a80780, event=0x7fff669e49e0)
at kernel/qwidget.cpp:7974
#23 0x7f5a08423fa3 in QMenu::event (this=0x1a80780, e=0x7fff669e49e0) at
widgets/qmenu.cpp:2406
#24 0x7f5a0800d776 in QApplicationPrivate::notify_helper (this=0x6481a0,
receiver=0x1a80780, e=0x7fff669e49e0) at kernel/qapplication.cpp:4242
#25 0x7f5a08015fe9 in QApplication::notify (this=value optimized out,
receiver=0x1a80780, e=0x7fff669e49e0) at kernel/qapplication.cpp:3822
#26 0x7f5a09c715c1 in KApplication::notify (this=0x7fff669e72d0,
receiver=0x1a80780, event=0x7fff669e49e0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/kernel/kapplication.cpp:302
#27 0x7f5a0903f603 in QCoreApplication::notifyInternal
(this=0x7fff669e72d0, receiver=0x1a80780, event=0x7fff669e49e0) at
kernel/qcoreapplication.cpp:704
#28 0x7f5a080188f1 in QApplicationPrivate::sendMouseEvent
(receiver=0x1a80780, event=0x7fff669e49e0, alienWidget=0x0,
nativeWidget=0x1a80780, buttonDown=value optimized out,
lastmousereceiv...@0x7f5a08a55a80, spontaneous=true) at
[Bug 218492] New: kgpg crashes at login after update to 4.3.80 [QEventLoop::exec, KJob::exec, KMSearchRuleString::matchesInternal]
https://bugs.kde.org/show_bug.cgi?id=218492
Summary: kgpg crashes at login after update to 4.3.80
[QEventLoop::exec, KJob::exec,
KMSearchRuleString::matchesInternal]
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: arne_...@web.de
Application: kontact (4.4 pre)
KDE Platform Version: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) (Compiled from
sources)
Qt Version: 4.6.0
Operating System: Linux 2.6.30-gentoo-r5 x86_64
Distribution (Platform): Gentoo Packages
-- Information about the crash:
kgpg crashes at login after update to 4.3.80.
Possibly related: pykde-4.3.80 doesn't build for me, so I currently use
pykde-4.3.4 with kdelibs-4.3.80.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 0x7f673948b3c5 in QEventLoop::exec (this=0x2128690, flags={i =
-382100432}) at ../../include/QtCore/../../src/corelib/tools/qstack.h:67
#6 0x7f6739b20912 in KJob::exec (this=0x28b5e20) at
/var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdecore/jobs/kjob.cpp:202
#7 0x7f6726cde14a in KMSearchRuleString::matchesInternal (this=value
optimized out, msgContents=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:475
#8 0x7f6726cdf94f in KMSearchRuleString::matches (this=0x15987a0,
msg=0x248c100) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:404
#9 0x7f6726cdc4fc in KMSearchPattern::matches (this=0x15ad1a0,
msg=0x248c100, ignoreBody=false) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmsearchpattern.cpp:746
#10 0x7f6726cc8127 in KMFilterMgr::isMatching (this=value optimized out,
msg=0x248c100, filter=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmfiltermgr.cpp:279
#11 0x7f6726cc8a7e in KMFilterMgr::process (this=0xf51210, msg=0x248c100,
set=value optimized out, account=true, accountId=551501770)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmfiltermgr.cpp:245
#12 0x7f6726c4e4cb in KMAccount::processNewMsg (this=0xd80c50,
aMsg=0x248c100) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmaccount.cpp:264
#13 0x7f6726d4f540 in KMail::PopAccount::slotProcessPendingMsgs
(this=0xd80c50) at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/popaccount.cpp:324
#14 0x7f6726d4fc08 in KMail::PopAccount::qt_metacall (this=0xd80c50,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffe939a830)
at
/var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/popaccount.moc:88
#15 0x7f67394a11bf in QMetaObject::activate (sender=0xd80e10, m=value
optimized out, local_signal_index=value optimized out,
argv=0xf004fb0) at kernel/qobject.cpp:3286
#16 0x7f673949d6d3 in QObject::event (this=0xd80e10, e=0x60c620) at
kernel/qobject.cpp:1216
#17 0x7f673845a776 in QApplicationPrivate::notify_helper (this=0x648600,
receiver=0xd80e10, e=0x7fffe939afe0) at kernel/qapplication.cpp:4242
#18 0x7f67384621f5 in QApplication::notify (this=0x7fffe939b320,
receiver=0xd80e10, e=0x7fffe939afe0) at kernel/qapplication.cpp:4207
#19 0x7f673a0be5c1 in KApplication::notify (this=0x7fffe939b320,
receiver=0xd80e10, event=0x7fffe939afe0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/kernel/kapplication.cpp:302
#20 0x7f673948c603 in QCoreApplication::notifyInternal
(this=0x7fffe939b320, receiver=0xd80e10, event=0x7fffe939afe0) at
kernel/qcoreapplication.cpp:704
#21 0x7f67394bc9bc in QTimerInfoList::activateTimers (this=0x655760) at
kernel/qcoreapplication.h:215
#22 0x7f67394b8fe8 in idleTimerSourceDispatch (source=value optimized
out) at kernel/qeventdispatcher_glib.cpp:184
#23 0x7f67315c5fc1 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#24 0x7f67315c9558 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#25 0x7f67315c970c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#26 0x7f67394b8cbc in QEventDispatcherGlib::processEvents (this=0x638880,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:407
#27 0x7f67385005df in QGuiEventDispatcherGlib::processEvents (this=0x2,
flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x7f673948afe2 in QEventLoop::processEvents (this=value optimized
out, flags={i = -382094768}) at kernel/qeventloop.cpp:149
#29 0x7f673948b3b4 in QEventLoop::exec (this=0x7fffe939b290, flags={i =
-382094688}) at kernel/qeventloop.cpp:201
#30 0x7f673948d844 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:981
#31 0x00403f9a in main (argc=3,
[Bug 216913] New: crash when trying to forward a specific mail via shortcut (F)
https://bugs.kde.org/show_bug.cgi?id=216913 Summary: crash when trying to forward a specific mail via shortcut (F) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application that crashed: kontact Version of the application: 4.3.3 KDE Version: 4.3.3 (KDE 4.3.3) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r5 x86_64 What I was doing when the application crashed: When I tried to forward an email (account activation info from the flipside forums) Kontact crashed. A second try (after restart) had the same result, so I assume I can reproduce it. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KMReaderWin::htmlMail (this=0x0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:2558 #6 0x7f30fbde7ee7 in KMail::ObjectTreeParser::processMultiPartAlternativeSubtype (this=0x7fff9d22b540, node=value optimized out) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:1182 #7 0x7f30fbde7ae0 in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff9d22b540, node=0x2944300) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:296 #8 0x7f30fbc24476 in KMMessage::parseTextStringFromDwPart (this=value optimized out, root=0x2944300, parsedstri...@0x7fff9d22b760, cod...@0x7fff9d22b758, isht...@0x7fff9d22b76f) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:502 #9 0x7f30fbc246a8 in KMMessage::asPlainText (this=0x28f6d80, aStripSignature=false, allowDecryption=false) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:527 #10 0x7f30fbc26ae1 in KMMessage::createForward (this=0x28f6d80, tm...@0x7fff9d22bda0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmmessage.cpp:1001 #11 0x7f30fbe0806d in KMForwardCommand::execute (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:1344 #12 0x7f30fbe0cd1b in KMCommand::slotPostTransfer (this=0x2598e50, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:274 #13 0x7f30fbe0cdf6 in KMCommand::qt_metacall (this=0x2598e50, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff9d22c390) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:87 #14 0x7f310d765e69 in QMetaObject::activate (sender=0x2598e50, from_signal_index=value optimized out, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101 #15 0x7f30fbdf7a3e in KMCommand::messagesTransfered (this=0x0, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:102 #16 0x7f30fbe0cb2b in KMCommand::transferSelectedMsgs (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:368 #17 0x7f30fbe0d7de in KMCommand::slotStart (this=0x2598e50) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:266 #18 0x7f30fbe0ce0a in KMCommand::qt_metacall (this=0x2598e50, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff9d22c610) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmcommands.moc:86 #19 0x7f310d765e69 in QMetaObject::activate (sender=0x1803760, from_signal_index=value optimized out, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101 #20 0x7f310d76b5ff in QSingleShotTimer::timerEvent (this=0x1803760) at kernel/qtimer.cpp:298 #21 0x7f310d760763 in QObject::event (this=0x1803760, e=0x3) at kernel/qobject.cpp:1066 #22 0x7f310e4f46dd in QApplicationPrivate::notify_helper (this=0x63c2f0, receiver=0x1803760, e=0x7fff9d22ccf0) at kernel/qapplication.cpp:4065 #23 0x7f310e4fd00e in QApplication::notify (this=0x7fff9d22d030, receiver=0x1803760, e=0x7fff9d22ccf0) at kernel/qapplication.cpp:4030 #24 0x7f310f2c30f1 in KApplication::notify (this=0x7fff9d22d030, receiver=0x1803760, event=0x7fff9d22ccf0) at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302 #25 0x7f310d750d03 in QCoreApplication::notifyInternal (this=0x7fff9d22d030, receiver=0x1803760, event=0x7fff9d22ccf0) at kernel/qcoreapplication.cpp:606 #26 0x7f310d77abd6 in QTimerInfoList::activateTimers (this=0x64c220) at kernel/qcoreapplication.h:213 #27 0x7f310d777e2d in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:165 #28 0x7f3108d33fc1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x7f3108d37558 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #30 0x7f3108d3770c in
[Bug 216100] adding an email to the addressbook makes adresses inaccessible for KMail (maybe akonadi bug)
https://bugs.kde.org/show_bug.cgi?id=216100 --- Comment #1 from Arne Babenhauserheide arne_bab web de 2009-11-25 14:43:28 --- typo: could be a duplicate of bug #191841 (I forgot to add the 1 at the end, sorry.) -- 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 215869] crash when opening a message from the outbox under very high load
https://bugs.kde.org/show_bug.cgi?id=215869 --- Comment #2 from Arne Babenhauserheide arne_bab web de 2009-11-25 15:20:16 --- I have the preview window active, so it's likely that they are related. I can't easily check it, though, since the crash only happened once (and I didn't dare do anything which migth have triggered it afterwards). -- 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 215869] New: crash when opening a message from the outbox under very high load
https://bugs.kde.org/show_bug.cgi?id=215869
Summary: crash when opening a message from the outbox under
very high load
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: arne_...@web.de
Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
I tried to send a mail, but sending failed (needed to receive first).
Then I found an error in the mail (view in outbox, not yet edit window).
I doubleclicked it and Kontact died.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 0x7f417ee5b7b0 in KMReaderWin::parseMsg (this=0x1571ce0,
aMsg=0x440d9d0) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1688
#6 0x7f417ee5341e in KMReaderWin::displayMessage (this=0x1571ce0) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1608
#7 0x7f417ee5361a in KMReaderWin::updateReaderWin (this=0x1571ce0) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1548
#8 0x7f417ee56afd in KMReaderWin::qt_metacall (this=0x1571ce0,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffe4b433d0)
at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmreaderwin.moc:168
#9 0x7f41908e8e69 in QMetaObject::activate (sender=0x1571d88,
from_signal_index=value optimized out, to_signal_index=4, argv=0xb) at
kernel/qobject.cpp:3101
#10 0x7f41908e3763 in QObject::event (this=0x1571d88, e=0x4e) at
kernel/qobject.cpp:1066
#11 0x7f41916776dd in QApplicationPrivate::notify_helper (this=0x64a850,
receiver=0x1571d88, e=0x7fffe4b43aa0) at kernel/qapplication.cpp:4065
#12 0x7f419168000e in QApplication::notify (this=0x7fffe4b46030,
receiver=0x1571d88, e=0x7fffe4b43aa0) at kernel/qapplication.cpp:4030
#13 0x7f41924460f1 in KApplication::notify (this=0x7fffe4b46030,
receiver=0x1571d88, event=0x7fffe4b43aa0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#14 0x7f41908d3d03 in QCoreApplication::notifyInternal
(this=0x7fffe4b46030, receiver=0x1571d88, event=0x7fffe4b43aa0) at
kernel/qcoreapplication.cpp:606
#15 0x7f41908fdbd6 in QTimerInfoList::activateTimers (this=0x63cf50) at
kernel/qcoreapplication.h:213
#16 0x7f41908fae2d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#17 0x7f418beb6fc1 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x7f418beba558 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#19 0x7f418beba70c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x7f41908fad9f in QEventDispatcherGlib::processEvents (this=0x6340e0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#21 0x7f419170328f in QGuiEventDispatcherGlib::processEvents
(this=0x440d9d0, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#22 0x7f41908d29c2 in QEventLoop::processEvents (this=value optimized
out, flags={i = -457949936}) at kernel/qeventloop.cpp:149
#23 0x7f41908d2b5c in QEventLoop::exec (this=0x2b545c0, flags={i =
-457949760}) at kernel/qeventloop.cpp:197
#24 0x7f417f07eebe in KMail::KleoJobExecutor::exec (this=0x7fffe4b44050,
job=0x44d1270, signatu...@0x7fffe4b44840, signedda...@0x7fffe4b44850)
at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kleojobexecutor.cpp:56
#25 0x7f417ef6d57d in
KMail::ObjectTreeParser::writeOpaqueOrMultipartSignedData (this=0x7fffe4b44d30,
data=0x1c4d430, si...@0x38fbbc0, fromaddre...@0x3fff710, doCheck=true,
cleartextData=0x0,
paramsignatur...@0x7fffe4b449a0, hideErrors=false) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:476
#26 0x7f417ef6f723 in
KMail::ObjectTreeParser::processMultiPartSignedSubtype (this=0x7fffe4b44d30,
node=0x3fff650)
at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:1266
#27 0x7f417ef6aae0 in KMail::ObjectTreeParser::parseObjectTree
(this=0x7fffe4b44d30, node=0x3fff650) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/objecttreeparser.cpp:296
#28 0x7f417ee28e73 in KMComposeWin::setMsg (this=0x21a81b0,
newMsg=0x34c2f90, mayAutoSign=false, allowDecryption=true, isModified=false)
at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcomposewin.cpp:1602
#29 0x7f417ef8e582 in KMEditMsgCommand::execute (this=value optimized
out) at
/var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmcommands.cpp:692
#30 0x7f417ef8fd1b
[Bug 215418] New: adding a contact often doesn't work (no target folders shown)
https://bugs.kde.org/show_bug.cgi?id=215418 Summary: adding a contact often doesn't work (no target folders shown) Product: kmail Version: 1.12.3 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.12.3 (using 4.3.3 (KDE 4.3.3), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.30-gentoo-r5 Reproduce: * Leave kontact running for some time * Right-click E-Mail address in received mail * select add to address book * No groups shown (shortly after starting kontact it works). -- 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 211975] New: clicking in search bar in huge folder crashed kontact
https://bugs.kde.org/show_bug.cgi?id=211975
Summary: clicking in search bar in huge folder crashed kontact
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: arne_...@web.de
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#5 0x7ff1a6e7f205 in raise () from /lib/libc.so.6
#6 0x7ff1a6e80723 in abort () from /lib/libc.so.6
#7 0x7ff1a7bb7295 in qt_message_output (msgType=QtFatalMsg, buf=value
optimized out) at global/qglobal.cpp:2042
#8 0x7ff1a7bb73b0 in qFatal (msg=value optimized out) at
global/qglobal.cpp:2241
#9 0x7ff196284d23 in
KMail::MessageListView::Core::Model::applyFilterToSubtree (this=0x179d370,
item=0x680aa40, parentind...@0x7fff153a01a0)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:348
#10 0x7ff19628b02e in KMail::MessageListView::Core::Model::setFilter
(this=0x179d370, filter=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:340
#11 0x7ff1962b308c in
KMail::MessageListView::Core::Widget::searchTimerFired (this=0x1776f40)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/widgetbase.cpp:1130
#12 0x7ff195f7a963 in KMail::MessageListView::Core::Widget::qt_metacall
(this=0x1776f40, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fff153a0340)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widgetbase.cpp:119
#13 0x7ff195f7aa75 in KMail::MessageListView::Widget::qt_metacall
(this=0x5503, _c=21763, _id=6, _a=0x)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widget.cpp:75
#14 0x7ff1a7cb1eb9 in QMetaObject::activate (sender=0x6bbc760,
from_signal_index=value optimized out, to_signal_index=4,
argv=0x) at kernel/qobject.cpp:3101
#15 0x7ff1a7cac7b3 in QObject::event (this=0x6bbc760, e=0x5503) at
kernel/qobject.cpp:1066
#16 0x7ff1a8a3f6dd in QApplicationPrivate::notify_helper (this=0x64a270,
receiver=0x6bbc760, e=0x7fff153a0a10) at kernel/qapplication.cpp:4065
#17 0x7ff1a8a4800e in QApplication::notify (this=0x7fff153a0d50,
receiver=0x6bbc760, e=0x7fff153a0a10) at kernel/qapplication.cpp:4030
#18 0x7ff1a980e061 in KApplication::notify (this=0x7fff153a0d50,
receiver=0x6bbc760, event=0x7fff153a0a10)
at
/var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#19 0x7ff1a7c9cd53 in QCoreApplication::notifyInternal
(this=0x7fff153a0d50, receiver=0x6bbc760, event=0x7fff153a0a10) at
kernel/qcoreapplication.cpp:606
#20 0x7ff1a7cc6c46 in QTimerInfoList::activateTimers (this=0x635bc0) at
kernel/qcoreapplication.h:213
#21 0x7ff1a7cc3e7d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#22 0x7ff1a327ff41 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7ff1a32834d8 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#24 0x7ff1a328368c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7ff1a7cc3def in QEventDispatcherGlib::processEvents (this=0x63d240,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:328
#26 0x7ff1a8acb28f in QGuiEventDispatcherGlib::processEvents (this=0x5503,
flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x7ff1a7c9ba12 in QEventLoop::processEvents (this=value optimized
out, flags={i = 356125824}) at kernel/qeventloop.cpp:149
#28 0x7ff1a7c9bbac in QEventLoop::exec (this=0x7fff153a0cc0, flags={i =
356125904}) at kernel/qeventloop.cpp:197
#29 0x7ff1a7ca0526 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#30 0x0040405a in main (argc=1, argv=0x7fff153a1268) at
/var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218
This bug may be a duplicate of or related to bug 211046
Reported using DrKonqi
--
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 211711] New: doubleclick on akonadi addressbook-resource crashed kontact
https://bugs.kde.org/show_bug.cgi?id=211711 Summary: doubleclick on akonadi addressbook-resource crashed kontact Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r5 x86_64 What I was doing when the application crashed: I switched to the kaddressbook view in kontact and doubleclicked the akonadi-resource (which didn't show me any kontacts, though it should have all). Then it showed a message saying already loading or similar. A few moments later Kontact died. (I'm not sure if I doubleclicked the akonadi-resource again after the message) My system is under high load, right now - damn high load - and sluggish at times, so it could be a race. -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #5 0x7f67e35d9205 in raise () from /lib/libc.so.6 #6 0x7f67e35da723 in abort () from /lib/libc.so.6 #7 0x7f67e4311295 in qt_message_output (msgType=QtFatalMsg, buf=value optimized out) at global/qglobal.cpp:2042 #8 0x7f67e43113b0 in qFatal (msg=value optimized out) at global/qglobal.cpp:2241 #9 0x7f67cd1ec432 in ResourcePrivateBase::loadingResult (this=0x199d1c0, ok=value optimized out, errorString=value optimized out) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2/kresources/shared/resourceprivatebase.cpp:489 #10 0x7f67cd1dbc5c in SharedResourcePrivateSubResource::loadingResult (this=0x17d3, ok=211, errorstri...@0x6) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2/kresources/shared/sharedresourceprivate.h:129 #11 0x7f67cd1d8ac4 in KABC::ResourceAkonadi::Private::loadingResult (this=0x17d3, ok=211, errorstri...@0x6) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2/kresources/kabc/resourceakonadi_p.cpp:259 #12 0x7f67cd1ec348 in ResourcePrivateBase::qt_metacall (this=0x199d1c0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fff577be060) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2_build/kresources/kabc/resourceprivatebase.moc:77 #13 0x7f67cd1d86f5 in KABC::ResourceAkonadi::Private::qt_metacall (this=0x17d3, _c=6099, _id=6, _a=0x) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2_build/kresources/kabc/resourceakonadi_p.moc:77 #14 0x7f67e440beb9 in QMetaObject::activate (sender=0x199d228, from_signal_index=value optimized out, to_signal_index=6, argv=0x) at kernel/qobject.cpp:3101 #15 0x7f67cd1e3a97 in AbstractSubResourceModel::loadingResult (this=0x17d3, _t1=true, _t2=value optimized out) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2_build/kresources/kabc/abstractsubresourcemodel.moc:134 #16 0x7f67cd1e3f65 in AbstractSubResourceModel::asyncCollectionsResult (this=0x199d228, job=0x1f0f250) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2/kresources/shared/abstractsubresourcemodel.cpp:269 #17 0x7f67cd1e448f in AbstractSubResourceModel::qt_metacall (this=0x199d228, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff577be220) at /var/tmp/portage/kde-base/akonadi-4.3.2/work/kdepim-runtime-4.3.2_build/kresources/kabc/abstractsubresourcemodel.moc:106 #18 0x7f67e440beb9 in QMetaObject::activate (sender=0x1f0f250, from_signal_index=value optimized out, to_signal_index=7, argv=0x) at kernel/qobject.cpp:3101 #19 0x7f67e4a21612 in KJob::result (this=0x17d3, _t1=0x1f0f250) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2_build/kdecore/kjob.moc:188 #20 0x7f67e4a21a13 in KJob::emitResult (this=0x1f0f250) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdecore/jobs/kjob.cpp:304 #21 0x7f67ccf34bb2 in Akonadi::JobPrivate::handleResponse (this=0x424c1f0, t...@0x7fff577be350, da...@0x7fff577be340) at /var/tmp/portage/kde-base/kdepimlibs-4.3.2/work/kdepimlibs-4.3.2/akonadi/job.cpp:67 #22 0x7f67ccf4d7eb in Akonadi::SessionPrivate::dataReceived (this=0x1ba1a40) at /var/tmp/portage/kde-base/kdepimlibs-4.3.2/work/kdepimlibs-4.3.2/akonadi/session.cpp:121 #23 0x7f67ccf4e071 in Akonadi::Session::qt_metacall (this=0x1bb06b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff577be560) at /var/tmp/portage/kde-base/kdepimlibs-4.3.2/work/kdepimlibs-4.3.2_build/akonadi/session.moc:81 #24 0x7f67e440beb9 in QMetaObject::activate (sender=0x1ba4f20, from_signal_index=value optimized out, to_signal_index=4, argv=0x) at kernel/qobject.cpp:3101 #25 0x7f67e443e14d in
[Bug 211370] New: selecting a big folder (13000 mails) crashed kmail
https://bugs.kde.org/show_bug.cgi?id=211370
Summary: selecting a big folder (13000 mails) crashed kmail
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: arne_...@web.de
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
sadly I have no additional info - aside from the crash report.
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#5 0x7f7ead939205 in raise () from /lib/libc.so.6
#6 0x7f7ead93a723 in abort () from /lib/libc.so.6
#7 0x7f7eae671295 in qt_message_output (msgType=QtFatalMsg, buf=value
optimized out) at global/qglobal.cpp:2042
#8 0x7f7eae6713b0 in qFatal (msg=value optimized out) at
global/qglobal.cpp:2241
#9 0x7f7e9cf72d23 in
KMail::MessageListView::Core::Model::applyFilterToSubtree (this=0x1503b60,
item=0x2ff41b0, parentind...@0x7fff95188890)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:348
#10 0x7f7e9cf7902e in KMail::MessageListView::Core::Model::setFilter
(this=0x1503b60, filter=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:340
#11 0x7f7e9cfa108c in
KMail::MessageListView::Core::Widget::searchTimerFired (this=0x14b87c0)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/widgetbase.cpp:1130
#12 0x7f7e9cc68963 in KMail::MessageListView::Core::Widget::qt_metacall
(this=0x14b87c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fff95188a30)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widgetbase.cpp:119
#13 0x7f7e9cc68a75 in KMail::MessageListView::Widget::qt_metacall
(this=0x698e, _c=27022, _id=6, _a=0x)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widget.cpp:75
#14 0x7f7eae76beb9 in QMetaObject::activate (sender=0x2b0aad0,
from_signal_index=value optimized out, to_signal_index=4,
argv=0x) at kernel/qobject.cpp:3101
#15 0x7f7eae7667b3 in QObject::event (this=0x2b0aad0, e=0x698e) at
kernel/qobject.cpp:1066
#16 0x7f7eaf4fb6dd in QApplicationPrivate::notify_helper (this=0x64a590,
receiver=0x2b0aad0, e=0x7fff95189100) at kernel/qapplication.cpp:4065
#17 0x7f7eaf50400e in QApplication::notify (this=0x7fff95189440,
receiver=0x2b0aad0, e=0x7fff95189100) at kernel/qapplication.cpp:4030
#18 0x7f7eb02cb341 in KApplication::notify (this=0x7fff95189440,
receiver=0x2b0aad0, event=0x7fff95189100)
at
/var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#19 0x7f7eae756d53 in QCoreApplication::notifyInternal
(this=0x7fff95189440, receiver=0x2b0aad0, event=0x7fff95189100) at
kernel/qcoreapplication.cpp:606
#20 0x7f7eae780c46 in QTimerInfoList::activateTimers (this=0x636440) at
kernel/qcoreapplication.h:213
#21 0x7f7eae77de7d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#22 0x7f7ea9d36f41 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7f7ea9d3a4d8 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#24 0x7f7ea9d3a68c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7f7eae77ddef in QEventDispatcherGlib::processEvents (this=0x634630,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:328
#26 0x7f7eaf58728f in QGuiEventDispatcherGlib::processEvents (this=0x698e,
flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x7f7eae755a12 in QEventLoop::processEvents (this=value optimized
out, flags={i = -1793551504}) at kernel/qeventloop.cpp:149
#28 0x7f7eae755bac in QEventLoop::exec (this=0x7fff951893b0, flags={i =
-1793551424}) at kernel/qeventloop.cpp:197
#29 0x7f7eae75a526 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#30 0x0040405a in main (argc=1, argv=0x7fff95189958) at
/var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218
This bug may be a duplicate of or related to bug 211046
Reported using DrKonqi
--
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 211046] New: crash when searching in a folder with many emails
https://bugs.kde.org/show_bug.cgi?id=211046
Summary: crash when searching in a folder with many emails
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: arne_...@web.de
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
I selected a folder with many emails and entered words in the search bar before
any mails were shown.
Kontact crashed before showing any results.
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#33 0x7fa8534af205 in raise () from /lib/libc.so.6
#34 0x7fa8534b0723 in abort () from /lib/libc.so.6
#35 0x7fa8541e7295 in qt_message_output (msgType=QtFatalMsg, buf=value
optimized out) at global/qglobal.cpp:2042
#36 0x7fa8541e73b0 in qFatal (msg=value optimized out) at
global/qglobal.cpp:2241
#37 0x7fa842c10d23 in
KMail::MessageListView::Core::Model::applyFilterToSubtree (this=0x14ce740,
item=0x42a94b0, parentind...@0x7fffd7828180)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:348
#38 0x7fa842c1702e in KMail::MessageListView::Core::Model::setFilter
(this=0x14ce740, filter=value optimized out)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:340
#39 0x7fa842c3f08c in
KMail::MessageListView::Core::Widget::searchTimerFired (this=0x147df80)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/widgetbase.cpp:1130
#40 0x7fa842906963 in KMail::MessageListView::Core::Widget::qt_metacall
(this=0x147df80, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x7fffd7828320)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widgetbase.cpp:119
#41 0x7fa842906a75 in KMail::MessageListView::Widget::qt_metacall
(this=0x66a4, _c=26276, _id=6, _a=0x)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widget.cpp:75
#42 0x7fa8542e1eb9 in QMetaObject::activate (sender=0x64e6670,
from_signal_index=value optimized out, to_signal_index=4,
argv=0x) at kernel/qobject.cpp:3101
#43 0x7fa8542dc7b3 in QObject::event (this=0x64e6670, e=0x66a4) at
kernel/qobject.cpp:1066
#44 0x7fa8550716dd in QApplicationPrivate::notify_helper (this=0x64a530,
receiver=0x64e6670, e=0x7fffd78289f0) at kernel/qapplication.cpp:4065
#45 0x7fa85507a00e in QApplication::notify (this=0x7fffd7828d30,
receiver=0x64e6670, e=0x7fffd78289f0) at kernel/qapplication.cpp:4030
#46 0x7fa855e41341 in KApplication::notify (this=0x7fffd7828d30,
receiver=0x64e6670, event=0x7fffd78289f0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#47 0x7fa8542ccd53 in QCoreApplication::notifyInternal
(this=0x7fffd7828d30, receiver=0x64e6670, event=0x7fffd78289f0) at
kernel/qcoreapplication.cpp:606
#48 0x7fa8542f6c46 in QTimerInfoList::activateTimers (this=0x63ceb0) at
kernel/qcoreapplication.h:213
#49 0x7fa8542f3e7d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#50 0x7fa84f8acf41 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#51 0x7fa84f8b04d8 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#52 0x7fa84f8b068c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#53 0x7fa8542f3def in QEventDispatcherGlib::processEvents (this=0x634770,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:328
#54 0x7fa8550fd28f in QGuiEventDispatcherGlib::processEvents (this=0x66a4,
flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202
#55 0x7fa8542cba12 in QEventLoop::processEvents (this=value optimized
out, flags={i = -679310240}) at kernel/qeventloop.cpp:149
#56 0x7fa8542cbbac in QEventLoop::exec (this=0x7fffd7828ca0, flags={i =
-679310160}) at kernel/qeventloop.cpp:197
#57 0x7fa8542d0526 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#58 0x0040405a in main (argc=1, argv=0x7fffd7829248) at
/var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218
Reported using DrKonqi
--
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 211139] New: opening a draft crashed the mail program and deleted the draft
https://bugs.kde.org/show_bug.cgi?id=211139
Summary: opening a draft crashed the mail program and deleted
the draft
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: arne_...@web.de
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64
What I was doing when the application crashed:
I started kontact and opened an email from drafts.
It died and I can't find the email anymore - anywhere.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 DwEntity::Headers (this=0x41201e00200072) at
/var/tmp/portage/kde-base/mimelib-4.3.2/work/mimelib-4.3.2/mimelib/entity.cpp:241
#6 0x7fafe2cdfa4e in KMMessage::rawHeaderField (this=0x1c6b790,
na...@0x7fff7afe7db0) at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmmessage.cpp:1958
#7 0x7fafe2ce0995 in KMMessage::from (this=0x1c6b790) at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmmessage.cpp:1710
#8 0x7fafe2e93b4e in KMail::FancyHeaderStyle::format (this=value
optimized out, message=0x1c6b790, strategy=0xb8b960,
vcardna...@0x7fff7aff2890, printing=value optimized out, topLevel=true)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/headerstyle.cpp:457
#9 0x7fafe2d89959 in KMReaderWin::writeMsgHeader (this=0x1759f30,
aMsg=0x1c6b790, hasVCard=false, topLevel=false)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmreaderwin.cpp:1783
#10 0x7fafe2d97497 in KMReaderWin::parseMsg (this=0x1759f30,
aMsg=0x1c6b790) at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmreaderwin.cpp:1668
#11 0x7fafe2d8f0de in KMReaderWin::displayMessage (this=0x1759f30) at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmreaderwin.cpp:1605
#12 0x7fafe2d8f2da in KMReaderWin::updateReaderWin (this=0x1759f30) at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/kmreaderwin.cpp:1545
#13 0x7fafe2d927bd in KMReaderWin::qt_metacall (this=0x1759f30,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff7aff30a0)
at
/var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/kmreaderwin.moc:168
#14 0x7faff46b2eb9 in QMetaObject::activate (sender=0x1759fd8,
from_signal_index=value optimized out, to_signal_index=4, argv=0x6d6f72) at
kernel/qobject.cpp:3101
#15 0x7faff46ad7b3 in QObject::event (this=0x1759fd8, e=0x1c6b790) at
kernel/qobject.cpp:1066
#16 0x7faff54426dd in QApplicationPrivate::notify_helper (this=0x64a530,
receiver=0x1759fd8, e=0x7fff7aff3770) at kernel/qapplication.cpp:4065
#17 0x7faff544b00e in QApplication::notify (this=0x7fff7aff3ab0,
receiver=0x1759fd8, e=0x7fff7aff3770) at kernel/qapplication.cpp:4030
#18 0x7faff6212341 in KApplication::notify (this=0x7fff7aff3ab0,
receiver=0x1759fd8, event=0x7fff7aff3770)
at
/var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#19 0x7faff469dd53 in QCoreApplication::notifyInternal
(this=0x7fff7aff3ab0, receiver=0x1759fd8, event=0x7fff7aff3770) at
kernel/qcoreapplication.cpp:606
#20 0x7faff46c7c46 in QTimerInfoList::activateTimers (this=0x63ceb0) at
kernel/qcoreapplication.h:213
#21 0x7faff46c4e7d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#22 0x7fafefc7df41 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7fafefc814d8 in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#24 0x7fafefc8168c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7faff46c4def in QEventDispatcherGlib::processEvents (this=0x634770,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:328
#26 0x7faff54ce28f in QGuiEventDispatcherGlib::processEvents
(this=0x41201e00200072, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#27 0x7faff469ca12 in QEventLoop::processEvents (this=value optimized
out, flags={i = 2063546848}) at kernel/qeventloop.cpp:149
#28 0x7faff469cbac in QEventLoop::exec (this=0x7fff7aff3a20, flags={i =
2063546928}) at kernel/qeventloop.cpp:197
#29 0x7faff46a1526 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#30 0x0040405a in main (argc=1, argv=0x7fff7aff3fc8) at
/var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218
Reported using DrKonqi
--
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
[Bug 209319] New: GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management)
https://bugs.kde.org/show_bug.cgi?id=209319 Summary: GnuPG: automatically attach my public key and the public key from all receivers - also automatically import attached public keys (decentral key management) Product: kmail Version: 1.12.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.12.1 (using 4.3.1 (KDE 4.3.1), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.30-hh2 I'd love to be able to tell KMail to automatically attach my public GnuPG key and all public GnuPG keys of the receivers to each email I send (and sign/encrypt). Along with the option to automatically import any attached GnuPG key, that would open the possiblity of using GnuPG without the need for central keyservers: If I sign a key, its owner will automatically get the updated version once he gets an email from me. And since GnuPG keys aren't verified via I have it but via the web of trust, this would be completely safe. No longer needing the keyservers would also alleviate a privacy concern. Currently people can find the people who verified my key by getting my key from a keyserver. By doing key spreading and signature merging decentrally (by sending mails), this type of analysis will become much less threatening, since the data will very likely be incomplete. People would have to get the public key directly from me or from some of their contacts to be able to do a signer-analysis - and they couldn't easily broaden it by getting the signed keys from my signers from the servers. All this can be accomplished by adding the two options always attach my public key and the keys of all public receivers (only TO and CC!) and always import attached GnuPG keys. Best wishes, Arne -- 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 206935] plan text markup: *foo*, doesn't show foo in bold (punctuation)
https://bugs.kde.org/show_bug.cgi?id=206935 --- Comment #4 from Arne Babenhauserheide arne_bab web de 2009-09-17 07:55:21 --- Thank you! And a big thank you to Julien, too! -- 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 169132] Kmail dies ungracefully when out of disk space (losing settings and mail data)
https://bugs.kde.org/show_bug.cgi?id=169132 --- Comment #23 from Arne Babenhauserheide arne_bab web de 2009-09-15 15:18:57 --- Many thanks! But could KMail instead warn that the disk is full and stop disk activity but give the user time to free some space. -- 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 206935] New: plan text markup: *foo*, doesn't show foo in bold (punctuation)
https://bugs.kde.org/show_bug.cgi?id=206935 Summary: plan text markup: *foo*, doesn't show foo in bold (punctuation) 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: arne_...@web.de Version: 1.12.1 (using 4.3.1 (KDE 4.3.1), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.30-hh2 I really can't say much more than the title, except that I'd love to see the option to also use different markup engines (for example markdown) which really is off topic... and: Many thanks for kmail and kontact! -- 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 206935] plan text markup: *foo*, doesn't show foo in bold (punctuation)
https://bugs.kde.org/show_bug.cgi?id=206935 --- Comment #2 from Arne Babenhauserheide arne_bab web de 2009-09-11 07:07:29 --- Wow, great! Many 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 199164] New: crash when starting again after adding old addressbook resources and then trying to add an address
https://bugs.kde.org/show_bug.cgi?id=199164 Summary: crash when starting again after adding old addressbook resources and then trying to add an address Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Application that crashed: kontact Version of the application: 4.3.0 rc1 KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) Qt Version: 4.5.2 Operating System: Linux 2.6.29-hh2 x86_64 What I was doing when the application crashed: I went into addressbook and enabled the old resources, because the Akonadi compatiblility resoruce didn't show my contacts. Then I switched back to kmail and added a contact. The first addition worked (but slow), but the second froze kontact and I finally closed the window. When I tried to start kontact again it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f676959d878 in KABC::AddressBook::loadingHasFinished () from /usr/lib64/libkabc.so.4 #5 0x7f676a930faa in KPIM::KAddrBookExternal::addAddressee () from /usr/lib64/libkdepim.so.4 #6 0x7f676a932510 in KPIM::KAddrBookExternal::addEmail () from /usr/lib64/libkdepim.so.4 #7 0x7f6754983faa in KMMailtoAddAddrBookCommand::execute () from /usr/lib64/libkmailprivate.so.4 #8 0x7f675497d6fa in KMCommand::slotPostTransfer () from /usr/lib64/libkmailprivate.so.4 #9 0x7f675498728e in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #10 0x7f6765fb0f15 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #11 0x7f675497a94e in KMCommand::messagesTransfered () from /usr/lib64/libkmailprivate.so.4 #12 0x7f6754996128 in KMCommand::transferSelectedMsgs () from /usr/lib64/libkmailprivate.so.4 #13 0x7f675499634e in KMCommand::slotStart () from /usr/lib64/libkmailprivate.so.4 #14 0x7f67549872a2 in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #15 0x7f6765fb0f15 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7f6765fb72ef in ?? () from /usr/lib64/qt4/libQtCore.so.4 #17 0x7f6765fad843 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7f6766ae9b3d in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #19 0x7f6766af240a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #20 0x7f6767863bbb in KApplication::notify () from /usr/lib64/libkdeui.so.5 #21 0x7f6765f9f033 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f6765fc6eee in ?? () from /usr/lib64/qt4/libQtCore.so.4 #23 0x7f6765fc3c8d in ?? () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7f67615e8fe1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x7f67615ec6bd in ?? () from /usr/lib/libglib-2.0.so.0 #26 0x7f67615ec87b in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x7f6765fc3bff in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #28 0x7f6766b6ee6f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #29 0x7f6765f9da32 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7f6765f9dbcc in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #31 0x7f6765f9fbc4 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #32 0x00404b51 in _start () This bug may be a duplicate of or related to bug 178986 Reported using DrKonqi -- 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 194951] New: slow (almost unresponsive) after startup when checking for new mail when kmail already manages very many emails (100, 000)
https://bugs.kde.org/show_bug.cgi?id=194951 Summary: slow (almost unresponsive) after startup when checking for new mail when kmail already manages very many emails (100,000) Product: kmail Version: 1.11.3 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.11.3 (using 4.2.3 (KDE 4.2.3), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.29-hh2 I have about 100,000 emails in my account (at least that's what find .kde/share/apps/kmail/mail says), and when I check for new mail after kmail started, it becomes so slow that it's almost unresponsive. Some time after the mails are downloaded it gets back to normal (nice) speed. Subsequent checking for new mail also has a speed penalty, but not as severe as the first check after startup. For me this means that I can't just fire up kmail to quickly check my mail. Instead I have to either keep it running at all times or go fetch something to eat/drink after telling it to check my mail (or idling in front of the computer). Note: du -h .kde/share/apps/kmail/mail reports over 3 GiB. -- 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 191209] New: right-click on a folder shouldn't show it's contents but only open the right-click menu (for performance)
https://bugs.kde.org/show_bug.cgi?id=191209 Summary: right-click on a folder shouldn't show it's contents but only open the right-click menu (for performance) Product: kmail Version: 1.11.2 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: arne_...@web.de Version: 1.11.2 (using 4.2.2 (KDE 4.2.2), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS:Linux (x86_64) release 2.6.27-gentoo-r8 I often work under considerable load, and often I just want to say send outbox now. kmail then first shows the outbox, which can take some time when your computer is in massive overload :) For that I would prefer having a right-click not show the folder contents (or having an option to specify the right-click behaviour). When I right-click I only want to see the right-click menu. This is also useful for simply saying mark all as read and delete all, because showing a folder with a massive amount of messages can take quite some time. Best wishes, Arne -- 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
