https://bugs.kde.org/show_bug.cgi?id=308068
--- Comment #5 from Josep <[email protected]> --- I think that since kmail and blender are executed by the same user, with the same privileges, and depending on what the exact problem is, it may not be easy preventing blender from disturbing kmail. When I reported the bug, I was aware that it could be a blender bug, or even a dbus bug, but, as I see it, it's kmail that is being affected, and the only practical way to find out what is happening, I think, is tracing back the problem from kmail misbehaviour (or from bug 308491, which seems to be almost the same problem) to its source and, should be discovered that blender overwrites some file, or some variable, or whatever when it shouldn't (or maybe dbus doesn't protect some data when it should, or some other non KDE related problem), then that can be reported as a bug to the program developers. But if I report the bug to blender (or dbus) developers, with just the little information I have now, I doubt they will be able to find what's wrong, since probably they would need first to get familiar with KDE code, and so, I suspect kmail will continue to have this problem for a long time. On the other hand, if I can tell blender (or dbus) developers that the problem is, say, that some variable that should have been left alone is overwritten when blender starts, then it is much more likely that the bug will be fixed quickly. My point is that, even if the bug is not necessarily kmail's fault (and remember that the bug could be too in some KDE library, for all we know), the only practical way I can see to debug it is by finding how this misbehaviour is triggered in kmail, and reporting those finds to the developers of the guilty program, if it's not kmail. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
