screenpipe
screenpipe copied to clipboard
[bounty] The given version [19] is not supported, only version 1 to 10 is supported in this build
/bounty 50
💎 $50 bounty • Screenpi.pe
Steps to solve:
- Start working: Comment
/attempt #794with your implementation plan - Submit work: Create a pull request including
/claim #794in the PR body to claim the bounty - Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts
Thank you for contributing to mediar-ai/screenpipe!
Add a bounty • Share on socials
| Attempt | Started (GMT+0) | Solution |
|---|---|---|
| 🟢 @Neptune650 | #830 |
maybe its related to nvidia gpu + ort (its running on rtx4060)
maybe its related to nvidia gpu + ort (its running on rtx4060)
@louis030195 It's not related to the Nvidia GPU but rather the way that Windows handles dynamic libraries.
It's loading an older version of onnxruntime.dll at C:\Windows\System32
While it should be running the one that's packaged with Screenpipe. The DLL has to be in the same place as screenpipe.exe so Windows runs it first.
See https://github.com/microsoft/onnxruntime/issues/11230
well if you know how to fix and want to send a PR!
well if you know how to fix and want to send a PR!
@louis030195 The thing is that currently this doesn't happen with users, did you use Tauri in your build environment and are you sure there's an onnxruntime.dll where your screenpipe.exe is.
💡 @Neptune650 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
for people who still have this issue, get the latest onnx runtime release from here: https://github.com/microsoft/onnxruntime/releases And extract the onnxruntime.dll to wherever your screenpipe.exe is.
This in itself is a bit a questionable thing btw. since it opens screenpipe to DLL sideloading attacks, but that imho is a different story.