Bug 86658

Just watched the first 10s of the video :)

Before trying to run "$> sudo /usr/sbin/ModemManager --debug", did you do the steps from the previous paragraph? This is, did you do these?
$> sudo mv /usr/sbin/ModemManager /
$> sudo killall -TERM ModemManager

Enter all commands in a terminal? I have Ubuntu 14.10 i use system initialization upstart, and therefore enter commands for option without systemd:
$> sudo mv /usr/sbin/NetworkManager /
$> sudo mv /usr/sbin/ModemManager /
$> sudo killall -TERM NetworkManager
$> sudo killall -TERM ModemManager

thereafter
$> sudo /usr/sbin/ModemManager —debug
$> sudo /usr/sbin/NetworkManager --no-daemon --log-level=DEBUG


And then what? I typed these commands:
$> sudo mv /ModemManager /usr/sbin/
$> sudo mv /NetworkManager /usr/sbin/

But he writes: stat failed for «/ ModemManager»: No such file or directory

If my comments seem rude, then please make allowances for my terrible english ...

(In reply to Tamir from comment #3)
> If my comments seem rude, then please make allowances for my terrible
> english ...

:) np

I actually just found out that the steps are *wrong* when not using systemd, your case. The steps should be these:

$> sudo mv /usr/sbin/NetworkManager /
$> sudo mv /usr/sbin/ModemManager /
$> sudo killall -TERM NetworkManager
$> sudo killall -TERM ModemManager
$> sudo /ModemManager —debug
$> sudo /NetworkManager --no-daemon --log-level=DEBUG
(do your tests here)
$> sudo mv /ModemManager /usr/sbin/
$> sudo mv /NetworkManager /usr/sbin/


So, the debug commands should be run in different terminals, and leave them running through your tests:
[terminal 1] $> sudo /ModemManager --debug
[terminal 2] $> sudo /NetworkManager --no-daemon --log-level=DEBUG

Those commands will dump to the standard output all the debug logs of both MM and NM. What we need to see is what those logs say.

I'll update the instructions page.

Created attachment 109948 [details]
ModemManager —debug

Created attachment 109949 [details]
networkmanager debug

