Sending USSD message does not work

Bug #1351939 reported by Marius B. Kotsbak on 2014-08-03
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Modem Manager Gui
modem-manager-gui (Ubuntu)
modemmanager (Ubuntu)

Bug Description

The error message says:

"Error sending USSD"

"GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5"

This is reported upstream here:

Marius B. Kotsbak (mariusko) wrote :

There is a fixed version of modemmanager published here: bug I could not find the patch applied or if it is submitted upstream.

Changed in modem-manager-gui:
status: New → Confirmed
Alex (linuxonly) wrote :

I've attached patch used in this PPA. This patch wasn't submitted upstream. It simply forces Modem Manager 1.2.0 to use unencoded USSD request string first (like in earlier Modem Manager versions <= 0.6.2). It works at least for ZTE 180 modem and there is no side effects for modems that work fine without this patch (e.g. Huawei E1550, E173u1).

Marius B. Kotsbak (mariusko) wrote :

Hmm, strange. It seems like the change was done in this commit:

commit c6c1e0fb50569b9eafd92ba170a8dba42c4948be
Author: Aleksander Morgado <email address hidden>
Date: Sun Jul 22 14:36:32 2012 +0200

    broadband-modem: fallback to unencoded command in USSD if encoded fails

diff --git a/src/mm-broadband-modem.c b/src/mm-broadband-modem.c
index d707363..7f818fa 100644
--- a/src/mm-broadband-modem.c
+++ b/src/mm-broadband-modem.c

but that indicate that this should be used as fallback.

Alex (linuxonly) wrote :

Yes, but some modems (e.g. ZTE MF-180) can't handle any USSD request string after encoded one was used. So timeout error is returned by Modem Manager because modem is unable to handle fallback unencoded request string sent after encoded one.

The attachment "use-unencoded-ussd-by-default.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Marius B. Kotsbak (mariusko) wrote :

Hmm, so the only way to handle all modems is to have a list of modems that require encoding disabled?

Alex (linuxonly) wrote :

I don't know how to detect if encoding needed or not, so I guess that list of modems that require unencoded request strings is the most obvious solution.

Graham Inggs (ginggs) wrote :

Is this actually an issue in modemmanager?

Marius B. Kotsbak (mariusko) wrote :

Yes, it is. We should have an upstream bug report.

Changed in modem-manager-gui:
status: Confirmed → Invalid
Graham Inggs (ginggs) on 2014-10-27
Changed in modem-manager-gui (Ubuntu):
status: New → Invalid
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in modemmanager (Ubuntu):
status: New → Confirmed
EsAmo (esamokoram) wrote :


The device is ZTE MF820D.

After chaning the old modem to a 4G one I've got:
"GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Sending USSD command failed"

How do I apply a patch?

Regards & respect.

presfil (presfil) wrote :


My device is E3372.

After sending any USSD i've get error:
"GDBus.Error:org.freedesktop.ModemManader1.Error.Core.Failed: Invalid USSD response received: '^CCIN:2,0,"","",0'".

Modem Manager GUI 0.0.18-3
Linux Mint 18.1

In the previous version of the USSD went sometimes and sometimes not.

Please fix the bug.

John Smith (mintlooser) wrote :

I use a ZTE K3565-Z from Vodafone.
In Linuxmint 17 I managed to get this running with patched version from Alex by PPA.

In Linuxmint 18 I'm lost - USSD still not working, to balance and no top up from abroad possible.
The old PPA version does not work - no modem found.

Is there a chance to find a patched Xenial Version in PPA again? Would be great!!!!

John Smith (mintlooser) wrote :

I wonder if I could be of any help with this?
Could I contribute any error message?
Could I be of help in testing?

I'd like to see a solution to this issue.

Bayu Aditya H. (bayuah) wrote :

Try this:

Before sending the request, transfer the modem port to "silent" mode.

   echo -en 'AT^CURC=0\r\n' > /dev/ttyUSBx

Where ttyUSBx is the port of the modem with which modemmanager communicates.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers