[SOLVED] USSD not working after upgrading to Ubuntu 14.04 from Modem Manager Gui
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USSD not working after upgrading to Ubuntu 14.04 from Modem Manager Gui
I use Modem Manger GUI for executing USSD commands for getting information about balance, validity etc. It worked fine in Ubuntu 12.04 Precise. However after upgrading to Ubuntu 14.04 Trusty, I found that when I send USSD command, I get a timeout error, but SMS, network traffic and all other tabs in Modem Manager GUI work fine. The Internet is working as well. Only somehow the ussd commands are not working. I have tried increasing the timeout (upto 40 sec), changing backends as posted here, and using PrepaidManager and mmcli commands from terminal. However, all show the same timeout error.
Modem : ZTE corporation MF190 (from ModemManger GUI).
Edit :
Here are the results of mmcli commands. I found the commands here.
Here is the last few lines of my dmesg after executing the command :
Code:
[ 16.576775] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 16.629129] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=0117
[ 16.629135] usb 1-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 16.629137] usb 1-1.3: Product: ZTE WCDMA Technologies MSM
[ 16.629139] usb 1-1.3: Manufacturer: ZTE,Incorporated
[ 16.629141] usb 1-1.3: SerialNumber: MF1900ZTED010000
[ 16.715105] type=1400 audit(1489112706.713:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=788 comm="apparmor_parser"
[ 16.859643] usb-storage 1-1.3:1.3: USB Mass Storage device detected
[ 16.859687] scsi8 : usb-storage 1-1.3:1.3
[ 16.914313] usbcore: registered new interface driver usbserial
[ 16.914331] usbcore: registered new interface driver usbserial_generic
[ 16.914339] usbserial: USB Serial support registered for generic
[ 17.129872] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory
[ 17.171047] usbcore: registered new interface driver option
[ 17.171331] usbserial: USB Serial support registered for GSM modem (1-port)
[ 17.171572] option 1-1.3:1.0: GSM modem (1-port) converter detected
[ 17.171763] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB0
[ 17.171791] option 1-1.3:1.1: GSM modem (1-port) converter detected
[ 17.171887] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB1
[ 17.171910] option 1-1.3:1.2: GSM modem (1-port) converter detected
[ 17.172015] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2
Also, can you please tell me why the following AT command that you gave me fails?
Code:
subhraman ~:~> mmcli -v -m 0 --command="E0"
[10 Mar 2017, 08:22:26] [Debug] ModemManager process found at ':1.3'
[10 Mar 2017, 08:22:26] [Debug] Assuming '0' is the modem index
[10 Mar 2017, 08:22:26] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/0'
[10 Mar 2017, 08:22:26] [Debug] Synchronously sending command to modem (29 seconds timeout)...
error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot send AT command to modem: operation only allowed in debug mode'
I have added the -v option for getting verbose output.
Last edited by Subhraman Sarkar; 03-10-2017 at 10:47 AM.
Reason: Added information.
subhraman ~:~> mmcli -v -G DEBUG
[11 Mar 2017, 18:39:02] [Debug] ModemManager process found at ':1.3'
Successfully set logging level
subhraman ~:~> mmcli -v -m 2 --command="E0"
[11 Mar 2017, 18:39:08] [Debug] ModemManager process found at ':1.3'
[11 Mar 2017, 18:39:08] [Debug] Assuming '2' is the modem index
[11 Mar 2017, 18:39:08] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'
[11 Mar 2017, 18:39:08] [Debug] Synchronously sending command to modem (29 seconds timeout)...
error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot send AT command to modem: operation only allowed in debug mode'
subhraman ~:~> mmcli -v -m 2 -e
[11 Mar 2017, 18:39:15] [Debug] ModemManager process found at ':1.3'
[11 Mar 2017, 18:39:15] [Debug] Assuming '2' is the modem index
[11 Mar 2017, 18:39:15] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'
[11 Mar 2017, 18:39:15] [Debug] Synchronously enabling modem...
successfully enabled the modem
subhraman ~:~> mmcli -v -m 2 --3gpp-ussd-initiate
error: no actions specified
subhraman ~:~> mmcli -v -m 2 --3gpp-ussd-initiate="*111#"
[11 Mar 2017, 18:39:50] [Debug] Forcing request to be run asynchronously
[11 Mar 2017, 18:39:50] [Debug] Assuming '2' is the modem index
[11 Mar 2017, 18:39:50] [Debug] ModemManager process found at ':1.3'
[11 Mar 2017, 18:39:50] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/2'
[11 Mar 2017, 18:39:50] [Debug] Asynchronously initiating USSD session...
error: couldn't initiate USSD session: 'Timeout was reached'
What should I do next to solve this problem? Should I try
(A) Upgrading ModemManager using deb files from xenial repository or files from any other newer version.
(B) Switching to a ModemManager alternative such as Wader-core or oFono.
Can this be a problem in the modem or service provider (though I don't think this likely)?
Last edited by Subhraman Sarkar; 03-11-2017 at 07:19 AM.
I was unable to upgrade ModemManger due to dependency problems, because I already had ModemManger 1.0.0-2ubuntu1.1 version, which was the latest for trusty. However, I managed to downgrade ModemManager to version 0.6.0.0.really-0ubuntu7_amd64 and the ussd worked. I think it is probably a problem with ModemManager. What do you say about this?
If your ModemManger isn't able to upgrade, that means that your ModemManger is corrupted. Some module relative to ModemManger doesn't match each other.
I have tried upgrading to ModemManager 1.4.12-1ubuntu1, but after upgrade it refuses to show my Mobile Broadband connections. It only shows Wired, Wireless and other connections, but not Mobile Broadband connections. Also,
Code:
mmcli -m 1 -e
shows a dialog notifying me that it requires the sudo password for unlocking (the dialog shows some problem with System Policy Kit). Even if I provide the password, my my Mobile Broadband connections do not show up. For now, I will be using ModemManager 0.6.
Thank you very much for your help.
Last edited by Subhraman Sarkar; 03-25-2017 at 05:23 AM.
Looks like my problem has been mentioned as a bug here, https://bugs.launchpad.net/ubuntu/+s...i/+bug/1351939.
I am now using ModemManager 1.4.12-1ubuntu1_amd64 in Ubuntu 16.04. I had upgraded to Ubuntu 16.04 Xenial. But the problem still followed. Today I found a patch in the bug report. I applied it and the ussd began working. Regards.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.