Please report this for the network-manager debian package, the snappy-
hwe-snaps is only for the network-manager snap package.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snappy-hwe-snaps
Status: New => Invalid
--
You received
Public bug reported:
There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4:
@slyon thanks, I have manually tested and seems to work. I've created
https://github.com/snapcore/network-manager-snap/pull/15, let's see how
tests go.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
To reproduce the problem, this should be enough:
1. Create a connection to an OpenVPN server
2. Start the connection. The OpenVPN plugin will create a tunnel interface.
3. "nmcli c" should show a tunX connection and the VPN connection. "nmcli d"
should show tunX as a external connection.
4.
> So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?
Hm, not sure if we mean the same. That two connections (tun2 and
) appear after connecting to the VPN is expected. NM
recognizes tun2 as "external"
Changing the check as suggested to:
if (!is_volatile && !is_nm_generated && !is_external) {
...
does help and netplan files for tun0 and tun1 are not written anymore.
But, when I create a VPN connection I still have problems.
$ network-manager.nmcli c import type openvpn file
$
Unfortunately this is still happening with the patch from comment #3. In
fact I do not even need to create a VPN connection for this. If I
install easy-openvpn-server:
$ snap install easy-openvpn-server
it creates two tun devices (tun0 and tun1) that can be seen with "ip
address" command. That
It turns out that this actually regressed some qualcomm modems because
modem-manager started to use some special netlink sockets that were not
enabled in the 5.4 kernel.
To have that we need (see LP: #1998194):
CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m
in the 5.4
Right, it is more about the plugin, was not fully sure where to put
this, but now probably we can put under network-manager deb.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
[Impact]
* This is a request to backport changes in kinetic plymouth package
to 0.9.5+git20211018-1ubuntu4 to jammy. That version contains a new
plugin named label-ft, which was introduced to replace the label
plugin in Ubuntu Core systems. The difference with the
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1973835
Title:
Ubuntu
Public bug reported:
The plymouth label pulls in too many dependencies (libpango, libcairo, X
libs, etc.). This is an issue for integration in the initramfs.
There is an alternative plugin (label-ft) that has been proposed upstream:
On Wed, Sep 29, 2021 at 1:35 PM Mattia Rizzolo
<1943...@bugs.launchpad.net> wrote:
>
> As a member of the Debian LibreOffice Team, and also as an Ubuntu
> Developer, I'm likewise not convinced that starting to build and ship
> graphite2's static library is a really useful thing to do.
>
> I'm
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
** Bug watch added: Debian Bug tracker #994757
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to graphite2 in
Debian bug report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=994752
** Bug watch added: Debian Bug tracker #994752
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
There is no libgraphite2.a file, so it is not possible to compile
statically against this library. See attached patch to solve this.
** Affects: graphite2 (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "debdiff.patch"
Public bug reported:
The development package for pango (libpango1.0-dev) does not include
static libraries so it is not possible to link these libraries
statically.
See attached patch with the fix.
** Affects: pango1.0 (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
Just FTR, note that the change in NM upstream was needed so the network-
manager snap was able to correctly detect if udevd is running. We
currently build the snap from the source package + some patches
including this one. But, the long term target is to be able to create
the snap by simply
There is here a change in behavior in lxc/lxd. Running
https://paste.ubuntu.com/p/vz7SXcX3K9/:
On hirsute lxd container:
root@hirsute:~# ./test
access errno 13
path is read only: 0
root@hirsute:~# mount | grep 'sysfs on /sys '
sysfs on /sys type sysfs (rw,relatime)
On focal lxd container:
This is, I think, a glibc bug. See
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and
This is, I think, a glibc bug. See LP:#1914044
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
This is, I think, a glib bug. See LP:#1846837.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
It looks like the VPN related SRU that was previous to this one was
reverted. Could we land this into bionic?
--
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/1781597
Title:
Public bug reported:
It has been detected that pppd crashes when running confined inside the
NM 1.10 snap. This happens because it cannot open/create a file in
called /var/run/pppd2.tdb, which triggers a bug later.
This is the backtrace:
#0 0x5581bd1031e9 in tdb_close (tdb=0x0) at
I would very much like the SRU to happen.
--
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/1781597
Title:
[SRU] WoWLAN settings are not supported
Status in network-manager
Changed now, thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
You received this bug notification because you are a member of Desktop
Pa
@sil2100, where can I take a look at those?
--
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/1781597
Title:
[SRU] WoWLAN settings are not supported
Status in network-manager
Verified on cosmic, using network-manager 1.12.4-1ubuntu1.2:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename: cosmic
$ apt policy network-manager
network-manager:
Installed: 1.12.4-1ubuntu1.2
Candidate:
** Merge proposal unlinked:
https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119
--
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/1780606
Title:
** Summary changed:
- WoWLAN settings are not supported
+ [SRU] WoWLAN settings are not supported
--
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/1781597
Title:
[SRU] WoWLAN
Public bug reported:
[Impact]
WoWLAN lets us wake up the system by sending wake packages over the wifi
connection. This is something requested by some OEM projects, for bionic
server images.
NM 1.12 supports configuring this feature, so this can be achieved by
backporting that support to 1.10
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1725190
Title:
Please update modemmanager in xenial
I have tried the packages in xenial-proposed for two modems:
Sierra HL8548
ZTE MF626
I was able to connect and everything seemed to be working as expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
** Description changed:
- Since linux-4.4.0-98, the kernel additionally load gcserial driver for
+ [Impact]
+
+ * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
+ and were using a ttyUSB* port for data connections instead of the MBIM
+ device (which provides better
@Lukasz please go for sponsoring the zesty->xenial backport, that is
enough to get support for the original modem OEM enablement needed. The
work in the patches needs some time, so better do this for the moment.
Thanks!
--
You received this bug notification because you are a member of Desktop
@Lukasz those are patches for Dell modems (plano project, unbuntu core).
It makes sense to upstream some of them in fact, and that is something I
can try.
But, it would still make sense to backport the zesty packages to xenial,
as that has the support needed for DW5816e (lp #1693756). If you
@Lukasz, I uploaded the backported packages (zesty->xenial) + patches
from the snap in:
https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/modem-
manager-backport
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in
@Lukasz yes, I think that using the version in zesty is perfectly
feasible, I can prepare the packages for that. About using the backports
pocket, I will let YC or Alex comment on that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Packages uploaded to https://launchpad.net/~snappy-hwe-
team/+archive/ubuntu/stacks-overlay and built for xenial. The versions
are the same as for artful, plus additional patches for Dell modems in
the modem-manager source package.
--
You received this bug notification because you are a member
** Description changed:
We would like to upgrade xenial to 1.6 series so it supports the same
- modems as the modem-manager snap, specifically some new Sierra modems.
- These are the packages that would need to be updated:
+ modems as the modem-manager snap, specifically some new Sierra modems
After chatting with sil2100, he said that potentially we could backport
artful 1.6.8 modemmanager to xenial, which would be great. I have
created bug #1725190 to track that and start in a clean state from
there.
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
We would like to upgrade xenial to 1.6 series so it supports the same
modems as the modem-manager snap, specifically some new Sierra modems.
These are the packages that would need to be updated:
libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
libqmi: 1.12.6-1 in xenial,
@jibel, thanks for the log. It looks like wpa_supplicant removes the
previous connection due to a timeout before you connect to another
Freewifi hotspot, which probably helps to rule out issues. Also, a new
DHCP lease is requested after reconnecting in all cases, and it gives
you back always the
Branch with fix/workaround:
https://code.launchpad.net/~alfonsosanchezbeato/+git/network-
manager/+ref/lp1478319-cannot-roam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Bug LP: #1637100 reported for indicator-network, to create unique
default SSIDs per device.
--
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/1478319
Title:
Wifi doesn't
@faenil, by the WiFi standards, APs with the same SSID and same
authentication method *are the same network*.
Is is unfortunate that some devices models use the same SSID instead of
customizing the name per device. Interestingly, NM uses a hard-coded
list to identify these networks and avoid
@jibel, @julia I have a workaround for this in
https://bileto.ubuntu.com/#/ticket/2098 . Could you please give this a
try?
My suspicion here is that when this happens the two APs have different
DHCP servers. The workaround forces a DHCP lease renewal when roaming
between APs. However, even if
Reproduced on bq 4.5, OTA13. I created two APs with SSID "Ubuntu", same
password, same authentication. I connected to one of them:
phablet@ubuntu-phablet:~$ nmcli d wifi
* SSIDMODE CHAN RATE SIGNAL BARS SECURITY
Ubuntu Infra 1
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
** Changed in: network-manager (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
ess
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Branch linked: lp:~phablet-team/unity8/sms-notif-lp1544477
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
** Also affects: telephony-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: telephony-service (Ubuntu)
Status: New => Confirmed
** Changed in: media-hub (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: unity8 (Ubuntu)
Status: Incomplete =>
@GTriderXC, the easiest thing would be to enable developer mode and grab
the crash file from a PC:
adb pull /var/crash/
then you can upload to the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Note on comment #101: I have checked that the issue happens for both
OTA12 and rc-proposed/bq-aquaris.en image #412, for BQ Aquaris 4.5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
I was able to reproduce this finally. It is a matter of killing media-
hub-server:
pkill -9 media-hub
(this has the same effect as a media-hub-server crash).
media-hub-server re-starts, but it looks like not all the system
recovers and re-connects to dbus-interface. Voice calls ringing,
@mpredotka thanks for the logs, will be useful.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477
Title:
No sound notification for new SMS (Ubuntu Touch)
Status in Canonical
I have been trying to reproduce the bug in most of the devices in
different ways (screenshot, sms, telegram), but no luck.
@all, is there anybody still experiencing this in OTA-12? If that is the
case, and you can reproduce easily, please do in your phone:
rm ~/.cache/upstart/*
sudo sh -c '>
@Pat, @Jim, I have sent an e-mail about this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1544477
Title:
No sound notification for new SMS (Ubuntu Touch)
Status in Canonical
Hmm, it looks like the screenshot issue is happening because file
"/system/media/audio/ui/camera_click.ogg"
does not exist. So it is a different bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
I have tested the screenshot case in turbo, where I heard no sound, and
in frieza, where sound is working (see attached logs). In turbo I saw in
unity8.log:
[2016-08-16:15:21:08.524] [PERFORMANCE]: Last frame took 32 ms to render.
[2016-08-16:15:21:09.087] virtual void
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574729
Title:
Audio/Video not in sync on M10/frieza
Device tarballs for testing the fix:
http://people.canonical.com/~abeato/lp1574729/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574729
Title:
Audio/Video not in sync on
Interesting finding (thanks @Jim for the suggestion): I changed the
output device to headphones using the jack, same issue. Then I switched
to bluetooth headphones, using A2DP profile, and video and audio came
into sync. However, that only lasted a couple of minutes, after that
suddenly I got the
@gubu, thanks for the link to the sync video, it is great to see the
delay between audio and video. To rule out gstreamer of the equation, I
have tried to transcode the video by doing:
gst-launch-1.0 filesrc location=Videos/sync-test.mp4 ! decodebin
name=demux demux. ! queue ! audioconvert !
@eviweb, would be interesting to have:
/var/log/syslog
/home/phablet/.cache/upstart/*
and output of following commands (execute them while the problem is
happening):
/usr/share/ofono/scripts/list-modems
/usr/share/ofono/scripts/list-contexts
nmcli c
nmcli d
--
You received this bug
I have just confirmed this still happens with 1.1.93-0ubuntu1~vivid3
** Description changed:
After moving in an out of my own "faraday cage" an ubuntu phone, NM got
into an state where *both* WiFi and cellular data were disconnected and
NM was not able to recover.
+
+ *
@pat-mcgowan, not exactly the same bug that was reported, as you do not
have active contexts. But still possibly a NM bug if you saw a cellular
data icon when dropping down the indicator line (if you have the icon
there but not in the top of the screen it means the modem is data
attached but there
** Changed in: ofono (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Changed in: avila
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1535689
Title:
Avila tablet is not recognised by libmtp
Status in The
Taking a look at output of ofono scripts it seems all is good on that
side: the modem is attached but the context has not been activated by
NM.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Branch linked: lp:~phablet-team/ofono/lp1545005
--
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/1533508
Title:
Mobile data doesn't automatically connect after leaving wifi
Also, doing
kill -9 `pgrep NetworkManager`
alse leaves in a bad state the modem device:
root@ubuntu-phablet:/home/phablet# nmcli d
DEVICE TYPE STATE CONNECTION
wlan0wifi connected WLAN_1609
ril_0gsm
Fix for this in:
https://github.com/rilmodem/ofono/pull/238
Note: it is possible to still having some issues with connections. see
bug #1565717 .
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
NOTE: On the cellular side, it seems like NM gets stuck into an
intermediate state (connecting (prepare)). I was able to reproduce
something very similar deterministically by doing:
stop network-manager
/usr/share/ofono/scripts/activate-context /ril_0 1
start network-manager
It seems that NM
Public bug reported:
After moving in an out of my own "faraday cage" an ubuntu phone, NM got
into an state where *both* WiFi and cellular data were disconnected and
NM was not able to recover.
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => Alfonso Sanchez-Beato
(alfonsosanchezbeato)
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Changed in: canonical-devices-system
** Changed in: ofono (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This is how the bug is apparently produced:
1. NM asks ofono to activate a context
2. Network is gone just a moment after that and modem detaches
3. Attached property is set to FALSE by ofono, then it tries to deactivate
activated contexts, but there are none (no response yet from the request
Finally I was able to reproduce this issue with traces. syslog attached.
** Attachment added: "syslog.bug"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+attachment/4617000/+files/syslog.bug
--
You received this bug notification because you are a member of Desktop
If anybody else is able to reproduce this, it would be great to have the
output of
/usr/share/ofono/scripts/list-contexts
additionally to list-modems and nmcli output.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
If anybody is able to reproduce this and does not mind making the system
image writable, please try downloading and installing
http://people.canonical.com/~abeato/debug/ofono_1.17-debug-
attachment.deb
AND modify /etc/init/ofono.override changing line
exec ofonod -P
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => Alfonso Sanchez-Beato
(alfonsosanchezbeato)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
ht
In all cases list-modems show something similar to:
[ org.ofono.ConnectionManager ]
RoamingAllowed = 0
Powered = 1
Bearer = hspa
Attached = 0
The modem is not attached, so no connection is possible. But, we are
able to detect a bearer, which is suspicious. It
** Changed in: nuntium (Ubuntu)
Status: Confirmed => Fix Released
--
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/1370376
Title:
Can't receive MMS despite ability to
@Tomas, thanks for your testing. I think you are seeing bug #1480815 .
Could you please add a comment there?
--
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/1370376
Title:
@Tomas, sending from one card to the other one in the Aquaris will not
work, because we need data enabled for MMS to work and only one slot can
have data at a time. So either you won't send or you won't receive.
Could you please attach/send me privately /var/log/syslog and
~/.cache/upstart/*
@Tomas, are you still unable to receive MMS for Tele2 after OTA-6?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
@Tomas, I have also performed a quick test sending to my own number and
the MMS is sent and received by nuntium, but messaging app only shows it
as sent. Don't know if this is intended or not, but anyway try to send
the MMS from another phone to get feedback from messaging app and know
for sure if
** Changed in: nuntium (Ubuntu)
Status: In Progress = Fix Released
** Changed in: nuntium (Ubuntu RTM)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
03mmsproxy sets up routes for MMS. It is undocumented and possibly racy.
It would be better if NetworkManager's ofono plugin did the job.
** Affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Affects: network-manager (Ubuntu)
Changes in ofono mean basically exposing the ipv6 settings returned by
rild in ofono's DBus interface. The only issue that is trickier is the
handling of MMS contexts, as ofono does establish addresses and routes
in that case (which is not true for internet contexts).
--
You received this bug
@Will, @Tony:
The behaviour you see is probably related to indicator-network, so if
you open a bug please include that package too. I think the behaviour
has improved after latest landings for that package which fixed some
problems for PUK-blocked SIMs, although issues still remain.
I do not
Probably the same as bug #1459995
--
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/1370376
Title:
Can't receive MMS despite ability to send on Tele2
Status in network-manager
** Changed in: nuntium (Ubuntu)
Status: In Progress = Fix Released
--
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/1361864
Title:
add Preferred property to
** Changed in: network-manager (Ubuntu)
Status: In Progress = Fix Released
--
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/1454625
Title:
Cannot send MMS messages with
Changes for nuntium in
https://github.com/ubuntu-phonedations/nuntium/pull/18
** Changed in: nuntium (Ubuntu)
Assignee: (unassigned) = Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Changed in: nuntium (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
--
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/1454625
Title:
Cannot send MMS messages with
The regression is due to NM setting DEVICE_IFACE to ril_0 in version
0.9.10.0 instead of /ril_0 as in 0.9.8.8.
There has been a change in nm-modem-ofono.c:nm_modem_ofono_new that
explains this (MODEM_UID is skipping the slash in the latest version).
The patch that creates nm_modem_ofono_new is
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
- enabled, for some operators. Combined contexts are able to handle
+ connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$
1 - 100 of 145 matches
Mail list logo
