manuskriptw.exe can not be executed due to unhandled exception "NullWriter"

[Anne501R]

Hello Manuskript-Team
,
I just installed Manuskript v0.14.0 and tried to open manuskriptw.exe in order to avoid having a console window in the background. But when I do so I get the following error message on my Win 11 system:

Unhandled exception in Script

Failed to excecute script 'manuskript' due to unhandled exception 'NullWriter' object has no attribute 'fileno'

Traceback (most recent call last):
File "manuskript", line 11, in
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "PyInstaller\loader\pyimod03_importers.py", line 495, in exec_module
File "manuskript\main.py", line 17, in
AttributeError: 'NullWriter' object has no attribute 'fileno'

My current workaround is to excecute the manuskript.exe as before. 😀

[TheJackiMonster]

Thanks for the feedback. That means I probably configured something wrong with manuskriptw.exe. I should look into this before the next release. Maybe some others can clarify whether this issue only occurs on Windows 11 or if it's a problem in general.

[geedeek]

Yes, I see this too on WIndows 11 - the console version works, the windowed version gives me the same error.

[nikelui]

I have encountered the same bug on Windows 10, so it's not an issue with the OS.

[TheJackiMonster]

Okay, thank you for the confirmation. I will probably need a Windows VM for the next release then. ^^'

[uuzp]

Okay, thank you for the confirmation. I will probably need a Windows VM for the next release then. ^^'

Thanks Reply.
I think it may be possible to mention this temporary processing method in the changelog, so that users can handle it themselves.
In fact, I've switched to arch because of the annoying EDGE update can't uninstall issue, and it's working fine so far.
manuskript is amazingly perfect🥳

[TheJackiMonster]

I've found the cause of the issue. The problem is known by the developers of pyinstaller and can be seen here. I will try to implement a workaround now for the next release.

[TheJackiMonster]

Okay, from my testing in a VM the issue is solved by my latest commit 029dfe2. So I will close this issue already. If you don't want to wait for the next release, you can theoretically build the Windows binaries in any Linux VM using the current state in the develop branch (or you try using PyInstaller on Windows). ^^'