The Ubuntu package has been updated to remove the C rewrite and use the
upstream tcl version now which should fix the issue
https://launchpad.net/ubuntu/+source/usb-modeswitch/2.6.0-2ubuntu1
We are not going to add tcl as a depends in a stable update though so
the C code bug is still going to
I just spent a few hours trying to figure out why my Alcatel modem
wasn't establishing a connection...and ran across this bug. Thank you
Hanno for the workaround!
I uninstalled the usb_modeswitch package and installed the one from
Debian Bullseye, and my modem shows up now! After adding entries
The dot in the kernel name of a USB device indicates that a device is connected
via a hub.
In theory, this can even be cascaded, leading to names like "2-1.2.1.3.4"
So the hardware difference is that the ports in the Toshiba are not
'primary' but exposed through an internal hub as opposed to the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: usb-modeswitch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
To further clarify the impact of different hardware on bug occurrence:
The difference in Mariusz' hardware (Dell vs. Toshiba) leads to
different kernel names ("3-4" on Dell vs. "2-1.2" on Toshiba). So
"device validation" only happened on his Toshiba (thereby updating iface
to the wrong value of
I am likely experiencing the same issue, yet on other hardware: Ubuntu
20.04 with a ZTE MF100 modem but only on Raspberry Pi. The good news: I
have triaged the issue.
The bug is in "usb_modeswitch_dispatcher.c", a C rewrite of the upstream
Tcl script. The C dispatcher receives the modem's
Please note that on a Dell laptop everything works as expected. The
difference most probably is caused by hardware in the laptop. Two
different modems do not work with Toshiba and both of them work with
Dell. The same up-to-date "focal fossa" system.
--
You received this bug notification because
Without being familiar with the Ubuntu flavour of usb_modeswitch - can
this be a permission issue?
Does the usb_modeswitch wrapper and program run in the proper user /
group context? It needs to be able to read attributes in the "sys" tree.
If the permissions are not correct, that would explain
Make the comment on Kubuntu irrelevant.
I have launched Kubuntu Live CD daily and the same behavior can be observed.
The laptop is Toshiba Satellite L755.
Let me know if I can provide any further useful information.
--
You received this bug notification because you are a member of Desktop
On Kubuntu @ Dell with the same modem:
cat /var/log/usb_modeswitch.log
USB_ModeSwitch log from Thu Mar 12 20:09:49 2020
Use global config file: /etc/usb_modeswitch.conf
Adjust delay for USB storage devices ...
Error: could not access delay_use attribute: No such file or directory
Raw args
Yes. I mistyped the attribute name. Exact log is:
$ cat /var/log/usb_modeswitch.log
USB_ModeSwitch log from Thu Mar 12 19:25:36 2020
Use global config file: /etc/usb_modeswitch.conf
Raw args from udev: 2-1.2
Bus ID for device not given by udev.
Trying to determine it from kernel name
** Tags added: focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926
Title:
usb_modeswitch does not switch modems (remain visible as mass storage)
Status in
There is no SCSI attribute named ref but there is one named rev.
This is likely to be a typo from ubuntu rewrite of the original
usb_modeswitch_dispatcher.tcl which reads the rev attribute.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Package changed: ubuntu => usb-modeswitch (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926
Title:
usb_modeswitch does not switch modems (remain visible as
14 matches
Mail list logo