4.2 Alpha 1 startup issue

Questions and bug reports for Beta releases should be posted here.
Forum rules
Help us help you:
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
buzzword
Newbie
Newbie
Posts: 27
Joined: March 21st, 2022, 11:16 am

4.2 Alpha 1 startup issue

Post by buzzword »

After installing 4.2 Alpha 1, starting SABNZBd opens an empty Powershell window which does not close.
Reinstalling 4.1 resumes normal startup.
User avatar
safihre
Administrator
Administrator
Posts: 5521
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 4.2 Alpha 1 startup issue

Post by safihre »

What version of Windows do you use?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
buzzword
Newbie
Newbie
Posts: 27
Joined: March 21st, 2022, 11:16 am

Re: 4.2 Alpha 1 startup issue

Post by buzzword »

Windows 11 Pro
22H2 Build 22621.2428
User avatar
safihre
Administrator
Administrator
Posts: 5521
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 4.2 Alpha 1 startup issue

Post by safihre »

Hmmm, just to be sure: you just click the shortcut in the Start menu or the Desktop and this happens?
Does it also happen when you go to the actual location of SABnzbd.exe and open it directly?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
automan3
Newbie
Newbie
Posts: 12
Joined: September 22nd, 2020, 2:57 am

Re: 4.2 Alpha 1 startup issue

Post by automan3 »

Got the same here on win 11home. Powershell window opens, when starting sabnzbd. Closing the window closes sabnzbd aswell.
buzzword
Newbie
Newbie
Posts: 27
Joined: March 21st, 2022, 11:16 am

Re: 4.2 Alpha 1 startup issue

Post by buzzword »

safihre wrote: October 20th, 2023, 12:02 am Hmmm, just to be sure: you just click the shortcut in the Start menu or the Desktop and this happens?
Does it also happen when you go to the actual location of SABnzbd.exe and open it directly?
Happens in all 3 cases, whether started from Start Menu, Desktop, or direct from .exe

- I was mistaken, it's not a Powershell window, but a blank command prompt window (right clicking on the taskbar icon, Powershell was simply first in the list)

- If I close the window, SABnzbd shuts down

- If I shutdown SABnzbd via right click shutdown on system tray icon, window closes but just before closing flashes the following error:
WNDPROC return value cannot be converted to LRESULT
TypeError: WPARAM is simple, so must be an int object (got NoneType)
User avatar
safihre
Administrator
Administrator
Posts: 5521
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 4.2 Alpha 1 startup issue

Post by safihre »

I was able to reproduce on my work laptop 😄

https://github.com/pyinstaller/pyinstal ... 1772485556
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
buzzword
Newbie
Newbie
Posts: 27
Joined: March 21st, 2022, 11:16 am

Re: 4.2 Alpha 1 startup issue

Post by buzzword »

Here's a fix for this, it involves setting the Windows 11 Terminal app to default to 'Windows Console Host' instead of 'Windows Terminal' on startup. It's default is Let Windows Decide and it appears to always "decide" on Windows Terminal.

- Open Terminal

- To the right of any existing tabs, right click on a blank area of the tab bar
(or left click on the drop down symbol next to the + sign)
in either case then choose Settings

- Once in settings, set 'Default terminal application' to 'Windows Console Host'

- 'Save' settings

- Did you remember to save settings?

After doing the above, SABnzbd will start correctly without leaving a terminal window
open.

Note these are *not* the same set of settings found for Terminal in the app list, so if you can't find it, maybe that's where you went looking. Do the above.

Also posted on https://github.com/pyinstaller/pyinstaller/issues/8022
Post Reply