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

Crash on open update details when ussing Classic Windows theme #220

Closed
JustOff opened this issue Nov 21, 2017 · 17 comments
Closed

Crash on open update details when ussing Classic Windows theme #220

JustOff opened this issue Nov 21, 2017 · 17 comments
Assignees
Labels
Bug Issues which are bug reports Confirmed Confirmed issues

Comments

@JustOff
Copy link

JustOff commented Nov 21, 2017

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.

@Belphemur
Copy link
Owner

Belphemur commented Nov 21, 2017 via email

@JustOff
Copy link
Author

JustOff commented Nov 21, 2017

I tried both Chrome & Firefox, but send is never ending and console reports jquery.js?ver=1.12.4:4 POST https://www.aaflalo.me/wp-json/contact-form-7/v1/contact-forms/665/feedback 413 ().

@JustOff
Copy link
Author

JustOff commented Nov 21, 2017

Done.

@Belphemur
Copy link
Owner

Belphemur commented Nov 21, 2017

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 ?

Message: Visual Styles-related operation resulted in an error because no visual style is currently active.
Source: System.Windows.Forms
StackTrace:
   at System.Windows.Forms.VisualStyles.VisualStyleRenderer.IsCombinationDefined(String className, Int32 part)
   at System.Windows.Forms.VisualStyles.VisualStyleRenderer..ctor(String className, Int32 part, Int32 state)
   at System.Windows.Forms.ProgressBarRenderer.InitializeRenderer(VisualStyleElement element)
   at System.Windows.Forms.ProgressBarRenderer.DrawHorizontalBar(Graphics g, Rectangle bounds)
   at SoundSwitch.UI.UserControls.TextProgressBar.OnPaint(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

@JustOff
Copy link
Author

JustOff commented Nov 21, 2017

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.

@Belphemur Belphemur added the Bug Issues which are bug reports label Nov 21, 2017
@Belphemur
Copy link
Owner

Do you mind if I share your dump with @FireEmerald ?

@Belphemur Belphemur changed the title Crash on open update details if "Notify me when available" selected Crash on open update details when ussing Classic Windows theme Nov 21, 2017
@JustOff
Copy link
Author

JustOff commented Nov 21, 2017

Of course, just not expose it to the public, plz. Thank you in advance.

@FireEmerald
Copy link
Contributor

FireEmerald commented Nov 23, 2017

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.

@Belphemur
Copy link
Owner

@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?

@FireEmerald
Copy link
Contributor

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...

@Belphemur
Copy link
Owner

Belphemur commented Nov 24, 2017 via email

@alystair
Copy link

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.
tmp.txt

@FireEmerald
Copy link
Contributor

@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?

@alystair
Copy link

alystair commented May 15, 2018 via email

@FireEmerald
Copy link
Contributor

FireEmerald commented May 15, 2018

Aero is not the Windows Classic Skin. The Windows Classic Skin was included up to Windows 7. The Theme was removed in Windows 8 and Windows 10 and is no longer include.

So your issue isn't the same as described in this thread.

You can en-/disable the Windows Classic Skin in Windows 7 here:
classic

@FireEmerald FireEmerald added the Confirmed Confirmed issues label May 15, 2018
@alystair
Copy link

alystair commented May 15, 2018 via email

@FireEmerald
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues which are bug reports Confirmed Confirmed issues
Projects
None yet
Development

No branches or pull requests

4 participants