Please note the libmbim 1.24 branch is not actively maintained any more
in upstream. If you want to keep on using that release, you're fully on
your own.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
> The snap "dpr-wwan_1.0-wwan-test_amd64.snap" is provided by Lenovo
(not published yet)
Is there any estimated date when it will be released?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
And where is the dpr-wwan_1.0-wwan-test_amd64.snap file?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https://bugs.launchpad.net/bugs/1934286
Title:
Update the ModemManager to 1.16.6-2 to support some modems in
Public bug reported:
Installed a 18.04 server image, and installed NetworkManager.
NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10-globally-
managed-devices.conf" file where it speciefies that all devices are by
default unmanaged except for types "wifi" and "wwan".
Now, the
For reference, I'm testing with a F3507g, and it seems that this modem
does receive and store the string properly:
AT*EIAAUW=2,1,"p...@a1plus.at","ppp"
OK
AT*EIAAUR=2,1
*EIAAUR: 2,1,"p...@a1plus.at","ppp",00111,0
--
You received this bug notification because you are a member of Desktop
(In reply to Aleksander Morgado from comment #17)
> (In reply to russianneuromancer from comment #16)
> > And in case it could help someone, this workaround systemd unit helps me.
> > With this unit connection could be established after suspend.
>
> Did you compile Modem
(In reply to russianneuromancer from comment #20)
> Hi
>
> Any news?
Yes, see: https://lists.freedesktop.org/archives/modemmanager-
devel/2017-August/005668.html
Could you apply the patch in a custom build and retry, to see if it
fixes your issue?
--
You received this bug notification because
If you want to apply it on a 1.6.x version, use this patch instead:
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=mm-1-6=196b8d619ad16d625ab0cc520854c2a044c0e4eb
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim
(In reply to russianneuromancer from comment #16)
> And in case it could help someone, this workaround systemd unit helps me.
> With this unit connection could be established after suspend.
Did you compile ModemManager with 'systemd' suspend/resume support?
Ideally, MM should detect the
(In reply to Adrian Perez de Castro from comment #10)
> I also have this issue, with a Fujitsu S936 laptop which includes an EM7305.
> After adding the udev rules in the post at 0xf8.org (modifying them to fit
> use the USB identifier that shows in my laptop, 1199:9041), the “mbim-proxy”
>
ool source package in Artful:
Fix Committed
Bug description:
[Impact]
An old bug in intltool breaks out-of-tree builds, including "make
distcheck", in a lot of intltool-using projects when automake version
is 1.15 or newer.
The fix for this issue (by Aleksander Morgado) is provid
Yeah I know, it's just not my problem any more. Everyone should migrate,
gettext is at least maintained.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to intltool in Ubuntu.
https://bugs.launchpad.net/bugs/1117944
Title:
intltool
intltool is dead, long live gettext-only :)
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=984625165e09f02b4d6b8389092d5055fdbb0f03
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to intltool in Ubuntu.
"WTF broke my distcheck!", then apply it to N projects using intltool,
sum the amount of hours wasted by everyone applying workarounds in their
own projects...
I have to admit this is very very sad.
A bug like this one, affecting every project using intltool, with one
suggested patch even, still
For reference, what projects are doing:
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=1ae6a7be8abab4b13520679f42c6cc8e2fb57d05
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/po/POTFILES.skip?id=66c3b673e32b7d055349a2a96ca2c2dfbbfc03ba
Comment on attachment 118426
Increase the retry interval to 5 seconds.
This breaks the timeout value given by the user. In open_message_ready()
we'll do a ctx->timeout--; if we got a timeout error, so that we can
retry. Instead of ctx->timeout--; there should be a ctx->timeout-=5
there, and along
Merged the patch to mbim-1-12 and git master, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
Status
Since ModemManager 1.0, allowed/preferred modes aren't retrieved from
NetworkManager connection settings; instead explicit calls in the MM API
are required:
https://sigquit.wordpress.com/2013/06/03/changing-modes-and-
capabilities-in-modemmanager/
** Changed in: modemmanager (Ubuntu)
I'm assuming those ttys are not to be treated as modem ttys; so long story
short, you'll need to blacklist them for now in MM udev rules... I fixed this
already in git master and the mm-1-4 branch for this specific MediaTek device,
so will be available in the next releases:
Marius, could you ask the original reporter about the concerns Lars had?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1404068
Title:
No internet connection with Huawei
Also, may be not modeswitched properly? See:
http://askubuntu.com/questions/525965/huawei-e3272-ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1404068
Title:
No
Merged branch to git master.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1057834
Title:
Haier CE81B is not detected on 12.04
Status in ModemManager (with NetworkManager
(In reply to Airlangga Cahya Utama from comment #9)
Hello Aleksander,
Thank you for your patch.
I'm a bit busy atm.
I'll try to look out for fedora source build this
weekend.
When does the merge window happen?
There's no merge window; as soon as you test it, if it works OK, I'll
merge
(In reply to Dan Williams from comment #7)
aleksander/haier-plugin looks good to me.
I tried to ping the original reporter to see if he can test the patch;
it's pretty much very low risk I would say anyway, so if we don't get
tests back I'll just merge it.
--
You received this bug notification
Superb!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue in Ubuntu.
https://bugs.launchpad.net/bugs/977761
Title:
Add support for using QMI protocol
Status in GNOME Control Center:
Fix Released
Status in GNOME Shell:
Fix
*** This bug is a duplicate of bug 1099766 ***
https://bugs.launchpad.net/bugs/1099766
So, yeah, just make this bug a duplicate of a private bug which cannot
be looked at; and while doing the duplication, make sure the attachments
of this bug get also removed so that no one can look at
In ModemManager 1.x, the current power state of the modem is not assumed
when the modem is enabled; i.e. we always re-check current power status
before trying to power-up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in
Done in git master;
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=0dd93549a175f05cd5290ca8b3a3fd78e59863b5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1229748
MBIM support is now merged into ModemManager git master, and a
preliminary version of libmbim is already available:
http://www.freedesktop.org/software/libmbim/libmbim-0.0.1.tar.xz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Marius: out of curiosity, did you try MM git master with this modem? Did
it work ok?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1167852
Title:
[0bdb:1926] REGRESSION:
Ok, so the MM_06 branch in git is actually free of your problem. Your issue is
fixed (99% chance :)) in the following commit:
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=MM_06id=5d854a32cf2d04cbdb3d16f019d277caaba69ab4
So, either compile directly that branch, or ask Ubuntu
Whoever gets this issue again, please make sure to grab SYSLOG around
the time of the *crash* (not the connection issue), and attach it here
:)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Please try with latest stable ModemManager 0.6.x, and get debug logs:
https://wiki.ubuntu.com/DebuggingModemmanager
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1088984
In the case of errors in call management; those are already passed back
to NetworkManager, but they get lost in there without getting to the UI
probably.
And for the case of the no SIM errors, you're right, the UI may not want
to spam the user with notifications about the missing SIM; but it may
The first step is to let MM say why it is in Failed state; then the UI
can pick that up and show the proper message to the user.
See https://bugzilla.gnome.org/show_bug.cgi?id=691778
** Bug watch added: GNOME Bug Tracker #691778
https://bugzilla.gnome.org/show_bug.cgi?id=691778
--
You
Restarting the applet does nothing; if the logic got stuck somewhere,
you much better killall -9 modem-manager and/or restart NetworkManager
directly; that should be equivalent to a reboot.
Also, please attach ModemManager debug logs as per:
https://wiki.ubuntu.com/DebuggingModemmanager
And
Wader is another program offering the same DBus interface as
ModemManager offers. NetworkManager can play well both with Wader and
ModemManager.
I would still like to see debug logs of ModemManager running with this
modem, to see why we don't handle it well, while Wader does. So, please,
anyone,
Current MM in Ubuntu fully ignores WWAN ports handled using the QMI
protocol; which means the modem is stuck to use PPP over a serial port.
That method seems to be enough for slower connections like GSM/HSPA, but
definitely not for LTE.
The fix for this is to use QMI and the WWAN port, as done in
@Marius: in your modems, are you using PPP for LTE? Maybe it's a Huawei-
only issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1042456
Title:
Huawei e398 doesn't work
Status in
Don't know; have not played with that modem. But what I can tell is that
using AT+PPP in such a modem is probably a fallback method which is not
supposed to be used... LTE speeds need a net port, PPP just introduces
too much unnecessary overhead.
--
You received this bug notification because you
Try to run nm-connection-editor and create a mobile broadband connection
setup for your provider. Once done, it should appear in the shell menu
and it also may be activated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Weird... is this happening for every LTE modem out there?
We could have a new property in MMBroadbandModem specifying that +CSQ is
always preferred over +CIND for signal quality updates (talking about
git master here), so that plugins can set it when that happens.
Or, if the issue is really more
On 10/03/2012 02:19 PM, Marius Kotsbak wrote:
Well, those two modems have in common that they are both using Qualcomm
chipsets (supporting QMI protocol), so it might just be a bug there.
I think there is such property in place, at least in the MM_06 branch.
The question is just when we want
+CSQ is usually defined as a value between 1 and 31; plus 99 for
unknown. ModemManager scales this value to the expected [0,100] range.
The signal strength reported with QMI is based on RSSI, which we then
convert to the same [0,100] range.
--
You received this bug notification because you are
Not really, no. What I'm not sure is why CIND is preferred over CSQ by
default.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1060831
Title:
Sierra/ZTE LTE modem
Backporting the QMI support from MM git master (0.7) to 0.5/0.6 is a
thousand times more complex than improving NetworkManager to support MM
0.7, which is anyway something planned to be done. Help welcome :-)
--
You received this bug notification because you are a member of Desktop
Packages,
I found this to be caused by ModemManager using the PPP port for both
control and PPP; instead of the PCUI port for control and the PPP port
for PPP. This issue should be fixed in the MM_06 branch of ModemManager
already, as well as in git master. If anyone can try with MM_06 branch
to confirm it,
There is work in progress already to use the cdc-wdm0 interface for QMI
with libqmi in ModemManager.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/977761
Title:
Connection
Still quite some things to do before being able to use QMI in
ModemManager, including finishing to port all pending MM plugins to the
new codebase, and updating NetworkManager to talk to the new redesigned
interface... Current MM git master is not yet able to talk to NM git
master.
Help really
Sleepy John: syslog log is pretty useless if ModemManager wasn't run
with --debug, :-/ And regarding the priority, I really don't give a s***
about it :-) I personally do this in my free time, so at least for me,
it doesn't matter if it was low or super-critical, I'll try to help if I
have time.
I'll follow up the issue in GB#662113
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/868034
Title:
Huawei E220 can't connect on Ubuntu 11.10
Status in ModemManager (with
Great, so anyone requiring to use MM with the Huawei modem can fallback
to 0.4 until the proper fix arrives in a 0.5 update.
Mark: step 4 not really needed; just killall modem-manager should do
it after installing the new .deb; and even that may not be needed
depending on the post install
Upstream devs know about the issue, and I was supposed to try to
reproduce this with my Huawei 220. I just don't have time to test it
myself whenever I remember that I have to test it. Can someone provide
modem-manager debug logs with the previous version, the one that worked?
--
You received
Mark: Thanks for the logs
I can find two main differences in the MM 0.4 (the one which worked) and
MM 0.5 (the one which failed) log.
1) In the MM 0.5 log, the secondary ttyUSB1 gets probed and grabbed as
secondary port; while in the MM 0.4 log capability probing in that port
is not even
54 matches
Mail list logo
