geluk/pass-winmenu

Error when launching versions 1.13.1

Closed this issue · 3 comments

Just updated pass-winmenu from version 1.13 to 1.13.1 changing the .exe in the instalation folder as I usually do. When the app is launched an error dialog shows saying an error ocurred.

This is the resulting log file:
[00:57:20.788] [DBG] ------------------------------ [00:57:20.789] [DBG] Starting pass-winmenu v1.13.1 [00:57:20.789] [DBG] ------------------------------ [00:57:20.790] [DBG] Enabled security protocols: Tls, Tls11, Tls12, Tls13 [00:57:20.934] [DBG] Config reloading enabled [00:57:21.044] [DBG] Attempting to detect the GPG installation directory [00:57:21.047] [DBG] GPG executable found at the configured path. Assuming installation dir to be C:\Program Files (x86)\GnuPG\bin [00:57:21.050] [ERR] Could not start pass-winmenu: An exception occurred. [00:57:21.053] DependencyResolutionException (An exception was thrown while activating PassWinmenu.Actions.ActionDispatcher -> PassWinmenu.Windows.DialogCreator -> PassWinmenu.PasswordManagement.PasswordManager -> PassWinmenu.ExternalPrograms.Gpg.GPG -> PassWinmenu.ExternalPrograms.Gpg.GpgTransport -> λ:PassWinmenu.ExternalPrograms.Gpg.GpgHomeDirectory.) in :0:0 [00:57:21.054] InvalidOperationException (The Process object must have the UseShellExecute property set to false in order to redirect IO streams.) in :0:0 [00:57:21.054] -> in System.Diagnostics.Process.StartWithShellExecuteEx -- :0:0 [00:57:21.054] -> in System.Diagnostics.Process.Start -- :0:0 [00:57:21.054] -> in PassWinmenu.ExternalPrograms.Processes.Start -- :0:0 [00:57:21.054] -> in PassWinmenu.ExternalPrograms.Gpg.GpgHomeDirResolver.GetDefaultHomeDir -- :0:0 [00:57:21.054] -> in PassWinmenu.ExternalPrograms.Gpg.GpgHomeDirResolver.GetHomeDir -- :0:0 [00:57:21.054] -> in Autofac.Builder.RegistrationBuilder+<>c__DisplayClass0_01.<ForDelegate>b__0 -- :0:0 [00:57:21.054] -> in Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance -- :0:0 [00:57:21.054] -> in Autofac.Core.Resolving.InstanceLookup.Activate -- :0:0

Same:
image

geluk commented

I messed this up a bit while making preparations for the migration to .NET 6. My apologies, that was pretty careless. I have removed the broken artifacts and uploaded a new release. If you download it again the issue should be fixed!

It is working now. Thanks