-
Notifications
You must be signed in to change notification settings - Fork 22
Linux #2
Comments
Please post the error output. |
Please post the following information:
If you are running from source:
|
Not him but I'm having the same problem.
uname -a: |
Bionic Beaver uses glibc 2.27 and this was compiled for glibc 2.28. |
Yeah I tried that, too:
I installed several different libraries but none of them seem to give it the version of tkinter it wants. |
You need to install the python3 version using apt or pip3 |
Yep. Python3 was already installed. I went with this instead: I can keep testing though if you want this resolved. |
I meant make sure you run Anyway, fusee-launcher works fine. |
Yep I installed that too and it still gave the same error. |
Try installing tkinter using pip.
…On Tue, Jul 16, 2019, 9:42 PM Mouse ***@***.***> wrote:
Yep I installed that too and it still gave the same error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=ADGPVKNAANYI7NDCORTALQDP7YXDBA5CNFSM4HR6DWMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2CCTFY#issuecomment-511977879>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADGPVKNRMB37XFSMRSTAHPDP7YXDBANCNFSM4HR6DWMA>
.
|
Is tkinter really available on pypi? I don't think so. |
Actually on a double check it should be in the stdlib, which means it not
being available seems more indicative of a borked python install than
anything.
…On Wed, Jul 17, 2019, 1:00 AM Ian Burgwin ***@***.***> wrote:
Is tkinter really available on pypi? I don't think so.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=ADGPVKK6TV4IMJKCQP2IUMTP7ZOJVA5CNFSM4HR6DWMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2CTHKY#issuecomment-512045995>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADGPVKN62GHHGE6GLOQQSKTP7ZOJVANCNFSM4HR6DWMA>
.
|
I had this exact same issue in Debian 9. I checked my /lib/ directory and saw that libc version is below the required 2.28 version. Upgrading glibc, Debian 9 protested that the version is already at its most up-to-date. I checked the packages website and saw that only Buster (10) offered version 2.28-10 or greater. So I had to edit my sources.list and do a full upgrade to Debian 10 to fix the issue. |
https://github.com/nh-server/fusee-interfacee-tk/releases/V1.0.1 |
I get “no module named fusee_launcher” |
Never mind I just had to put in the fusee_launcher.py |
TheGhostboi64 did you seriously just come to a 3 year old issue and make the first comment in 2 years? |
The issue is still open. There's nothing wrong with posting in it so long as the issue is still active. The internet police: Don't necro! |
but what if there's more problems involving Linux, like right now, I have a problem where it says "no module named mock_arguments" |
I ran into the same problem on Ubuntu 22.04.03 Apparently, it has nothing to do with tkinter. You have to add a usb rule to udev in order to make it work. Follow the steps on this website:
I did not have to add myself to the plugdev group. I just used the terminal to create the "50-switch.rules" files, edit it and then saved. I hope it helps anyone in the future with Err13 usb permission errors. |
When I try to run fusee-interface-tk on my ubuntu pc, I always get some kind of python, libc error. How do I fix this?
The text was updated successfully, but these errors were encountered: