[bounty] $100 windows installation fails for a new user, logs attached

[m13v]

1. I downloaded screenpipe on windows machine
2. started it, the setup failed
3. I pulled up the inspector and looked at the console, this is the error I found

error or timeout: Error: command failed with code -1073741515
at page-2bff8a7bfd23260b.js:1:174911
at f.emit (590-d9ad7e6472c4fddd.js:276:162075)
at n.onmessage (590-d9ad7e6472c4fddd.js:276:163069)
at 590-d9ad7e6472c4fddd.js:276:160962
at value (:229:30)

[linear]

MED-332 [bounty] /bounty 100 windows installation fails for a new user, logs attached

[m13v]

/bounty 100

[algora-pbc]

💎 $100 bounty • Screenpi.pe

Steps to solve:

1. Start working: Comment /attempt #764 with your implementation plan
2. Submit work: Create a pull request including /claim #764 in the PR body to claim the bounty
3. 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		#767

[algora-pbc]

💡 @Neptune650 submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[algora-pbc]

🎉🎈 @Neptune650 has been awarded $100! 🎈🎊

• Share on socials
• Give feedback

[louis030195]

@Neptune650 this is not solved fyi, if you want to help!

i believe issue is on screenpipe setup subcommand

screenpipe/screenpipe-app-tauri/components/onboarding/status.tsx

Line 43 in 014c209

const command = Command.sidecar("screenpipe", ["setup"]);

is this subcommand actually working on windows?

screenpipe/screenpipe-server/src/bin/screenpipe-server.rs

Line 145 in 014c209

Command::Setup { enable_beta } => {

i think solving this would also solve the troubleshooting button in settings which does not seem to work on windows (using same subcommand)

[Neptune650]

@Neptune650 this is not solved fyi, if you want to help!

i believe issue is on screenpipe setup subcommand

screenpipe/screenpipe-app-tauri/components/onboarding/status.tsx

Line 43 in 014c209

const command = Command.sidecar("screenpipe", ["setup"]);

is this subcommand actually working on windows?

screenpipe/screenpipe-server/src/bin/screenpipe-server.rs

Line 145 in 014c209

Command::Setup { enable_beta } => {

i think solving this would also solve the troubleshooting button in settings which does not seem to work on windows (using same subcommand)

@louis030195 Of course, will look into it, will use a Windows VM for testing.

[m13v]

thx Neptune, looking forward

…

On Tue, Nov 26, 2024 at 8:48 AM Neptune ***@***.***> wrote: @Neptune650 <https://github.com/Neptune650> this is not solved fyi, if you want to help! i believe issue is on screenpipe setup subcommand https://github.com/mediar-ai/screenpipe/blob/014c209e164b68dc6d2138adc6559cff7ca53bcc/screenpipe-app-tauri/components/onboarding/status.tsx#L43 is this subcommand actually working on windows? https://github.com/mediar-ai/screenpipe/blob/014c209e164b68dc6d2138adc6559cff7ca53bcc/screenpipe-server/src/bin/screenpipe-server.rs#L145 i think solving this would also solve the troubleshooting button in settings which does not seem to work on windows (using same subcommand) @louis030195 <https://github.com/louis030195> Of course, will look into it, will use a Windows VM for testing. — Reply to this email directly, view it on GitHub <#764 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY62CDESXYE5IJZFLKTJ6XT2CSQ5ZAVCNFSM6AAAAABSPI6HCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGM4DOMZWGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Neptune650]

1. I downloaded screenpipe on windows machine

   2. started it, the setup failed

   3. I pulled up the inspector and looked at the console, this is the error I found

error or timeout: Error: command failed with code -1073741515 at page-2bff8a7bfd23260b.js:1:174911 at f.emit (590-d9ad7e6472c4fddd.js:276:162075) at n.onmessage (590-d9ad7e6472c4fddd.js:276:163069) at 590-d9ad7e6472c4fddd.js:276:160962 at value (:229:30)

@m13v Do we have the entire logs? We do need to know what step is failing, could also be a network issue at the user side