Hello. Everything works great when I work on my laptop without external monitor attached. However, when second monitor is attached (the output is NOT unified), the global hotkey F12 only works if the mouse pointer is located on the laptop screen. If pointer is located on the external monitor, hitting F12 does nothing. I would prefer for F12 to work wherever pointer is located and open the terminal on the same display as the pointer. Is there any way to fix this for me? Thank yo-u in advance. PS: KDE Frameworks 5.27.0 Qt 5.7.0 (built against 5.7.0) The xcb windowing system
I am seeing this too. Yakuake works on my primary monitor, but not on the secondary. I remember this feature working months ago. Interestingly, it stopped working when a KDE bug was discovered that made it impossible to drag windows on the second monitor if a panel was put vertically between the two monitors (I do not remember the bug number, but it's resolved now). I believe that the way that bug was fixed left Yakuake out in the cold. I made this remark on that bug too, but nobody responded. I'll see if I can find that bug and I'll report it here. @Fedor: do you have a vertical panel between the two screens?
Forgot to add: Yakuake v3.0.5 KDE Frameworks 5.44.0 Qt 5.10.0 (built against 5.10.0) The xcb windowing system
I found the bug I was talking about. Here it is: https://bugs.kde.org/show_bug.cgi?id=371199 However, nobody cared about my remarks on yakuake. Maybe I'm wrong and it is not related, but the fact that the two problems appeared simultaneously make me think it is.
I can confirm my suspects, as moving the panel to the right side of the right monitor (it was previously "between" the two monitors) fixes the problem. So this bug is related to bug 371199 (https://bugs.kde.org/show_bug.cgi?id=371199). Is it possible to implement a workaround in Yakuake?
Is this still happening?
Unfortunately yes :-(
Now I'm using Yakuake 20.08.0 KDE Frameworks 5.73.0 Qt 5.15.0 (built against 5.15.0) And it still happens.
Alright. Having a closer look, as you mentioned the bug is related to having a vertical panel in between the monitors. Also I read bug 371199. The root cause might be the same. However, I think that since the original bug there described a different problem one has to track this in a different one now. Since this might be kwin related, it might make sense to move it there or create a bug report there.
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? I'm not so sure about this... I have no evidence that kwin is involved, why do you think it is so? Besides, I'm not even the original bug creator... event though I see that Fedor is not replying anymore, probably he has lost interest.
(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.
(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? > I'm not so sure about this... I have no evidence that kwin is involved, why > do you think it is so? > Besides, I'm not even the original bug creator... event though I see that > Fedor is not replying anymore, probably he has lost interest. Sorry for not repling -- kinda did not notice the notification until this burst of comments.(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? > I'm not so sure about this... I have no evidence that kwin is involved, why > do you think it is so? > Besides, I'm not even the original bug creator... event though I see that > Fedor is not replying anymore, probably he has lost interest. Sorry for not replying -- I kinda did not notice the notifications. I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, KDE Frameworks 5.70.1 and Qt 5.14.2.
(In reply to Claudius Ellsel from comment #10) > (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. Wait, I did not explain well... I *am* convinced that the problem lies in kwin, exactly for the reasons you just explained. But, as you can see in bug 371199, the developer was not of the same idea and in fact we had a little discussion towards the end of the comment thread, for the fact that I had reopened the bug. So my question to you was intended to understand if you had any more evidence of the fact that the problem is rooted in kwin. Anyway, I think I'm going to try to open a new bug for kwin, let's see how it goes.
(In reply to Fedor Gusev from comment #11) > I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, > KDE Frameworks 5.70.1 and Qt 5.14.2. So are you saying that, in the same condition (two monitors, panel on the left side of the right monitor) Yakuake opens on the monitor where you happen to have the mouse pointer, even if it is the left monitor?
(In reply to Fedor Gusev from comment #11) > Sorry for not replying -- I kinda did not notice the notifications. > > I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, > KDE Frameworks 5.70.1 and Qt 5.14.2. No problem, thanks for getting back :) Do you remind whether you had a vertical panel like Cristiano back then? Else you might have experienced a different bug. Either one that got fixed already or one with a different cause (Wayland - does not seem to be the case, scaling, ...).
(In reply to Cristiano Guadagnino from comment #12) > Wait, I did not explain well... I *am* convinced that the problem lies in > kwin, exactly for the reasons you just explained. > But, as you can see in bug 371199, the developer was not of the same idea > and in fact we had a little discussion towards the end of the comment > thread, for the fact that I had reopened the bug. I read the discussion in bug 371199. I guess you misunderstood the developer there. The point was that the bug was treating a different problem. The root cause might have been the same like what you experience with Yakuake, but the bug report was about something different. That got fixed, so the bug has been closed (and for this reason also should not be reopened). Also I think you were advised back then that you can open a new bug there for your specific problem. The communication was probably not that ideal and I can see why you might have misunderstood that statement. > So my question to you was intended to understand if you had any more > evidence of the fact that the problem is rooted in kwin. No, I don't have any more evidence. > Anyway, I think I'm going to try to open a new bug for kwin, let's see how > it goes. Nice. Make sure to reference it :)
(In reply to Claudius Ellsel from comment #14) > (In reply to Fedor Gusev from comment #11) > > Sorry for not replying -- I kinda did not notice the notifications. > > > > I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, > > KDE Frameworks 5.70.1 and Qt 5.14.2. > > No problem, thanks for getting back :) > > Do you remind whether you had a vertical panel like Cristiano back then? > Else you might have experienced a different bug. Either one that got fixed > already or one with a different cause (Wayland - does not seem to be the > case, scaling, ...). No, I don't think I ever had a panel on the side. However, now if I move the panel on left monitor to the left side of that monitor, then the hotkey does not work on the right monitor (like Cristiano, I guess). So I can reproduce his bug. And I think that you're right -- my bug is fixed somehow, but his bug is a completely different one.
(In reply to Fedor Gusev from comment #16) > (In reply to Claudius Ellsel from comment #14) > > (In reply to Fedor Gusev from comment #11) > > > Sorry for not replying -- I kinda did not notice the notifications. > > > > > > I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, > > > KDE Frameworks 5.70.1 and Qt 5.14.2. > > > > No problem, thanks for getting back :) > > > > Do you remind whether you had a vertical panel like Cristiano back then? > > Else you might have experienced a different bug. Either one that got fixed > > already or one with a different cause (Wayland - does not seem to be the > > case, scaling, ...). > > No, I don't think I ever had a panel on the side. > > However, now if I move the panel on left monitor to the left side of that > monitor, then the hotkey does not work on the right monitor (like Cristiano, > I guess). So I can reproduce his bug. And I think that you're right -- my > bug is fixed somehow, but his bug is a completely different one. To state this more correctly: I always use a horizontal panel on the top, never vertical panels on the right or left side.
(In reply to Fedor Gusev from comment #16) > (In reply to Claudius Ellsel from comment #14) > > (In reply to Fedor Gusev from comment #11) > > > Sorry for not replying -- I kinda did not notice the notifications. > > > > > > I cannot confirm this bug anymore. I am currently running yakuake 20.04.1, > > > KDE Frameworks 5.70.1 and Qt 5.14.2. > > > > No problem, thanks for getting back :) > > > > Do you remind whether you had a vertical panel like Cristiano back then? > > Else you might have experienced a different bug. Either one that got fixed > > already or one with a different cause (Wayland - does not seem to be the > > case, scaling, ...). > > No, I don't think I ever had a panel on the side. > > However, now if I move the panel on left monitor to the left side of that > monitor, then the hotkey does not work on the right monitor (like Cristiano, > I guess). So I can reproduce his bug. And I think that you're right -- my > bug is fixed somehow, but his bug is a completely different one. Alright. Thanks for your efforts. Then this bug can be closed. I will wait until Cristiano has opened his bug on KWin (also small correction, he was not asked to do that on the other KWin bug, unfortunately). Maybe also another bug to track the specific problem of Cristiano for Yakuake might make sense, I don't know. Since this bug has never been about vertical panels, that should be treated somewhere else then to not mix different problems.
(In reply to Claudius Ellsel from comment #18) > Alright. Thanks for your efforts. Then this bug can be closed. I will wait > until Cristiano has opened his bug on KWin (also small correction, he was > not asked to do that on the other KWin bug, unfortunately). Maybe also > another bug to track the specific problem of Cristiano for Yakuake might > make sense, I don't know. Since this bug has never been about vertical > panels, that should be treated somewhere else then to not mix different > problems. Claudius, sorry for the long delay. I have not had time to create the KWin bug, but today I discovered that Yakuake is working again in my setup!! I do not know if the recent activity in this bug got noticed by someone who was able to fix it, but nevertheless it works now!!
@Cristiano: No problem. If this happens again for you, feel free to report a new bug for the specific problem you experienced. Since the original bug seems to no longer appear, I will close this now. @Fedor or anybody else experiencing this original bug: feel free to reopen if it occurs again or create a new bug.