https://bugs.kde.org/show_bug.cgi?id=371971
--- Comment #10 from Claudius Ellsel <claudius.ell...@live.de> --- (In reply to Cristiano Guadagnino from comment #9) > Thank you Claudius for looking into this. > So you think I should change the "product" field in this bug to point to > kwin instead of yakuake? That might be one option. Probably it is better to open a new bug there, though for the reasons you mentioned below. > I'm not so sure about this... I have no evidence that kwin is involved, why > do you think it is so? I was reading the kwin bug. It looked like both problems - the one described there and the problems with Yakuake - appeared at the same time? Also you wrote that the fix did not cover the Yakuake problem. How would it be able to cover Yakuake if it was unrelated? > Besides, I'm not even the original bug creator... event though I see that > Fedor is not replying anymore, probably he has lost interest. Yes, I see that. It might even be that your bug is different from what Fedor is/was experiencing. Since we cannot say that for sure, probably it is best to create a new bug for KWin and describe your issue there again and link to this bug report. If it turns out to not be caused by KWin, the bug can be closed or moved to the right product again. However, I doubt this is just Yakuakes fault, so in order to get this fixed, imho it makes sense to have a bug for the correct product filed, so the maintainers there are aware of it. -- You are receiving this mail because: You are watching all bug changes.
