From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Solaar udev rules are not applied
Date: Tue, 12 Oct 2021 15:22:41 +0200 [thread overview]
Message-ID: <20211012132241.rLsheuT7YL12Zm4Jzrtu-Qz88g4mT9OA3zw9QaCZOx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33422@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]
Closed issue by Meister1593 on void-packages repository
https://github.com/void-linux/void-packages/issues/33422
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.13.19_1 x86_64 AuthenticAMD notuptodate rrrmFFFFF
* package:
Solaar-1.0.6_1
### Expected behavior
When running program for first time, you might only see error message (example bellow) once about re-plugging your usb dongle for mouse and afterwards it shouldn't say about that, allowing detection and working with mouse properly
### Actual behavior
When running program it always shows error message bellow, and you can't do much because of it.
### Steps to reproduce the behavior
1. Install Solaar
2. Open Solaar
3. Error message appears every time
or
1. Install Solaar
2. Reload and trigger udev rules (`udevadm control --reload-rules && udevadm trigger`)
3. Open Solaar
4. Error message appears every time
### Potential clues
I thought that rules were not applied because of some issues with app itself, but looking at Solaar's archive contents (it had rules.d with rules), this is not the case.
But then i checked out where rules actually are installed in system, and they went into `/usr/share/solaar/udev-rules.d/42-logitech-unify-permissions.rules` instead of `/usr/lib/udev/rules.d/42-logitech-unify-permissions.rules`
After that i configured udev to run with debug logging (probably not needed) and tested with udevadm the same device (`/dev/hidraw3`), it gave me a list of rules that it reads and there was no `/usr/share/solaar/udev-rules.d` path
Lastly, i checked maybe package had this - and it did, in [this](https://github.com/void-linux/void-packages/commit/5ff792f86eab693bbe649de9ae8864e3b6449c3c#diff-d076aad4591896aba208d138d3ba5b10b6b2a0c0311dcc2e9937f54c6f300d25) commit it had copying rules to proper path (as well as [here](https://github.com/void-linux/void-packages/blob/dd122baf86f513f326cb6d99657c12d8785bef75/srcpkgs/Solaar/template). But then at [this](https://github.com/void-linux/void-packages/blob/c33c5bc603b00c75e936e72300642d6fb84dcbdd/srcpkgs/Solaar/template) commit this has been changed and important rule copying just got deleted.
Was it intentional or just a mistake?
prev parent reply other threads:[~2021-10-12 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 10:22 [ISSUE] " Meister1593
2021-10-08 16:16 ` NeelChotai
2021-10-12 13:22 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211012132241.rLsheuT7YL12Zm4Jzrtu-Qz88g4mT9OA3zw9QaCZOx8@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).