Win10: Sideband throws python exception on first run
Read the Contribution Guidelines Before creating a bug report on this issue tracker, you must read the Contribution Guidelines. Issues that do not follow the contribution guidelines will be deleted without comment.
- The issue tracker is used by developers of this project. Do not use it to ask general questions, or for support requests.
- Ideas and feature requests can be made on the Discussions. Only feature requests accepted by maintainers and developers are tracked and included on the issue tracker. Do not post feature requests here.
- After reading the Contribution Guidelines, delete this section only ("Read the Contribution Guidelines") from your bug report, and fill in all the other sections.
Describe the Bug First of all: Is this really a bug? Is it reproducible?
If this is a request for help because something is not working as you expected, stop right here, and go to the discussions instead, where you can post your questions and get help from other users.
If this really is a bug or issue with the software, remove this section of the template, and provide a clear and concise description of what the bug is.
Win10: From the release of Sideband 1.4.0 download the zip Extract in the user Downloads directory Run Sideband.exe
Python crash notice occurs:
Traceback (most recent call last):
File "main.py", line 1, in
To Reproduce Describe in detail how to reproduce the bug.
New install with all files removed
Expected Behavior A clear and concise description of what you expected to happen.
Logs & Screenshots Please include any relevant log output. If applicable, also add screenshots to help explain your problem. In most cases, without any relevant log output, we will not be able to determine the cause of the bug, or reproduce it.
System Information
- OS and version : Win10
- Python version: Running packaged Sideband.exe
- Program version: 1.4.0 release
Additional context Add any other context about the problem here.
Weird. That really shouldn't be able to happen, since the config is always loaded, checked and migrated before the UI is initialised.
I've tried a fresh install and wiping the configuration directory, but I can't reproduce it on Windows 10 here.
Changing line 529 of main.py to:
if "telemetry_allow_requests_from_anyone" in self.sideband.config and self.sideband.config["telemetry_allow_requests_from_anyone"]:
Would probably solve it, but I'm hesitant to do that as a quick fix, since the underlying cause is likely to be something much stranger. Are you 100% certain there is not something strange going on with this particular Win10 system?
Is this reproducible on multiple machines in your end?
Only one failure machine on first install. Do you know if anything besides .config, .kivy and .sideband is created? I moved those away and tried to repeat, and it started this time without the error. I don't think there is anything special, other than it is a Win10 VM running in Bootcamp/Parallels on Mac.
That is really puzzling. I can't think of anything else, off the top of my head. I'll keep it in mind and see if I can eventually reproduce it. Thanks for posting!
Sounds good, no problem marking this 'can't reproduce' or something. If I find a case for that I can add details and reopen.
Fixed in latest release.