Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Key binds Not working. Only solution is to fully reinstall the app, only for it to stop working on next restart #120

Open
Immortaleye3115 opened this issue Nov 9, 2023 · 4 comments
Assignees
Labels
bug Something isn't working cannot-replicate We're unable to replicate the issue triage Marks issues that were created with an issue template

Comments

@Immortaleye3115
Copy link

Version Number

6.5.1

File

Installer (VolumeControl-Installer.exe)

Windows Version

Windows 11 Pro

Actual Behaviour

Whenever I restart my pc, the key binds stop working all together. The only way to make them start working again is by uninstalling and reinstalling the app. Btw I have tried the portable version as well, but the same thing happens.

Expected Behaviour

No response

Reproduction Steps

No response

Log

HH:mm:ss:fff              === Log Initialized @ Thursday, 9 November 2023 4:44:10 AM ===  { LogFilter: 62 (INFO, WARN, ERROR, CRITICAL, FATAL) }
15:44:10:917  [INFO]      Config version is 0.0.0, settings will be migrated to version 6.5.1.
15:44:12:900  [INFO]      Volume Control version 6.5.1 (Installed)
15:44:13:116  [INFO]      Microsoft Windows 11 Pro (64-bit)
15:44:14:143  [INFO]      Showing update prompt for new version: 6.5.2
15:44:20:677  [INFO]      User indicated they want to update to version 6.5.2.
15:44:21:890  [ERROR]     [AddonLoader] An exception occurred while loading embedded resource "VolumeControl.HotkeyActions.Localization.it-HotkeyActions.loc.json": {
                            "Message": "Unexpected character encountered while parsing value: . Path '', line 0, position 0."
                            "ExceptionType": "Newtonsoft.Json.JsonReaderException"
                            "LineNumber": "0"
                            "LinePosition": "0"
                            "Source": "Newtonsoft.Json"
                            "TargetSite": {
                              "Name": "ParseValue"
                              "DeclaringType": "Newtonsoft.Json.JsonTextReader"
                              "Attributes": "PrivateScope, Private, HideBySig"
                              "CallingConvention": "Standard, HasThis"
                            }
                            "StackTrace": {
                              [0] at Newtonsoft.Json.JsonTextReader.ParseValue()
                              [1] at Newtonsoft.Json.JsonTextReader.Read()
                              [2] at Newtonsoft.Json.JsonReader.ReadAndMoveToContent()
                              [3] at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
                              [4] at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
                              [5] at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
                              [6] at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
                              [7] at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
                              [8] at Newtonsoft.Json.JsonConvert.DeserializeObject(String value)
                              [9] at VolumeControl.Helpers.LocalizationHelper.StreamLoader.LoadFromString(String jsonString, LocalizationLoader loader, String sourceFileName)
                              [10] at VolumeControl.Helpers.LocalizationHelper.StreamLoader.LoadFromStream(Stream stream, LocalizationLoader loader, String resourceName)
                              [11] at VolumeControl.Helpers.LocalizationHelper.LoadFromManifestResource(Assembly addonAssembly, String resourceName)
                              [12] at VolumeControl.Helpers.AddonLoader.LoadTranslations(Assembly assembly)
                            }
                          }
@Immortaleye3115 Immortaleye3115 added bug Something isn't working triage Marks issues that were created with an issue template labels Nov 9, 2023
@radj307
Copy link
Owner

radj307 commented Nov 10, 2023

Log doesn't show anything unexpected (that exception has already been fixed).
Do all of your hotkeys appear to be registered, or are you unable to register them? Do you have any other applications that add global hotkeys (i.e. AutoHotkey) installed?

With the application freshly installed and not started yet, try the following:

  1. Press Win+R and paste this path: %LocalAppData%/radj307/VolumeControl.
    Make a backup of VolumeControl.json if you want to preserve your settings.
  2. Open VolumeControl.json in a text editor like notepad & replace everything in the file with this:
    {
      "LogFilter": 111,
    }
  3. Start Volume Control
  4. Re-register all hotkeys (uncheck then recheck the checkbox):
    image
  5. Close Volume Control
  6. Copy the contents of your log and post them in a reply here. Make sure you enclose the text with triple-backticks, like this:
    ```
    <-- Log goes here
    ```
  7. Restart your computer, then start volume control again (hopefully the bug will occur so the log includes what went wrong)
  8. Repeat step 5. (re-register all hotkeys)
  9. Repeat step 7. (post the second log)

@Immortaleye3115
Copy link
Author

Immortaleye3115 commented Nov 10, 2023 via email

@radj307
Copy link
Owner

radj307 commented Nov 12, 2023

It seems like your previous hotkeys weren't loaded correctly, but the cause of that is uncertain. Please try the latest version and see if the problem still occurs.

@radj307 radj307 changed the title Key binds Not working. Only solution is to fully reinstall the app, only for it to stop working on next restart [BUG] [BUG] Key binds Not working. Only solution is to fully reinstall the app, only for it to stop working on next restart Nov 12, 2023
@radj307 radj307 added the cannot-replicate We're unable to replicate the issue label Nov 12, 2023
@radj307
Copy link
Owner

radj307 commented Dec 14, 2023

Is this issue still occurring for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cannot-replicate We're unable to replicate the issue triage Marks issues that were created with an issue template
Projects
None yet
Development

No branches or pull requests

2 participants