You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running in PowerShell interactively everything works okay but when running from Task Scheduler and writing output to log file I'm getting some systray errors:
ERROR systray: systray_windows.go:769 Unable to init instance: Unspecified error [error=Unable to init instance: %v error_location=github.com/getlantern/systray.registerSystray (systray_windows.go:769
) error_op= error_text=Unable to init instance: Unspecified error error_type=errors.Error]
ERROR systray: systray_windows.go:769 at github.com/getlantern/systray.registerSystray (systray_windows.go:769)
ERROR systray: systray_windows.go:769 at github.com/getlantern/systray.Register (systray.go:106)
ERROR systray: systray_windows.go:769 at github.com/getlantern/systray.Run (systray.go:77)
ERROR systray: systray_windows.go:769 at runtime.goexit (asm_amd64.s:1650)
ERROR systray: systray_windows.go:769 Caused by: Unspecified error
I think this error occurs because powershell runs in non interactive mode.
Maybe it would be posible to add some parameter -silent or -non-interactive which would prevent these popup windows about backup status and there will be no ERRORS?
These errors don't have impact to it's main function and backups are done successfully but it would be nice to see no errors in Logs files :)
The text was updated successfully, but these errors were encountered:
Running in PowerShell interactively everything works okay but when running from Task Scheduler and writing output to log file I'm getting some systray errors:
I think this error occurs because powershell runs in non interactive mode.
Maybe it would be posible to add some parameter -silent or -non-interactive which would prevent these popup windows about backup status and there will be no ERRORS?
These errors don't have impact to it's main function and backups are done successfully but it would be nice to see no errors in Logs files :)
The text was updated successfully, but these errors were encountered: