odrinari / Linux-screen-lock-with-MiBand-and-other-bluetooth-watches

Linux screen lock with MiBand and other bluetooth watches
GNU General Public License v3.0
12 stars 2 forks source link

Provide other app formats than .deb? #2

Open gluckgluckwasserbauch opened 11 months ago

gluckgluckwasserbauch commented 11 months ago

Exactly that kind of application I searched for!

Sadly, I'm on Fedora (.rpm-based) and can't get it to work on Distrobox. I have no experience in programming, so I can't package it myself sadly.

Would you be able to package it as rpm, nix or something else?

odrinari commented 11 months ago

Hello, thank you!

I think that it will be possible, maybe code will need some rework. So I can try to do that, but nothing promise)

I will let you know

odrinari commented 10 months ago

Hello! @zewonex

I released an .rpm version of a package, so you can try it now Actually, I have Fedora only in the virtual machine. So it will be perfect if you try to install and use package and give some feedback if something is wrong. I recommend you to also install bluez package - if you haven't

Thank you for awaiting, best regards, Olesya

gluckgluckwasserbauch commented 10 months ago

@odrinari Done :) Sadly, no success. :(

On Fedora Workstation (the conventional one) it kind of works. I can install and launch it normally, and after configuring it, it locks and unlocks my laptop. That sadly worked only once or twice, and even that felt a bit weird to be honest (black screen, freezes, etc.) :grimacing:

I tested it with both my MiBand 6 (directly connected and also non-paired) and my Amazfit GTS 4 (only via BtLE, as it is connected to my phone via Gadgetbridge). I played with a wide range of thresholds (-1, -20, -60, -75, -90) and nothing worked. I started and killed the process many times with both wearables, also with an external bluetooth dongle that supports BtLE, as I wasn't sure if my laptop chip supports that. Nothing worked.


On Fedora Silverblue, I couldn't even get it installed sadly. I tried both via Terminal and graphically, and both ended with the same error code.

`$alex-buero@silverblue-buero:~/Downloads$ rpm-ostree install ./btunlock-1.0.1-x86_64.rpm

Checking out tree c502be8... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ublue-os:akmods fedora-cisco-openh264 updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam copr:copr.fedorainfracloud.org:phracek:PyCharm updates-archive
Importing rpm-md... done
rpm-md repo 'copr:copr.fedorainfracloud.org:ublue-os:akmods' (cached); generated: 2023-11-24T08:46:57Z solvables: 60
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates' (cached); generated: 2023-11-26T01:34:16Z solvables: 13967
rpm-md repo 'fedora' (cached); generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2023-11-24T19:24:24Z solvables: 91
rpm-md repo 'rpmfusion-free' (cached); generated: 2023-11-04T16:49:08Z solvables: 445
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2023-11-24T19:44:29Z solvables: 29
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2023-11-04T17:26:32Z solvables: 208
rpm-md repo 'google-chrome' (cached); generated: 2023-11-22T17:04:48Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2023-11-24T21:19:35Z solvables: 29
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2023-08-10T16:27:35Z solvables: 2
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2023-08-10T15:35:19Z solvables: 5
rpm-md repo 'updates-archive' (cached); generated: 2023-11-26T03:04:34Z solvables: 12832
Resolving dependencies... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
error: Running %post for btunlock: bwrap(/bin/sh): Der Kindprozess wurde mit Signal 0 beendet; run `journalctl -t 'rpm-ostree(btunlock.post)'` for more information

$alex-buero@silverblue-buero:~/Downloads$ journalctl -t 'rpm-ostree(btunlock.post)'

Nov 26 13:32:56 silverblue-buero rpm-ostree(btunlock.post)[64809]: /proc/self/fd/5: Zeile 4: perl: Kommando nicht gefunden.
Nov 26 13:33:26 silverblue-buero rpm-ostree(btunlock.post)[65935]: /proc/self/fd/5: Zeile 4: perl: Kommando nicht gefunden.
-- Boot e94c64c36ca8448999359048bbe0c87b --
Nov 26 13:41:35 silverblue-buero rpm-ostree(btunlock.post)[8371]: /proc/self/fd/5: Zeile 4: perl: Kommando nicht gefunden.
`

(Note: "Kommando nicht gefunden" means "Command not found" in english)

And also graphically (Gnome-Software): Running %post for btunlock: bwrap(/bin/sh): Der Kindprozess wurde mit Signal 0 beendet; run ’journalctl -t 'rpm-ostree(btunlock.post)'’ for more information (Note: "Der Kindprozess wurde mit Signal 0 beendet" means "Child process has been terminated with Signal 0")

Before you made the RPM I tried installing it with Distrobox too, and due to the sandbox, it of course didn't work.