(In reply to Tamir from comment #5)
> Created attachment 109948 [details]
> ModemManager —debug

Seems that the MM wasn't run in debug mode; did you run it with "--debug" ?

Yes, sorry, now attach the new log to test

Created attachment 109952 [details]
ModemManager--debug

(In reply to Tamir from comment #9)
> Created attachment 109952 [details]
> ModemManager--debug

Could you attach the full log? I'm missing all the initial part of the log, which is (among other things) where the decision of which port to use for data vs control is done...

Now I will try, I just run in different terminals debug, and so the two logs with incomplete data ... try to piece together

Created attachment 109953 [details]
full log debug networkmanager

Created attachment 109954 [details]
debug modem manager

(In reply to Tamir from comment #13)
> Created attachment 109954 [details]
> debug modem manager

Sorry, but it isn't in debug mode... :/

Not sure why you put this:
  sudo /ModemManager —debug
instead of this:
  sudo /ModemManager --debug

Try to put dash-dash-debug, don't copy&paste it.

Created attachment 109956 [details]
--debug ModemManager --full log

Created attachment 109957 [details]
networkmanager full log

For NetvorkManager was such a message after entering commands (NetworkManager: 23798): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: The key file does not contain a group of «connectivity»

(In reply to Tamir from comment #17)
> For NetvorkManager was such a message after entering commands
> (NetworkManager: 23798): GLib-WARNING **: GError set over the top of a
> previous GError or uninitialized memory.
> This indicates a bug in someone's code. You must ensure an error is NULL
> before it's set.
> The overwriting error message was: The key file does not contain a group of
> «connectivity»

That one is a bug in NetworkManager, shouldn't prevent you from connecting the modem.

I believe the issue is that we don't properly parse the GETPORTMODE result:
 ^GETPORTMODE: TYPE: WCDMA: ,pcui:1,modem:2,ncm:3,mass:4,mass_two:5,

We don't expect those strings for pcui and modem, so we're not properly using the info to decide which port should be used for data. I'll prepare a patch.

Thank you for your time and willingness to correct mistakes, waiting to solve the problem

Created attachment 109961 [details] [review]
Expect "pcui" and "modem" in ^GETPORTMODE response

Could you test with a self-compiled ModemManager with the attached patch applied?

All right. What should I do? Where to install the patch?

I will try to tell you about the request for launchpad Ubuntu, there is a bug-report on this subject - https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1354823

(In reply to Tamir from comment #23)
> I will try to tell you about the request for launchpad Ubuntu, there is a
> bug-report on this subject -
> https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1354823

Not sure if that affects you, truth be told, you already have the TTYs.

(In reply to Tamir from comment #22)
> All right. What should I do? Where to install the patch?

Which Ubuntu version are you using, and which arch?

The manual steps would involve (installing in /usr/local, so that it doesn't collide with your system installed MM):

$ sudo apt-get install git
$ sudo apt-get build-dep modem-manager
$ git clone git://anongit.freedesktop.org/ModemManager/ModemManager
$ cd ModemManager
$ wget https://bugs.freedesktop.org/attachment.cgi?id=109961
$ git am attachment.cgi?id=109961
$ ./autogen.sh
$ make
$ sudo make install
$ sudo mv /usr/sbin/ModemManager /
$ sudo killall -TERM ModemManager
$ sudo /usr/local/sbin/ModemManager --debug

(more or less I guess)

> $ sudo apt-get build-dep modem-manager
Reading package lists ... Done
Building dependency tree
Reading state information ... Done
E: Could not find a source package for modem-manager

Ubuntu 14.10 
3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

(In reply to Tamir from comment #26)
> > $ sudo apt-get build-dep modem-manager
> Reading package lists ... Done
> Building dependency tree
> Reading state information ... Done
> E: Could not find a source package for modem-manager

Gah, you'll need to use the correct package name, I don't know what that is in Ubuntu.

Found written together modemmanager, like this:
sudo apt-get build-dep modemmanager

tr@tr-lp:~/ModemManager$ git am attachment.cgi?id=109961

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'tr@tr-lp.(none)')
You need to set your committer info first

(In reply to Tamir from comment #30)
> tr@tr-lp:~/ModemManager$ git am attachment.cgi?id=109961
> 
> *** Please tell me who you are.
> 
> Run
> 
>   git config --global user.email "you@example.com"
>   git config --global user.name "Your Name"
> 
> to set your account's default identity.
> Omit --global to set the identity only in this repository.
> 
> fatal: unable to auto-detect email address (got 'tr@tr-lp.(none)')
> You need to set your committer info first


  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

:)

git am attachment.cgi ..my name Tamir or id...? What id?

(In reply to Tamir from comment #32)
> git am attachment.cgi ..my name Tamir or id...? What id?

It doesn't matter what you put there. That is just to apply the patch.

sorry :). Here is another:
tr @ tr-lp: ~ / ModemManager $ make
make: *** No targets specified and is not found make-file. Stop.

(In reply to Tamir from comment #34)
> sorry :). Here is another:
> tr @ tr-lp: ~ / ModemManager $ make
> make: *** No targets specified and is not found make-file. Stop.

did you ./autogen.sh ?

(In reply to Aleksander Morgado from comment #35)
> did you ./autogen.sh ?
Yes, attach

Created attachment 110006 [details]
autogen

there is an error:
configure: error: Couldn't find libmbim-glib. Install it, or otherwise configure using --without-mbim to disable MBIM support.

(In reply to Tamir from comment #38)
> there is an error:
> configure: error: Couldn't find libmbim-glib. Install it, or otherwise
> configure using --without-mbim to disable MBIM support.

For the purpose of the test, just:
./autogen.sh --without-mbim --without-qmi

Reboot the system after installing the necessary? If not then tried, the result attached. Modem longer trying to connect, but the result is again - the detached

Created attachment 110013 [details]
sudo /usr/local/sbin/ModemManager --debug

(In reply to Tamir from comment #41)
> Created attachment 110013 [details]
> sudo /usr/local/sbin/ModemManager --debug

Could not acquire the 'org.freedesktop.ModemManager1' service name

That just means that there is another ModemManager running. Did you mv the binary and killall -TERM before trying to run with --debug?

tr @ tr-lp: ~ $ sudo mv / usr / sbin / ModemManager /
[sudo] password for tr:
mv: stat failed for «/ usr / sbin / ModemManager»: No such file or directory
tr @ tr-lp: ~ $

(In reply to Tamir from comment #43)
> tr @ tr-lp: ~ $ sudo mv / usr / sbin / ModemManager /
> [sudo] password for tr:
> mv: stat failed for «/ usr / sbin / ModemManager»: No such file or directory
> tr @ tr-lp: ~ $

There shouldn't be any whitespace between the elements of a path, so no whitespaces between "/" and "usr"  and so on...

Didn't know it would be so difficult for you to test this, do you prefer me to build a custom MM ubuntu package instead? It will take me longer, but will be easier for you to test.

In the terminal I typed without gaps:
sudo mv /usr/sbin/ModemManager /
mv: stat failed for «/usr/sbin/ModemManager»: No such file or directory
> tr @ tr-lp: ~ $
or
sudo mv /usr/sbin/ModemManager/
mv: after the «/usr/sbin/ModemManager/» missing operand target file
At the command «mv --help» to get more information.

If possible, it is likely to be more productive to have a ready-made package for testing. I have little experience with such things, unfortunately. Everything that I have a desire to correct mistakes for comfortable work in OS.

The patch is really a minor change, plus Dan also reviewed it, so I pushed it to git master and the MM-1-4 branch. It should get into the next stable 1.4.x release soon.

Aleksander Morgado thank you very much for your time and effort spent to fix this problem. Let's try a new version)