David Southwell schrieb: > Current report found at: http://bugs.kde.org/show_bug.cgi?id=149003 > Previous report found at: http://bugs.kde.org/show_bug.cgi?id=147358 > > As you will see from the dialogue there seem to be some resistance amongst > kde > developer team to take this bug seriously. They are inclided to suggest this > is a freebsd problem (despite evidence that the same problem occurs on > linux!!!). > > They seem pretty insistant that I should seek help from freebsd ports to help > identify the cause although I do not know what more I can do apart from > providing the gdb trace. > I am really sorry that you are having the misfortune of experiencing the worst possible open source tech support scenario. :( There are many things that are coming together here I think, and they all add up to your disadvantage:
- The kmail developers are all Linux users and like to treat bugs reported on FreeBSD as low priority, since they are quite swamped in bugs already. - The resources of the kmail developers are spread even thinner due to the upcoming KDE 4 release. - Neither the kmail developers nor me or apparently anyone else on this list can reproduce this bug. Again, I am terribly sorry. I understand how frustrating this experience is. That said, I read the bug again and the part of KDE/X not responding to input at all reminded me of something else: I assume you are using gpg-agent and a pinentry utility - can you check if you have a ~/.gnupg/gpg-agent.conf file (if not, create one) and add the line no-grab to it and see if that makes any difference? Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org _______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
