-
Notifications
You must be signed in to change notification settings - Fork 86
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
Repository does not have release file #191
Comments
Facing similar issue on Ubuntu 24.04 LTS version. Lenovo thinkpad t480 |
Same as @Wambugu-Muchemi on 24.04 LTS. ThinkPad x220. No release file for noble. |
Can confirm that the workaround in #188 does NOT work for 24.04. The installation throws dbus errors. |
Oh good to note. Thanks for the heads up, will keep checking |
In order to get this work on Ubuntu 24.04 LTS (Noble Numbat) we need a new release file. @uunicorn I am using a Thinkpad Yoga 370. this was working with the lastest version of fedora i remember. |
Any chance that the developer is active for this project? |
Same problem on a Lenovo ThinkPad T470 running a fresh install of Debian 12. |
Similar error trying to get it running on my Thinkpad T480 with Fedora 40. Getting this error: Copr repo for python-validity owned by tigro 1.4 kB/s | 1.5 kB 00:01
|
This repository won't work with Fedora 40. This is primarily for Ubuntu I guess. You can refer to Fedora:
Also mentioned in Unicorn's repo. But this still doesn't work anymore. However for me this one here: https://copr.fedorainfracloud.org/coprs/taaem/python-validity/ Worked flawlessly on my Thinkpad Yoga 370 with 138a:0097. |
Same issue ngl |
Any potential workaround for this issue or do we have to wait for the dev to see this issue. Please inform if any steps could be taken to fix this issue with a PR. Good Day. |
I don't think there's any potential solution to the issue unless the dev works on the fix so we have a release file. There's a similar repo named taaem's python-validiity that works on Fedora. If someone can port this to Ubuntu then we can get the fingerprint working though I feel this will require a tremendous amount of work. https://copr.fedorainfracloud.org/coprs/taaem/python-validity/ |
|
It installed fine, but it seems much less stable. Occasionally my login manager crashes. Maybe we can get a rebuild for noble? |
Ubuntu Version is 23.10 and Fingerprint sensor is Synaptics 06cb:009a and machine is Thinkpad T480. I can install and update PAM, but cannot run fprintd-enroll.
I ran
sudo add-apt-repository ppa:uunicorn/open-fprintd
And encounter the error:
Found existing deb entry in /etc/apt/sources.list.d/uunicorn-ubuntu-open-fprintd-mantic.sources Hit:1 http://ph.archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://ph.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:4 http://ph.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:5 http://repository.spotify.com stable InRelease Ign:6 https://ppa.launchpadcontent.net/uunicorn/open-fprintd/ubuntu mantic InRelease Err:7 https://ppa.launchpadcontent.net/uunicorn/open-fprintd/ubuntu mantic Release 404 Not Found [IP: 185.125.190.80 443] Reading package lists... Done E: The repository 'https://ppa.launchpadcontent.net/uunicorn/open-fprintd/ubuntu mantic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
The Fingerprint login will show up when i go to Users but will disappear once the dialog for Authentication opens.
The text was updated successfully, but these errors were encountered: