Public bug reported:
If you have a modem whose switching is normally working successfully by
usb_modeswitch, installing wader-core prevents it from functioning.
After turning on debugging in usb_modeswitch it can be seen that after
installation of wader-core usb-modeswitch no longer finds the correct
sysfs path. I've attached two logs, one with Modem Manager installed,
and functioning switching, one with Wader and non functioning switching.
It appears that the command line arguments are different in the two
calls
Wader:
/lib/udev/usb_modeswitch '1-3:1.0/1-3:1.0'
Modem Manager:
/lib/udev/usb_modeswitch '/1-3:1.0'
This can be traced back to the usb_modeswitch's use of udev variables
substitution '%b/%k'. It seems that Udev unly populates those
substitutions if any rule makes use of a related variable. It seems that
Modem Manager did not cause %b to be populated, whereas Wader did. I've
attached a patch that changes Wader's udev rules to be more like Modem
Manager's, tested with 50+ modems I have and I'm happy that this patch
should be applied to work around the issue. I would like to point out
that at some point this is likely to happen again to usb_modeswitch when
triggered by some 3rd party udev ruleset, as the root cause would seem
to be that usb_modeswitch uses a substitution that once populated stops
the device being found.
** Affects: wader (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988365
Title:
Usb_modeswitch doesn't switch when wader is installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wader/+bug/988365/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
