So in Ubuntu 20.04 (a.k.a Focal) we already had that in place, were you using Focal before and upgraded to Jammy (22.04)? Or is this a new installation? If you upgraded, had you experienced this issue before?
There is a patch (d/p/gpsd_hotplug_rules_disable_generic_serial_converters) in the debian package disabling a similar udev rule at the top of the file indeed:
-ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK+="gps%n", @UDEVCOMMAND@
+# rule disabled in Debian as it matches too many other devices
+# ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK+="gps%n", @UDEVCOMMAND@
It seems to be created before they added the other udev rule at the bottom at the file, someone might have forgotten to update the patch. I believe we should address it in the debian package and update the patch.
I also believe this is an issue to be discussed with upstream anyway. Could you try to report a bug upstream here [1]? If you do so, could you please link it here so we can track it?
Thanks for taking the time to report this bug and trying to make Ubuntu better.
This rule at the end of the file was added by upstream 4 years ago:
https:/ /gitlab. com/gpsd/ gpsd/-/ commit/ c0c0e53d7fe400c de49398bdcce024 fb9eb1d51b
So in Ubuntu 20.04 (a.k.a Focal) we already had that in place, were you using Focal before and upgraded to Jammy (22.04)? Or is this a new installation? If you upgraded, had you experienced this issue before?
There is a patch (d/p/gpsd_ hotplug_ rules_disable_ generic_ serial_ converters) in the debian package disabling a similar udev rule at the top of the file indeed:
-ATTRS{ idVendor} =="067b" , ATTRS{idProduct }=="2303" , SYMLINK+="gps%n", @UDEVCOMMAND@ =="067b" , ATTRS{idProduct }=="2303" , SYMLINK+="gps%n", @UDEVCOMMAND@
+# rule disabled in Debian as it matches too many other devices
+# ATTRS{idVendor}
It seems to be created before they added the other udev rule at the bottom at the file, someone might have forgotten to update the patch. I believe we should address it in the debian package and update the patch.
I also believe this is an issue to be discussed with upstream anyway. Could you try to report a bug upstream here [1]? If you do so, could you please link it here so we can track it?
[1] https:/ /gitlab. com/gpsd/ gpsd/-/ issues/ new