Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to limit upgrades when new version will be OS incompatible #3324

Open
bmuessig opened this issue Jul 24, 2022 · 9 comments
Open

ability to limit upgrades when new version will be OS incompatible #3324

bmuessig opened this issue Jul 24, 2022 · 9 comments
Labels
Component: Updates Issue needs changes to how we perform client updates Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Enhancement Issue is a small enhancement to existing functionality

Comments

@bmuessig
Copy link

Version and Platform (required):

  • Binary Ninja Version: 3.1.3469
  • OS: Windows
  • OS Version: 8.1 Pro
  • CPU Architecture x64

Bug Description:

---------------------------
binaryninja
---------------------------
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: windows.

---------------------------
OK   
---------------------------

Steps To Reproduce:
Updated Binary Ninja and then started it.

Expected Behavior:
It should start and not crash on launch.

Additional Information:
Before the update, it worked just fine.

@bmuessig
Copy link
Author

I would like to add that I have reinstalled Binary Ninja without effect.

@psifertex
Copy link
Member

Can you try the steps in this document to see if it's a plugin causing this problem? It's quite likely that it's caused by an old version of the binexport plugin.

https://docs.binary.ninja/guide/troubleshooting.html#troubleshooting-plugins

(related binexport issue: google/binexport#93)

@psifertex psifertex added the Type: Crash Issue is a crash or deadlock label Jul 25, 2022
@psifertex
Copy link
Member

Sorry, ignore me, I mis-read your original comment. QT failing to load is probably not binexport.

@psifertex
Copy link
Member

Unfortunately this is due to the decency requirements for new versions of QT. You'll notice that 8.1 is no longer supported: https://doc.qt.io/qt-6/supported-platforms.html

and in fact, hasn't been supported officially for BN itself for some time: https://binary.ninja/faq/#supported-platforms it just happened to work longer than it was officially supported

@psifertex psifertex changed the title Binary Ninja crashes on launch after update Latest Binary Ninja does not support Windows 8.1 Jul 25, 2022
@psifertex psifertex added State: Wontfix Issue will probably never be fixed unsupported platform labels Jul 25, 2022
@bmuessig
Copy link
Author

Could you please provide a download that still works?
I can neither downgrade to it, nor download a version that still supports it.

@psifertex
Copy link
Member

psifertex commented Jul 25, 2022

Unfortunately we don't have old installers available. The easiest way to get a version that old is to install a copy on a newer version of windows elsewhere, then use the UI to downgrade to a previous version and copy the file structure back over.

The biggest issue this points out is that we should have the ability to disable updates to a version that will be incompatible. In fact, even if you get the old version installed you have to disable updates or it will try to update to the incompatible version. I'm going to re-open this issue and re-name it to track that issue.

Note though that with the current updater infrastructure it's actually quite difficult to do this so it necessitates some new design to the way updates work.

@psifertex psifertex reopened this Jul 25, 2022
@psifertex psifertex changed the title Latest Binary Ninja does not support Windows 8.1 ability to limit upgrades when new version will be OS incompatible Jul 25, 2022
@psifertex psifertex added Type: Enhancement Issue is a small enhancement to existing functionality Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround and removed State: Wontfix Issue will probably never be fixed Type: Crash Issue is a crash or deadlock unsupported platform labels Jul 25, 2022
@bmuessig
Copy link
Author

Thanks for converting the issue. Having the updater respect OS compatibility borders is great. I think this would become particularily useful for macOS too with its yearly updates.

@psifertex
Copy link
Member

MacOS tends to be less of a big deal though since we usually support the last 2-3 major releases at least and mac users tend to update more frequently than other OS's in my experience.

@bmuessig
Copy link
Author

Indeed, I just thought that if you keep 2-3 major releases supported, with every new release, one would be pushed out of the 'queue' of supported operating systems.

@fuzyll fuzyll added the Component: Updates Issue needs changes to how we perform client updates label May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Updates Issue needs changes to how we perform client updates Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Enhancement Issue is a small enhancement to existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants