Summary: | Kmail drag and drop of messages to folders stops working if blender has been started | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Josep <jgue> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | minor | CC: | cfeck, montel, philipp, sonichedgehog_hyperblast00 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Josep
2012-10-08 10:41:29 UTC
I can confirm this issue. Started kmail; can move mails to different folders; start blender; cannot drag anymore, in running kmail instance. Note: logout and login (via KDM) "fixes" the problem - until blender is started again... That started only 2 months ago or so (running now debian on amd64, kmail 1.13.7, kde 4.8.4); are there any more details I can offer to hunt that down? I am pretty sure it is a Blender bug, because it is not only KMail that is affected, see bug 308491. But if kmail lets itself disturb by other programs in this way, I'd see it as a bug in kmail, too. Well, how can I see what the cause for the problem is? Trace dbus? 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. If it's not just kmail which is affected I report it to kdelibs As found out in bug 308068, this a Blender bug. Of course I meant bug 308491 :) Blender 2.65 came out so I updated my binaries. I can confirm that after opening Blender, drag and drop support no longer breaks on my KDE desktop, so the problem is solved. I can confirm too that with blender 2.65 the issue disappeared in kmail. Thanks to everyone involved! |