Bug 46793 - Popups in Omnet++ simulator stay on screen (repaint failure)
Summary: Popups in Omnet++ simulator stay on screen (repaint failure)
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-29 12:14 UTC by Da Fox
Modified: 2013-10-02 11:31 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Da Fox 2012-02-29 12:14:51 UTC
Sometimes tooltip/autocomplete popups in the Omnet++ editor (which is really just eclipse) fail to 'go away'. The following screenshot shows the problem: http://en.zimagez.com/zimage/screenshot-02292012-050336pm.php# . In the tooltip in this screen the bottom part has disappeared, but the top part remained on screen (you can see the very tops of the letters of the next line at the bottom of the tooltip, and the lack of the black 1px border).

Clicking on a line obscured by the remainder of the tooltip causes that line (but only that line) to be properly repainted.

This issue can be reproduced as follows:
 - Get a popup to show in the editor (as shown in the screenshot)
 - While the popup shows, scroll the window contents up or down (use the mouse-wheel)
 - The popup will (should) partially remain on screen instead of disappearing.



My hardware is a Dell XPS 15 (L502x) laptop with:
00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09)
[    13.803] (II) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge
Mobile (GT2)

Software versions:
Mesa: 15e60d9976f82174afeca1d026f566cb8aea5104
xf86-video-intel: a3c398a6731874ba47e0a46bbd42bf9378e12ab8 (with sna).
x11-base/xorg-server-1.11.2-r2 (gentoo)
libdrm: 783db34f6d8aded019b005a957fed1b91fd67c7c
dri2proto: 7fd18b15646a62bd82a4eb0eca60a34c1731813d
Comment 1 Chris Wilson 2012-02-29 14:29:16 UTC
With compositing? xorg-server-1.11.2 is known to be buggy with compositing after a modeswitch (which can happen just by logging in).
Comment 2 Da Fox 2012-02-29 22:00:09 UTC
(In reply to comment #1)
> With compositing? xorg-server-1.11.2 is known to be buggy with compositing
> after a modeswitch (which can happen just by logging in).

Without, compositing is still turned off due to bug #37686. I think it happens also on a clean login, but I don't know how to tell if this involves a modeswitch. It certainly happens /after/ a modeswitch (suspend to disk/ram) though. 

Would it help to try this by starting X with 'startx' (since I don't have compositing enabled)?
Comment 3 Da Fox 2012-03-05 00:52:10 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > With compositing? xorg-server-1.11.2 is known to be buggy with compositing
> > after a modeswitch (which can happen just by logging in).
> 
> Without, compositing is still turned off due to bug #37686. I think it happens
> also on a clean login, but I don't know how to tell if this involves a
> modeswitch. It certainly happens /after/ a modeswitch (suspend to disk/ram)
> though. 
> 
> Would it help to try this by starting X with 'startx' (since I don't have
> compositing enabled)?

I had the opportunity, so I tried this anyway. I booted with the 'nox' option to prevent X from starting automatically, then logged in to a console and executed 'startx'. 
Under these conditions the issue is still present and easily reproduced using the step above.
Comment 4 Chris Wilson 2012-03-14 04:20:10 UTC
I suspect this is related to:

commit 6dfe28f978b59ab2fc44cdd8ddf3743d6507588b
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Mar 13 15:47:27 2012 +0000

    sna/gen6: Remove the double application of the render offset
    
    Cut'n'paste error from an older generation.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Can you please retest with current xf86-video-intel.git?
Comment 5 Da Fox 2012-03-16 02:07:33 UTC
(In reply to comment #4)
> I suspect this is related to:
> 
> commit 6dfe28f978b59ab2fc44cdd8ddf3743d6507588b
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Tue Mar 13 15:47:27 2012 +0000
> 
>     sna/gen6: Remove the double application of the render offset
> 
>     Cut'n'paste error from an older generation.
> 
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> Can you please retest with current xf86-video-intel.git?

I just tested with fe4ad66aadcfa0c907ba6460a88c49e65225602c and the issue can still be reproduced with the steps described above.
Comment 6 Da Fox 2012-04-23 09:00:56 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > I suspect this is related to:
> > 
> > commit 6dfe28f978b59ab2fc44cdd8ddf3743d6507588b
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date:   Tue Mar 13 15:47:27 2012 +0000
> > 
> >     sna/gen6: Remove the double application of the render offset
> > 
> >     Cut'n'paste error from an older generation.
> > 
> >     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > 
> > Can you please retest with current xf86-video-intel.git?
> 
> I just tested with fe4ad66aadcfa0c907ba6460a88c49e65225602c and the issue can
> still be reproduced with the steps described above.

Open-office might also be affected by this bug, and easier to test:
http://www.zimagez.com/zimage/screenshot-04232012-054727pm.php

On the right side, next to the scrollbar you can see some square yellowish artifacts. These seem to be left by the tooltip that pops up when you move the scrollbar by dragging it with the mouse (it shows the current row). It may be necessary to move the mouse quickly to make the artifacts appear.
Comment 7 Chris Wilson 2012-06-15 04:27:28 UTC
Tons of little fixes with quite a few in damage tracking that may be of note. Do you still see the unredrawn areas on the screen?
Comment 8 Chris Wilson 2012-07-04 10:55:51 UTC
Ping?
Comment 9 Da Fox 2012-07-08 05:57:15 UTC
(In reply to comment #8)

Just tested with xf86-video-intel 5d2f88fd9972c62c87098ddc7fee7b6f0cea0fdb .
This no longer seems to happen with the OpenOffice scrollbar/tooltip.
The autocomplete popups in omnet however still fail to 'unpaint' properly.

> Ping?
Sorry about the huge ping :)
Comment 10 Chris Wilson 2012-07-08 06:05:00 UTC
Does a screenshot capture the omnet popup bug?
Comment 11 Da Fox 2012-07-09 11:47:21 UTC
(In reply to comment #10)
> Does a screenshot capture the omnet popup bug?

There is a screenshot in comment #1 (the bottom half of the popup has disappeared, but the top half remains). So, yes, it can be captured on a screenshot.
Comment 12 Chris Wilson 2012-12-12 12:21:30 UTC
Been a while since I've heard whether this is still an issue.
Comment 13 Da Fox 2013-01-09 20:12:23 UTC
(In reply to comment #12)
> Been a while since I've heard whether this is still an issue.

Still happens with open office, but it takes a bit of effort:
When quickly scrolling the OOCalc sheet (you can do this with an empty sheet), I can sometimes see a bit of corruption similar to that in the screenshot from Comment 6. This however seems to clear up by the time you stop scrolling. Occasionally a bit of the tooltip still remains though.

The best way I've found to trigger this is to cause the tooltip to move while scrolling. The tool tip will move to stay out from under your cursor. Here's what I mean:
1) Click-hold the scrollbar.
2) Slowly start scrolling.
3) The tooltip will appear.
4) While scrolling up/down, try to move your mouse over the tooltip.
5) The tooltip will move out of the way.

The easiest way to do that quickly is to move your mouse in circles a little bit while scrolling (or use a trackpad ;).
I think the bug is most likely to trigger when you scroll the currently selected cell in/out of view.


Alas I no longer have access to the Omnet software, so I cannot test that (the issue was much more pronounced and hence annoying there though).
Comment 14 Chris Wilson 2013-10-02 11:31:31 UTC
I have this theory that by closing this bug will cause 20 people to suddenly spot it - including myself...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.