From: austinrojers <austinrojers@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: USB tethering not working, might be due to a bug in 'usbmux' package.
Date: Tue, 14 Dec 2021 14:00:34 +0100 [thread overview]
Message-ID: <20211214130034.QYRa3GNxUWF3ncCoY0foX3y2PNDfI0ZSh1TEzMg48WI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34458@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
New comment by austinrojers on void-packages repository
https://github.com/void-linux/void-packages/issues/34458#issuecomment-993515069
Comment:
> The purpose of the udev rule is to autostart the daemon when a device is attached and kill it on detach
_You are right_; we should not remove the udev_rule; without this _udev-rule_, the USB tethering won't work if I remove my device and plug it in again. I verified it by restoring the _39-usbmuxd.rules_ file from my system snapshot and everything was fine again.
But the issue is this _udev-rule_ automatically runs `/usr/bin/usbmuxd` on boot, thus overriding the usbmuxd service, and nothing would work.
> In the absence of evidence that the systemd tag declaration actually causes a problem in the udev autostart rule, we should assume it takes no meaningful action and avoids carrying a patch for no purpose.
As evidence, killing this process `/usr/bin/usbmuxd` fixes everything.
So I would suggest that since this rule is required, you could edit the part of the rule that autostarts `/usr/bin/usbmuxd` on boot.
I have no knowledge about programming languages, so I have no idea about this.
Please patch this out, so this issue can be resolved; otherwise, I have to kill /usr/bin/usbmuxd every time on boot
Thank you
```
GNU nano 5.9 /usr/lib/udev/rules.d/39-usbmuxd.rules
# usbmuxd (Apple Mobile Device Muxer listening on /var/run/usbmuxd)
# systemd should receive all events relating to device
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{PRODUCT}=="5ac/12[9a][0-9a-f]/*|5ac/8600/*", TAG+="systemd"
# Initialize iOS devices into "deactivated" USB configuration state and activate usbmuxd
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{PRODUCT}=="5ac/12[9a][0-9a-f]/*|5ac/8600/*", ACTION=="add", ENV{USBMUX_SUPPORTED}="1", ATTR{bConfigurationValue}="0", OWNER="usbmux", RUN+="/usr/bin/usbmuxd --user usbmux --udev"
# Make sure properties don't get lost when bind action is called
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{PRODUCT}=="5ac/12[9a][0-9a-f]/*|5ac/8600/*", ACTION=="bind", ENV{USBMUX_SUPPORTED}="1", OWNER="usbmux", RUN+="/usr/bin/usbmuxd --user usbmux --udev"
# Exit usbmuxd when the last device is removed
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{PRODUCT}=="5ac/12[9a][0-9a-f]/*|5ac/8600/*", ACTION=="remove", RUN+="/usr/bin/usbmuxd -x"
```
next prev parent reply other threads:[~2021-12-14 13:00 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 5:19 [ISSUE] " austinrojers
2021-12-10 21:17 ` dotnetfox
2021-12-11 10:08 ` austinrojers
2021-12-11 10:08 ` [ISSUE] [CLOSED] " austinrojers
2021-12-11 19:02 ` dotnetfox
2021-12-11 19:03 ` dotnetfox
2021-12-12 3:12 ` austinrojers
2021-12-12 3:13 ` austinrojers
2021-12-12 3:14 ` austinrojers
2021-12-12 3:15 ` austinrojers
2021-12-12 3:15 ` austinrojers
2021-12-12 3:16 ` austinrojers
2021-12-12 4:39 ` dotnetfox
2021-12-12 4:40 ` dotnetfox
2021-12-12 4:52 ` dotnetfox
2021-12-12 5:33 ` austinrojers
2021-12-12 5:34 ` austinrojers
2021-12-12 5:37 ` austinrojers
2021-12-12 5:47 ` austinrojers
2021-12-12 5:48 ` austinrojers
2021-12-12 5:49 ` austinrojers
2021-12-12 5:50 ` austinrojers
2021-12-12 5:50 ` austinrojers
2021-12-12 6:02 ` austinrojers
2021-12-12 6:04 ` austinrojers
2021-12-12 6:04 ` austinrojers
2021-12-12 6:05 ` austinrojers
2021-12-12 6:09 ` dotnetfox
2021-12-12 6:30 ` austinrojers
2021-12-12 6:35 ` dotnetfox
2021-12-12 8:25 ` austinrojers
2021-12-12 8:58 ` dotnetfox
2021-12-12 8:58 ` dotnetfox
2021-12-12 12:19 ` austinrojers
2021-12-12 12:20 ` austinrojers
2021-12-12 12:35 ` austinrojers
2021-12-12 12:38 ` austinrojers
2021-12-12 12:39 ` austinrojers
2021-12-12 16:55 ` dotnetfox
2021-12-12 16:57 ` dotnetfox
2021-12-12 17:02 ` dotnetfox
2021-12-12 17:03 ` dotnetfox
2021-12-13 3:17 ` austinrojers
2021-12-13 3:18 ` austinrojers
2021-12-13 3:20 ` austinrojers
2021-12-13 3:33 ` austinrojers
2021-12-13 3:33 ` austinrojers
2021-12-13 6:11 ` austinrojers
2021-12-13 6:13 ` austinrojers
2021-12-13 6:13 ` austinrojers
2021-12-13 6:16 ` austinrojers
2021-12-13 9:20 ` austinrojers
2021-12-14 11:07 ` dotnetfox
2021-12-14 11:21 ` dotnetfox
2021-12-14 11:56 ` ahesford
2021-12-14 13:00 ` austinrojers [this message]
2021-12-14 13:01 ` austinrojers
2021-12-14 13:20 ` ahesford
2021-12-14 13:50 ` austinrojers
2021-12-14 13:51 ` austinrojers
2021-12-14 13:51 ` austinrojers
2021-12-14 14:17 ` ahesford
2021-12-14 14:41 ` dotnetfox
2021-12-14 14:49 ` austinrojers
2021-12-14 15:11 ` ahesford
2021-12-14 15:18 ` austinrojers
2021-12-14 15:30 ` austinrojers
2021-12-14 15:31 ` dotnetfox
2021-12-14 15:31 ` austinrojers
2021-12-14 15:35 ` austinrojers
2021-12-14 15:52 ` austinrojers
2021-12-14 15:53 ` austinrojers
2021-12-14 15:53 ` austinrojers
2021-12-14 16:03 ` dotnetfox
2021-12-14 16:29 ` austinrojers
2021-12-14 16:43 ` dotnetfox
2021-12-14 16:54 ` austinrojers
2021-12-14 16:55 ` austinrojers
2021-12-14 17:31 ` dotnetfox
2021-12-14 18:00 ` austinrojers
2021-12-15 7:22 ` austinrojers
2021-12-15 7:22 ` austinrojers
2021-12-15 11:52 ` ahesford
2021-12-15 12:52 ` austinrojers
2021-12-15 12:58 ` austinrojers
2021-12-20 17:20 ` austinrojers
2021-12-21 1:19 ` dotnetfox
2021-12-21 1:28 ` dotnetfox
2021-12-21 4:15 ` austinrojers
2021-12-21 4:25 ` austinrojers
2021-12-21 4:25 ` austinrojers
2021-12-21 4:26 ` austinrojers
2021-12-21 9:26 ` dotnetfox
2021-12-23 4:50 ` austinrojers
2022-06-18 2:13 ` github-actions
2022-07-03 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20211214130034.QYRa3GNxUWF3ncCoY0foX3y2PNDfI0ZSh1TEzMg48WI@z \
--to=austinrojers@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).