-
Notifications
You must be signed in to change notification settings - Fork 452
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
Tribler does not start - "TypeError: arguments did not match any overloaded call: QPoint(): too many arguments" #6688
Comments
Thanks for reporting! This seems to be a residue (pun intended) of Python 2 to 3 migration. We'll try to fix that in 7.11 |
Could you please try this branch? #6687 |
The original error gone, but still crashes at start, but with a different error message:
|
In the current version, we can't see what happened at the Core console - the crash happens too soon, before the Sentry init. Could you please run Core standalone like this: |
Of course, this is what I got:
|
Well, sir, Python 3.10 is officially not supported by Tribler yet. There are many reasons for that, PonyORM incompatibility in particular 🤷 |
And try running it like this: |
Mistery solved. :) Then I will retest your solution with Python 3.9 in a conda environment. The rolling release nature of Arch sometimes causes issues like this. |
I am an Arch Linux user and did not use Tribler for some week and after that the app won't start with the following error in the log:
I am the Tribler package maintainer for the Arch Linux/AUR and at least one other user also reported the exact same issue with the same error message, so I thought this is an Arch-specific problem. I thought one of the Qt or Python update is the cause of this behavior, but I could not triangulate which one. I tried to downgrade several suspicious package which was upgraded in the meantime to pinpoint the issue, but no luck.
Beside version 7.10 I also tried 7.11-RC2, but it has the same issue.
I am pleased to provide more information If necessary to solve this problem.
The text was updated successfully, but these errors were encountered: