Burp Overlay Menus no longer Working on Fedora 26
with Burp version 1.7.31 the overlay menus (like the proxy filter menu) are instantly closing as soon as one clicks on it. It is confirmed working with Burp version 1.7.27.
Oracle java version: 1.8.0_162-b12
run command: java -Dawt.useSystemAAFontSettings=on -Dsun.java2d.d3d=false -Dsun.java2d.xrender=false -jar
Have you tried using the latest version of Oracle Java?
Or using the platform installer version of Burp Suite?
version 1.8.0_162-b12 is already the latest version (as Java 9 is not yet fully supported). A colleague of mine seems to have the exact opposite problem with the latest version (menus can't be closed anymore). The functionality worked perfectly till version 1.7.28 and stopped working with version 1.7.29
I tried OpenJDK 8 latest version, Oracle JDK 8 latest version and the packaged jre version. None work with version 1.7.29 or greater.
Thanks for the additional information. We’ll try and reproduce this issue.
Thanks for keeping us updated.
We’re still unable to reproduce this in our testing. Currently using Fedora 26 with the installer version of Burp Suite (bundled with 1.8.0_112-b15).
We’ll try using 1.8.0_162-b12. In the meantime, you could try using the linux installer version of Burp Suite.
I'll try to get it to reproduce in a VirtualBox image during the weekend. Hopefully that works, to help you reproduce it.
Thanks for the update!
Sometimes the window stays open (but after closing can't be opened again ...). Maybe it is some kind of focus check, that immediately closes the window again?
If I click the proxy bar on a normal system for example, the window always closes and opens again. Maybe that mechanism doesn't work here and instead of staying open, it just closes again...
Thanks for the additional information Norman. We’ve made a note to investigate this further if we manage to reproduce it during testing.
Thanks for the report Jan. We’ll have another go and reproducing the issue.
Norman. We’ve been unable to reproduce the issue. It would be a great help if you could help us narrow down the exact version change when the issue occurred.
You mentioned there is no issue with 1.7.27 and the issue occurs from 1.7.31 onwards? Would it be possible to try out 1.7.28, 1.7.29 and 1.7.30?
The issue started to appear in Burp 1.7.29. Everything works fine in Version 1.7.28.
And I can confirm that it is a Qubes specific issue with any recent Java version.
I have not been able to reproduce it on any other system (tried windows 7 and windows 10, I tried running multiple distros with different window managers in a VM on windows and live directly on the laptop and with windows VMs under linux).
It not only affects burp, the Intellij Rider has the same problem.
I also tried multiple different linux version within the qubes VM itself (fedora 24 - 27) and debian 8 and 9, same result.
It must an issue with how the sub windows are opened programmatically in the java user code. I also tried Oracle JDK 7,8,9 with different sub versions and OpenJDk to no avail.
Thanks for the information and updates Norman. We made a change from 1.7.28 to 1.7.29 to address another issue, which may have inadvertently triggered this issue.
We don’t think this is a bug in our software so we’re going to monitor the situation and take another look if it isn’t fixed long term.
Thanks for letting us know. We are going to investigate the relevant code in Burp to what we had in 1.7.28. Unfortunately, because we can’t replicate the issue ourselves, we can’t confirm the fix has worked. We’ll let you know when we make progress.
Just to let you know that this issue should be fixed in today’s release (1.7.35). Thanks for your feedback and please let us know if you run into any other problems.
It looks like the fix worked for other versions of Linux, but not Qubes. We’ll continue to investigate this issue. In the meantime we’d recomend using another OS.
I'll stick with version 1.7.28 for now :)
Thanks for the update Simon.
We’ve believe we’ve identified the change between 1.7.28 and 1.7.29 that introduced this behavior. We’re going to revert this which hopefully will resolve these issues.
Is there any update on this?
The change will be in the next beta release. We’ll notify you when this is made public.