Skip to content
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

Fedora 41: Solaar crashes at startup #2762

Open
tet2211 opened this issue Jan 6, 2025 · 10 comments
Open

Fedora 41: Solaar crashes at startup #2762

tet2211 opened this issue Jan 6, 2025 · 10 comments

Comments

@tet2211
Copy link

tet2211 commented Jan 6, 2025

Hello,
I do have a similar problem as here, but this solution doesn't work for me.
I installed Solaar (.rpm) using "Fedora Software" and at first it worked, then i tried to create custom rules and copied the rules.d-uinput/42-logitech-unify-permissions.rules file to /etc/udev/rules.d. After this Solaar didn't display my devices anymore so I tried to get back to where I started by removing the rules file. After I did that I tried again and still no devices showed up. So I thought maybe reinstalling Solaar could help. I did that and now it won't even start up. Every time I try to do so, Fedora tells me "Sorry Solaar crashed on startup" and if I try to start it using terminal, i get the following error message:

grafik

I already tried to install the python package typing_extensions using pip3 install and I made sure to have the newest version of python installed. I also checked if any file might be left of Solaar that could interfere before downloading it again.
I'm not sure if the whole problem is not my fault, or if this is really a bug of Solaar, but anyways i would be glad for someone to help me!
Thanks!

@Obi-Wahn
Copy link

Obi-Wahn commented Jan 6, 2025

I have the same error message under Fedora 41 and RPM version 1.1.14-1-fc41. I have no problems with Flathub version 1.1.13. I have not made any adjustments or changes, I think...

a@b:~$ solaar Traceback (most recent call last): File "/usr/bin/solaar", line 53, in <module> import solaar.gtk File "/usr/lib/python3.13/site-packages/solaar/gtk.py", line 33, in <module> from solaar import cli File "/usr/lib/python3.13/site-packages/solaar/cli/__init__.py", line 26, in <module> from logitech_receiver import device File "/usr/lib/python3.13/site-packages/logitech_receiver/device.py", line 35, in <module> from . import hidpp10 File "/usr/lib/python3.13/site-packages/logitech_receiver/hidpp10.py", line 22, in <module> from typing_extensions import Protocol ModuleNotFoundError: No module named 'typing_extensions'

@pfps
Copy link
Collaborator

pfps commented Jan 6, 2025

Python packages are install on a per-Python-version basis. Make sure that the version of Python that you installed the typing extension with is the same that you are running Solaar with.

@rathann
Copy link
Contributor

rathann commented Jan 6, 2025

You need to install typing-extensions system-wide, i.e. dnf install python3-typing-extensions. It's likely that this dependency should be optional and will be fixed in a subsequent release, though. Please use this work-around for now.

@rathann
Copy link
Contributor

rathann commented Jan 6, 2025

This was reported downstream as well: https://bugzilla.redhat.com/show_bug.cgi?id=2335637 .

@sr-m01
Copy link

sr-m01 commented Jan 7, 2025

You need to install typing-extensions system-wide, i.e. dnf install python3-typing-extensions. It's likely that this dependency should be optional and will be fixed in a subsequent release, though. Please use this work-around for now.

I can confirm that this fixed the issue for me. Thanks!

Problem must've been introduced with recent (Fedora) updates few days or weeks ago because Solaar was working fine before.

Fedora 41 KDE
KDE Plasma 6.25
KDE-Frameworks 6.9.0
QT 6.8.1
Kernel: 6.12.8-200.fc41.x86_64 (64-bit)

@glennDittmann
Copy link

You need to install typing-extensions system-wide, i.e. dnf install python3-typing-extensions. It's likely that this dependency should be optional and will be fixed in a subsequent release, though. Please use this work-around for now.

+1 on this workaround; also worked for me on Fedora 41.

@tet2211
Copy link
Author

tet2211 commented Jan 7, 2025

dnf install python3-typing-extensions

Worked for me too, I don't get the error message anymore. Tanks!

But now I don't want to mess it up again, do I still need to copy the rules.d-uinput/42-logitech-unify-permissions.rules file to /etc/udev/rules.d for it to work with custom rules?
It now says: "rules cannot access modifier keys in Wayland, accessing process only works on GNOME with Solaar Gnome extension installed" even tough I have the extension installed.

@pfps
Copy link
Collaborator

pfps commented Jan 7, 2025

You need to have one of the Solaar udev rules in /etc/udev/rules.d. If you are using Wayland and you want to allow Solaar rules to simulate keyboard or mouse input you need the Wayland rule; otherwise the other one is fine, and more secure.

The Gnome extension is independent of this.

@tet2211
Copy link
Author

tet2211 commented Jan 7, 2025

Okay thanks! Everything works now!

@gleitoncampos
Copy link

You need to install typing-extensions system-wide, i.e. dnf install python3-typing-extensions. It's likely that this dependency should be optional and will be fixed in a subsequent release, though. Please use this work-around for now.

+1 to the problem and the workaround. Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants