GNOME Bugzilla – Bug 607753
Appointment tooltip sometimes 'stick' to screen
Last modified: 2016-02-23 15:07:31 UTC
When you hover over an appointment in Evo's calendar section, it pops up some details about the appointment. With Evo 2.29.5 on my system, sometimes these popups get 'stuck' and never disappear until I close Evo. They stick over the top of everything, even other applications' windows. Never saw this with 2.28 or earlier. Fedora Rawhide. Will attach screenshot.
Created attachment 152000 [details] screenshot of the bug
I've noticed tooltips over canvas widgets like the calendar and task list don't set a "tip area" or bounding rectangle for the tooltip (via gtk_tooltip_set_tip_area()), so moving the pointer over the same item makes the tooltip redraw like crazy because the "tip area" is the exact pixel you're pointing at. This bug might be another side-effect of that.
I'm wondering how this is possible, because it doesn't want to stick it there for me. But I recall seeing it on older versions too, though very rarely. Might be something with update on your remote calendar. What is your refresh interval there? Or even better do you have any hints what to do or what happened in time of "forgotten" tooltip? Say a new event arrived from the server or any was deleted, or something like that.
What I was doing when I got the screenshot in question was going through and deleting a bunch of duplicate events that had got onto the server while I was screwing with various synchronization bits. You can see several of the dupes in the screenshot. I was just going from event to event, right-clicking and deleting each one. Several times through this process, the event info pop-up appeared before I got to the actual deletion, and sometimes the pop-up remained. Nothing should have changed on the server at the time besides the deletion of events that I was doing. My sync interval is 5 minutes.
Since the "tip area" is a single pixel, it might be that GTK+ is missing signals it would ordinarily use to clear the tooltip. Haven't looked into it yet though so I'm just speculating.
Hrm, I cannot reproduce it on a recently released 2.29.90
I finally managed to reproduce this and hopefully fixed it too (it's fixed for me, but as I had some issues with reproducibility in the past I cannot be 100% sure). Created commit 6765ed1 in evo master (3.13.4+) [1] Created commit 25b6704 in evo evolution-3-12 (3.12.4+) [1] https://git.gnome.org/browse/evolution/commit/?id=6765ed1
awesome! sorry I wasn't able to provide a convenient reproducer.
A follow-up change: https://git.gnome.org/browse/evolution/commit/?id=8d2e134
*** Bug 220286 has been marked as a duplicate of this bug. ***