Closed logicito closed 3 years ago
What do you mean by stopped working? Thank you
I am running Fedora 34
The service will not start at boot.
I tried to run the boot enable option again and didn't find the linux-enable-ir-emitter file
I tried to install it, it said already installed
When I removed it, didn't find many of the application files in the removal process
Then, I installed it again and it started working
It seems to me, when the upgrade happened after a sudo dnf update, it removed files instead of update.
Have you used the bash installer before ?
I have never used the bash installer, I used the instructions for Fedora
Ok, thank you for your investigations. Maybe it's because I change the files structure of the software. But I don't know how to fix that in the .spec file. I will try to find a solution. Thank you @logicito !
@supdrewin did you have problems after updating the package on Arch ? Thank you.
Happy to help, you app is critical to ensure Howdy works, thank you very much for your hard work and keeping the app up to date
I think I've found the problem: in the post uninstall section, I remove the files added after installation but I don't check if it's an uninstallation "for ever" or just the uninstallation of an older version.
I've update the COPR repo. I hope this will solve the problem for future users who upgrade the software.
I think I've found the problem: in the post uninstall section, I remove the files added after installation but I don't check if it's an uninstallation "for ever" or just the uninstallation of an older version.
I've update the COPR repo. I hope this will solve the problem for future users who upgrade the software.
Great news, thank you
@supdrewin did you have problems after updating the package on Arch ? Thank you.
Actually I test it just now. I try to fix PKGBUILD
and it work fine.
But if reinstall with a empty configuration when the ir emitter
work, configure may return a error configuration
which actually not work. To fix it, fully power off
the machine with adapter not plugged in, then start the machine and configure.
Yes this is expected, because the driver is already loaded. It can be fixed if I also generate (btw it can be easily done) the "disable" driver and in the uninstall script execute this one. But I think that it's feature a bit overkill.
An other way to fix this, is to know his driver value, add -v
to the configure command, answer "no" to the first question and then look at the debug in the terminal and input "y" when you see your driver. (even if the emitter blink for every question)
But if you think that a "disable" command can be usefull, I can implement it in a next update.
I updated today to 3.2 in Fedora 34, after the update it stopped working, I had to remove it and install again