Community
Participate
Working Groups
Created attachment 274704 [details] Image of display corruption showing border offset in editor on the right. I'm running Photon 4.8.0 build 20180619-1200 in an Umbuntu 16.04 Virtual Machine under VirtualBox 5.2.12r122591(Qt5.6.2) running on a Windows 10 Pro 64 Bit 1709 build 16299.492 Host. When editing a PHP file with PHP editor, if I insert a new line or delete one at times I get corruption of the display as shown in the attached image where an area of the display is replicated in the current editor. The part that is replicated is from the right and displays over the current editor. This area is returned to normal when highlighting the corrupted area, scrolling the content, or selecting another editor. This problem did not exist before updating to Photon. I was previously running Neon. I normally run VirtualBox in seamless display mode but this happens in any other display mode for VitrualBox. Note that I do not run Eclipse natively on any system, only under VirtualBox, so I can't test that way.
Created attachment 274705 [details] Closer view of problem
This seems an SWT issue.
Duplicate of bug 536458? Note that 536458 was reported against CDT on Windows. So if it's SWT, it's probably in the platform-independent part. There have been many changes in StyledText in Photon.
Per the reference in 536458 to using Env SWT_GTK3=0, I checked any I do have that set and still have the display corruption problem. I believe I set that Env variable some time ago for a similar problem with an earlier version of Eclipse.
It turns out that having SWT_GTK3=0 was preventing my system from working correctly. Switching that to force GTK3 (SWT_GTK3=1) seems to have solved the problem with display corruption.
(In reply to Charles Scott from comment #5) > It turns out that having SWT_GTK3=0 was preventing my system from working > correctly. Switching that to force GTK3 (SWT_GTK3=1) seems to have solved > the problem with display corruption. Okay, thanks for following up. Please reopen this ticket if you see the issue on GTK3.
