Open jurajsolarml opened 1 year ago
I had the same problem with Windows 10 but I installed windows desktop runtime-6.0.13 and the problem was solved.
Hello, Ferdium-win-AutoSetup-6.2.3-x64.exe desktop same problem no change.
Same here, ferdium portable 6.2.3 x64, Windows 10 21H2 (19044.2846). After restart PC, only blue screen appears, force close, or anything else didn't help. download portable installer again, run and afterthat ferdium worked.
Even a reboot didn't help. Desktop and portable no change, non-functional.
now in 6.2.4. same problem, even reboot ferdium didn't solve problem and reinstall isn't possible now because of Symantec (Unproven.LowPrevalence), so i must wait
@Dareiko or @jurajsolarml would you be able to provide me with the Console Log ?
CTRL + ALT + I several times (calmly press them) until a window opens on the right side. Then press "Console" and take a screenshot or copy paste the logs here please.
Also, this issue might be related with: https://github.com/ferdium/ferdium-app/issues/814
Probably a full clean uninstall may work (This will delete all your Ferdium related data if you are NOT using Ferdium Server): On AutoSetup or Setup:
On Portable:
Try installing again - use version 6.2.4 please (the latest stable version)
I use built in updater and ferdium was start. All services are here, but logged off. Logged again and it's worked now. I wil try restart after work.
Can confirm the same issue on macOS, also version 6.2.4.
Same issue for version 6.2.4 macOS 13.1 Both Apple Silicon & Intel
Hello, @SpecialAro Ferdium running, frozen. Pressed CTRL + ALT + I several times. The console does not start.
Same here. version 6.2.4 apple silicon MacOS Ventura
Looks like it happens after waking up from sleep mode. The console says that the Developer Tools have been disconnected.
Then it seems to be related/duplicate to #923
- Wild hunch - how many of us are Little Snitch users?
I don't use Little Snitch
Me neither.
Hunch dispelled - thanks both
I experience this as soon as I add the arguments
--auth-server-whitelist '*.example.com' --auth-negotiate-delegate-whitelist '*.example.com'
If it helps anyone in the meantime, about a week ago I started using @marcoarment's Quitter to shut Ferdium down after half an hour of idleness, and it has been working well so far. It makes for a more predictable life until this bug is resolved.
I can't remember where I got this idea from so apologies if I've taken credit for it away from someone here.
Still happening on my system (macbook air M2) Version: 6.2.7 Server: No Server Electron: 24.2.0 Chrome: 112.0.5615.165 Node.js: 18.14.0 Platform: macOS Ventura 13.1 Arch: arm64 Build date: Mon May 08 2023 21:46:55 GMT+0200 (Central European Summer Time)
Everytime the computer wakes up regardless of how much time it was in standby.
Preflight Checklist
Ferdium Version
6.2.3-x64
Recipe Name
Ferdium-win-Portable 6.2.3-x64
Recipe Version
6.2.3-x64
Last Known working version of the recipe
0
Steps to reproduce
Expected Behavior
I was expecting a sputtering program.
Actual Behavior
The program freezes after starting.
Screenshots
Additional Information
No response