mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-25 11:45:49 +03:00
[GH-ISSUE #519] CustomTkinter crashing on RDP after upgrading auto-py-to-exe #400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @grbaker5 on GitHub (Feb 14, 2025).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/519
Hi there
I have been writting a Python 3.11.4 programe which uses customtkinter that works fine (displays normally).
I then use auto-py-to-exe to convert this python script to an EXE which I then upload to my works Windows 2022 server RDP jumphost where it is normally run from.
This was all working fine until auto-py-to-exe recommended that I upgrade which I did.
Now...
Running the EXE on my Windows 11 PC works and sisplays normally.
Running on the RDP host in now displays frames in odd places then crashes with a 'error creating window' in the background.
I have tried all pip components are up to date, also upgrading all my Python to V3.13.2 which hasn't made any difference.
I also tried the options of creating as 'One File' and 'Windows Based (hide the console)' all resulting in the same issue
Unsure of what my previous version of 'auto-py-to-exe' was but I first installed it early December 2024 on Python V3.11.4
Here is a copy of the pip components under V3.13.2 (happy to down grade to V3.11 if recommended)
pip freeze
altgraph==0.17.4
auto-py-to-exe==2.45.1
bcrypt==4.2.1
bottle==0.13.2
bottle-websocket==0.2.9
certifi==2025.1.31
cffi==1.17.1
charset-normalizer==3.4.1
colorama==0.4.6
cryptography==44.0.1
customtkinter==5.2.2
darkdetect==0.8.0
DateTime==5.5
decorator==5.1.1
Deprecated==1.2.18
Eel==0.18.1
fabric==3.2.2
future==1.0.0
gevent==24.11.1
gevent-websocket==0.10.1
greenlet==3.1.1
idna==3.10
invoke==2.2.0
numpy==2.2.3
packaging==24.2
pandas==2.2.3
paramiko==3.5.1
pefile==2023.2.7
pycparser==2.22
pycryptodome==3.21.0
pyinstaller==6.12.0
pyinstaller-hooks-contrib==2025.1
PyNaCl==1.5.0
pyparsing==3.2.1
python-dateutil==2.9.0.post0
pytz==2025.1
pywin32-ctypes==0.2.3
requests==2.32.3
setuptools==75.8.0
six==1.17.0
tqdm==4.67.1
typing_extensions==4.12.2
tzdata==2025.1
urllib3==2.3.0
wrapt==1.17.2
zope.event==5.0
zope.interface==7.2
@github-actions[bot] commented on GitHub (Feb 14, 2025):
👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.
Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.
@brentvollebregt commented on GitHub (Feb 14, 2025):
I can't imagine this is an auto-py-to-exe issue directly - probably a PyInstaller-related issue. auto-py-to-exe might have recommended you to update PyInstaller.
In early December 2024, PyInstaller 6.11.1 was the latest version - you could try using that? Since then PyInstaller has released one new version, 6.12.0, which could be your issue.
@grbaker5 commented on GitHub (Feb 14, 2025):
OK... I will give that a go.
@github-actions[bot] commented on GitHub (Mar 17, 2025):
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.
@github-actions[bot] commented on GitHub (Mar 23, 2025):
Closing issue due to no activity in more than 60 days.