-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Crash on open update details when ussing Classic Windows theme #220
Comments
Hello,
Without the crashlog I can't help you.
Can you send it to me using my contact form ?
https://www.aaflalo.me/contact/
|
I tried both Chrome & Firefox, but send is never ending and console reports |
Done. |
About the contact form, I didn't expect the file to be more than 10MB. I changed it to 20MB for further usage. About your issue, it's a duplicate of #194 which was resolved by @FireEmerald in #195 It's weird to see it coming back. Can you confirm that you're using the Classic Windows theme ?
|
Yes, it looked exactly the same as here, but when I switched to "Install automatically" update went flawlessly. |
Do you mind if I share your dump with @FireEmerald ? |
Of course, just not expose it to the public, plz. Thank you in advance. |
I don't like the current update process at all. There are free frameworks like https://github.com/ProgTrade/nUpdate which could be implemented instead of re-creating the wheel. |
@FireEmerald That would be nice feature to have to start the 4.0.0 Would you like to explore the possibility to use that lib to redo the update process? |
I already evaluated the lib several month ago but for the rest of 2017 i will be unable to implement this, due to less free time. Perhaps in the winter holidays... |
Sure I understand.
Let's keep it as an open improvement :)
It will be for 4.1 instead of 4.0.
…On 2017-11-24 10:32, FireEmerald wrote:
I already evaluated the lib several month ago but for the rest of 2017
i will be unable to implement this, due to less free time. Perhaps in
the winter holidays...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMEsh6Qyb0vuYqLdjqILyY2ApHn6I28ks5s5uF6gaJpZM4QlooB>.
|
I think this came back - every time a new update is pushed out SoundSwitch crashes, however restarts and updates correctly (however the 100% green progress bar seems to flash unusually). Running Windows 7, I've attached the log. |
@alystair This issue was never fixed, so it can't "came back". The issue is only present if you have the classic windows skin active - do you? |
I'm using Windows 7 so... aero?
|
Guess I'll have to open my own issue and ref this once since it's similar then
|
As already mentioned, the classic theme is no longer included in recent windows versions. Windows 7 was the last release which included the theme. As of 14th January 2020 Microsoft stopped the support for Windows 7 and therefore the OS should not be used anymore. You may use choco to update the application without having to enter the update details window. |
I had 3.15.1 installed with "Notify me when updates are available" setting. Today I received notification about 3.15.2, but when trying to see the details SoundSwitch has been crashed. I restarted it, but the result was the same. The only way to get a new version was to change update settings to "Install automatically".
PS: Sorry, but I'm not comfortable with exposing crashdumps publicly.
The text was updated successfully, but these errors were encountered: