| Summary: | [wayland - upstream] - Latte Dock 0.9 Is faulty auto-hiding with the cursor on it after a second | ||
|---|---|---|---|
| Product: | [Plasma] lattedock | Reporter: | Alberto Díaz López <takuya> |
| Component: | plasmoid | Assignee: | Michail Vourlakos <mvourlakos> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fondatommaso2 |
| Priority: | NOR | ||
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Latte Dock Layout File | ||
|
Description
Alberto Díaz López
2019-07-30 14:59:20 UTC
I can not reproduce this in my system, please send your layout file Created attachment 121843 [details]
Latte Dock Layout File
Added my daily usage Latte Dock layout file.
I can reproduce, the suspect probably is GhostWindowScreenEdge and I must investigate the case Ok, I investigated this... You can blame Qt, under wayland the hidden window changes its mask and the QEvent::Leave signal is not sent always... In my system is a hit and miss To occur the mouse must remain at the exact far edge of the screen and sometimes it occurs and sometimes it does not. is it possible to check if this still possible with master version? This still happens on the latest version packaged in openSUSE Tumbleweed. I can provide more info if needed. Thanks. (In reply to Tommaso Fonda from comment #7) > This still happens on the latest version packaged in openSUSE Tumbleweed. I > can provide more info if needed. > Thanks. As described earlier, this is Qt issue not sending a signal. (In reply to Michail Vourlakos from comment #6) > is it possible to check if this still possible with master version? Yeah, sure. I just downloaded the code from the GitHub mirror, installed it and it looks like it's still the same (or maybe Latte Dock needs a relaunch). But, if i'm doing it right, the bug still persists. I still have the version that Arch Linux packages (currently, still 0.9.8.1, so i'm not sure if i'm doing anything wrong to run the master one). I would be grateful if you provide me information if i'm doing right or not, and if not, how could i do it the right way. Thank you very much. There is no fix for this from Latte side... Last time I investigated this, it was Qt fault under wayland... I just hoped that Qt 5.14 might solved it. (In reply to Michail Vourlakos from comment #10) > There is no fix for this from Latte side... Last time I investigated this, > it was Qt fault under wayland... I just hoped that Qt 5.14 might solved it. I see, then shouldn't we report it to Qt? I have reported a few bugs and at least on one of them, the issue come because of Qt (like this one) and the bug scaled to Qt, which was finally solved a few months ago. (In reply to Alberto Díaz López from comment #11) > (In reply to Michail Vourlakos from comment #10) > > There is no fix for this from Latte side... Last time I investigated this, > > it was Qt fault under wayland... I just hoped that Qt 5.14 might solved it. > > I see, then shouldn't we report it to Qt? > > I have reported a few bugs and at least on one of them, the issue come > because of Qt (like this one) and the bug scaled to Qt, which was finally > solved a few months ago. Yep, that should be the case but someone must find a way to reproduce it in a simple way with plain Qt and take up the task to report and interact for feedback, personally no time for this. is this reproducable to 0.10.1? (In reply to Michail Vourlakos from comment #13) > is this reproducable to 0.10.1? No, you're right, sorry, I should have closed this a few time ago. Thanks for your hard & great work on Latte Dock, 0.10.x is awesome and it improved a lot since 0.9.x branch :). |