[Desktop-packages] [Bug 2015887] Re: VPN private key is visible
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 this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2015887 Title: VPN private key is visible Status in snappy-hwe-snaps: Invalid Status in network-manager package in Ubuntu: New Bug description: When importing a configuration from .ovpn file, I select "Store the password only for this user" for Private key in Network Manager's GUI. It then works as expected, great job! What I did not expect though, is possibility of seeing the Private key at any time afterwards (actually, the same issue applies to Password in Wi-Fi Security settings). The problem is, that this key is confidential and may only be used by our sysadmin at work, and I'm not allowed to know it, but still, I need to be able to connect to remote desktop in his absence, so the key should be stored somewhere in an encrypted format. I'd appreciate an option, that allows to hide this key from end-user - a way to disable Show password check-boxes and buttons for Private key after VPN was added, otherwise I cannot use remote desktop feature on Ubuntu at my current work. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-hwe-snaps/+bug/2015887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012902] [NEW] netplan plugin: generated NM config when using globbing will be used for only one connection
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: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2012902 Title: netplan plugin: generated NM config when using globbing will be used for only one connection Status in network-manager package in Ubuntu: New Bug description: 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: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
@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. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Invalid Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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. Disconnect the VPN connection (nmcli c down ) 5. A file in /etc/netplan/ for the tunX which should not be there is created -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
> 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" as it is an auxiliary device/connection created by the OpenVPN plugin. The problem that is happening is that that connection is being stored in /etc/netplan/, which should not be the case. Note that tun0 and tun1 are slightly different as those are created by the OpenVPN server also running on the device. The netplan files for them are not written anymore after changing the patch. > Does running 'nmcli connection reload' after the connection profile for the VPN connection (tun2?) got written, make it show up in the NM daemon? No, that does not happen. But it happens if I reboot the system. I think that is because there is some file in /run that prevents this from happening if just reloading things. Before rebooting: $ sudo ls run/NetworkManager/system-connections/ -l total 20 lrwxrwxrwx 1 root root9 Jan 10 11:22 891164a5-1fed-42b8-8f6e-903db6396d5e.nmmeta -> /dev/null -rw--- 1 root root 403 Jan 10 11:24 netplan-NM-891164a5-1fed-42b8-8f6e-903db6396d5e.nmconnection -rw--- 1 root root 1248 Jan 10 11:24 netplan-NM-af486148-2495-48a9-9704-2a1230e97e32.nmconnection -rw--- 1 root root 131 Jan 10 11:24 netplan-ens3.nmconnection -rw--- 1 root root 336 Jan 10 09:37 tun0.nmconnection -rw--- 1 root root 336 Jan 10 09:37 tun1.nmconnection After rebooting: $ sudo ls run/NetworkManager/system-connections/ -l total 20 -rw--- 1 root root 403 Jan 10 11:28 netplan-NM-891164a5-1fed-42b8-8f6e-903db6396d5e.nmconnection -rw--- 1 root root 1248 Jan 10 11:28 netplan-NM-af486148-2495-48a9-9704-2a1230e97e32.nmconnection -rw--- 1 root root 131 Jan 10 11:28 netplan-ens3.nmconnection -rw--- 1 root root 336 Jan 10 11:28 tun0.nmconnection -rw--- 1 root root 336 Jan 10 11:28 tun1.nmconnection 891164a5 was tun2 and af486148 the VPN connection. -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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
$ network-manager.nmcli c up
$ network-manager.nmcli c
NAME UUID TYPE DEVICE
7b7fd99d-2651-4796-ba50-beda0890aab9 vpn ens3
tun0 1d7b454c-4897-4d3d-899a-619165a996bf tun tun0
tun1 f7b9ba1f-496b-4cca-ae79-31db28a64c29 tun tun1
tun2 46935370-3662-4aac-b563-877214b48cd8 tun tun2
netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3
$ sudo /snap/bin/network-manager.nmcli d
DEVICE TYPE STATE CONNECTION
tun0tun connected (externally) tun0
tun1tun connected (externally) tun1
tun2tun connected (externally) tun2
ens3ethernet connected netplan-ens3
lo loopback unmanaged --
$ network-manager.nmcli c down default
$ network-manager.nmcli c
NAME UUID TYPE DEVICE
netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3
tun0 8bc8d5b1-6000-4b78-9988-72d2d811bfb7 tun tun0
tun1 9d614be8-dac1-44ef-acfd-f9c60005b56f tun tun1
default 7b7fd99d-2651-4796-ba50-beda0890aab9 vpn --
$ ls /etc/netplan/
00-default-nm-renderer.yaml
50-cloud-init.yaml
90-NM-7b7fd99d-2651-4796-ba50-beda0890aab9.yaml
90-NM-46935370-3662-4aac-b563-877214b48cd8
Note that when you create an OpenVPN connection both a normal NM
connection and a new tunnel device (tun2) are created. NM creates a
external device for tun2. The interesting thing here is that the file
for tun2 is written after setting down the connection, and the NM daemon
actually forgets it (until you restart it and reads the netplan file).
Maybe this storing is in a different code path.
--
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/1998207
Title:
netplan network-manager plugin tries to save temporary connections
Status in netplan:
Triaged
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When creating an OpenVPN connection, a temporal connection called tunN
is created. For instance, after activating a connection called
vpntest, I have:
NAME UUID TYPE DEVICE
vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3
tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0
tun0 is created/removed after activating/deactivating vpntest and
should not really be saved, but I see netplan adding it in
/etc/netplan. And while doing so the plugin also reports some errors
(I see these when stopping the connection):
Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG:
the profile cannot be stored in keyfile format without becoming unusable:
cannot access file: No such file or directory
Nov 28 16:16:57 ubuntu NetworkManager[11752]:
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920]
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null))
to
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
keyfile writer produces an invalid connection: cannot access file: No such
file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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 makes NM create the corresponding devices and connections: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 edc2d2e1-b126-475d-8d5b-1a5b3bfd43d3 tun tun0 tun1 2945f4f4-2d44-4a61-83b4-cee73fd81129 tun tun1 /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli d DEVICE TYPE STATE CONNECTION ens3ethernet connected netplan-ens3 tun0tun connected (externally) tun0 tun1tun connected (externally) tun1 lo loopback unmanaged but unfortunately these connections are still written as static connections in /etc/netplan/. And when I reboot, I see 4 of them: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 864e0de2-e5c6-4c9b-aa7f-20aef970067c tun tun0 tun1 ddfc7db2-2baa-488f-95da-c8e1e66e458b tun tun1 default be2bc22c-fc98-4b2b-9484-fd4d5c838d5f vpn -- tun0 3c1e12f9-1a08-4a6f-aef3-5ea22d9e9bb2 tun -- tun1 eb8ed73b-3312-401f-a4c4-c26aadb3a014 tun -- The files look like https://paste.ubuntu.com/p/KvTVXPwK75/ -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe
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 kernel. However, this might not be easy according to some discussion I had. Would it be possible to revisit this backport? -- 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/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: New Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981432] [NEW] [SRU] Backport label-ft plugin to 22.04
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 label plugin is that it pulls much less dependencies (LP: #1976352), which allows a much smaller initramfs. This change should not affect classic systems. [Test Plan] * The test plan consists on creating a UC image using this package and make sure that label.so and cairo/pango dependencies are not pulled, while we still have a splash screen. * For classic, the test plan is to refresh plymouth and make sure that it still uses label.so and its dependencies, and still the splash works. [Where problems could occur] * The change introduces a new package named plymouth-label-ft with the label-ft.so plugin. This package will not be installed on classic by default, and it is the main change proposed. The rest of the plymouth code changes use label-ft.so as a fallback if label.so is not present. This is just a few lines of code, and still uses label.so by default, so the potential risk of breaking the splash should be small. If something goes wrong, we could be without splash and without a user friendly way of unlocking disks if using FDE. [Other Info] * Change should be relevant for UC only ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Description changed: [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 label plugin -is that it pulls much less dependencies (LP: #1976352), which allows -a much smaller initramfs. This change should not affect classic systems. + * 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 label plugin + is that it pulls much less dependencies (LP: #1976352), which allows + a much smaller initramfs. This change should not affect classic systems. [Test Plan] - * The test plan consists on creating a UC image using this package and make -sure that label.so and cairo/pango dependencies are not pulled, while we -still have a splash screen. + * The test plan consists on creating a UC image using this package and + make sure that label.so and cairo/pango dependencies are not pulled, + while we still have a splash screen. - * For classic, the test plan is to refresh plymouth and make sure that -it still uses label.so and its dependencies, and still the splash works. + * For classic, the test plan is to refresh plymouth and make sure that + it still uses label.so and its dependencies, and still the splash +works. [Where problems could occur] - * The change introduces a new package named plymouth-label-ft with the label-ft.so -plugin. This package will not be installed on classic by default, and it is -the main change proposed. The rest of the plymouth code changes use label-ft.so -as a fallback if label.so is not present. This is just a few lines of code, -and still uses label.so by default, so the potential risk of breaking the splash -should be small. If something goes wrong, we could be without splash and without -a user friendly way of unlocking disks if using FDE. + * The change introduces a new package named plymouth-label-ft with the + label-ft.so plugin. This package will not be installed on classic by + default, and it is the main change proposed. The rest of the plymouth + code changes use label-ft.so as a fallback if label.so is not present. + This is just a few lines of code, and still uses label.so by default, so + the potential risk of breaking the splash should be small. If something + goes wrong, we could be without splash and without a user friendly way + of unlocking disks if using FDE. [Other Info] - - * Change should be relevant for UC only + + * Change should be relevant for UC only -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1981432 Title: [SRU] Backport label-ft plugin to 22.04 Status in plymouth package in Ubuntu: New Bug description: [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 label plugin is that it pulls much less
[Desktop-packages] [Bug 1973835] Re: Ubuntu 22.04, Bluetooth issues
** 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 22.04, Bluetooth issues Status in bluez package in Ubuntu: New Bug description: 0 I installed Ubuntu 22.04 and the Bluetooth was working fine. I turned off the bluetooth and could not turn it back on. I did some research and found some calls to turn it back on: sudo rfkill unblock all sudo hciconfig hci0 down sudo rmmod btusb sudo modprobe btusb sudo hciconfig hci0 up Now, I can turn it on and off as I please but It is now not connecting to any device. It would connect for a brief second and then disconnect. Can't find anything from research. Anyone can help with this ? Also, Whenever I boot up windows, the bluetooth works perfectly fine on windows. So it's not an hardware issue. I ran the command: bluetoothctl and the bluetooth is cycling through connecting to the device and disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976352] [NEW] The plymouth label pulls in too many dependencies
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: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/91 I have attached a debdiff that integrates that plugin in our packaging. As it is a separate plugin, core parts of plymouth are only slightly changed. The package built for kinetic can be found here too: https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/build2 ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Patch added: "label-ft.debdiff" https://bugs.launchpad.net/bugs/1976352/+attachment/5594049/+files/label-ft.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1976352 Title: The plymouth label pulls in too many dependencies Status in plymouth package in Ubuntu: New Bug description: 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: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/91 I have attached a debdiff that integrates that plugin in our packaging. As it is a separate plugin, core parts of plymouth are only slightly changed. The package built for kinetic can be found here too: https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1976352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
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 personally generically against static libraries, since I regularly see > grief caused by poor tracking of statically-builtand or embedded things. Well, I have seen grief caused by shared libraries pulling too many dependencies or by shared libraries updates that break applications even though in theory the ABI compatibility has been kept. Also, there is actually a trend towards static compilation (golang, rust), so I do not think I'm the only one seeing this. But that is not really relevant. There are valid uses of static libraries, and the developers should have the option to choose between shared and static. The patch does not prevent using shared libraries, it just gives more options to application developers. > > And I don't really buy the need to save space when talking about a 137328 > bytes shared lib (taken from the last build of graphite2 in Sid, that's the > size of the .so). > It feels like you are building some kind to system image that you'd then > flash into some embedded thingy. I don't think there is much value in > saving...what, a dozen kB perhaps? (I haven't tried building the .a, so > happy to get the number). If your system is so constrained in space you're > likely going to need some much more dedicated work to reduce the size of > all components anyway; similarly if you are after the (normally > uncountable) performance improvement of statically linked binaries. Nobody said this was about saving space. libgraphite was being pulled as many other dependencies and I wanted to have all statically compiled instead of some static, some dynamic. Said this, I agree in not carrying a delta between Debian and Ubuntu as this library does not pull additional dependencies and is small, so additional maintenance is not worth the effort. > > On Wed, 29 Sep 2021, 1:06 pm Sebastien Bacher, <1943...@bugs.launchpad.net> > wrote: > > > Debian wontfixed the change so it means we will need to carry a delta at > > the cost of increased workload from our team if we take the change. Not > > saying that we should be we need to weight the cost over time and the > > benefit > > > > -- > > You received this bug notification because you are subscribed to Ubuntu. > > https://bugs.launchpad.net/bugs/1943984 > > > > Title: > > No archive files for static compilation are included in the -dev > > package > > > > Status in graphite2 package in Ubuntu: > > New > > Status in graphite2 package in Debian: > > Won't Fix > > > > Bug description: > > There is no libgraphite2.a file, so it is not possible to compile > > statically against this library. See attached patch to solve this. > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > > > > > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1943984 > > Title: > No archive files for static compilation are included in the -dev > package > > Status in graphite2 package in Ubuntu: > New > Status in graphite2 package in Debian: > Won't Fix > > Bug description: > There is no libgraphite2.a file, so it is not possible to compile > statically against this library. See attached patch to solve this. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Won't Fix Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
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 Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943859] Re: The development package does not include static libraries
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 pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943984] [NEW] No archive files for static compilation are included in the -dev package
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" https://bugs.launchpad.net/bugs/1943984/+attachment/5525961/+files/debdiff.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943859] [NEW] The development package does not include static libraries
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: "debdiff.patch" https://bugs.launchpad.net/bugs/1943859/+attachment/5525735/+files/debdiff.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
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 staging the network-manager debs. So, please keep this in mind and try to put back this change as soon as is feasible again, so we do not need to remove the change in the deb and then put it back in the snap. -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
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: root@focal:~# ./test path is read only: 1 root@focal:~# mount | grep 'sysfs on /sys ' sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime) (no idea why there are two mounts in focal) According to https://systemd.io/CONTAINER_INTERFACE/ , /sys should be mounted read-only? -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
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 totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
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 broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
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 broken on aarch64 Status in GStreamer: Unknown Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04
** 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. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: New Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
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: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets 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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831914] [NEW] pppd crashes when running from the NM 1.10 snap
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 tdb.c:1872 #1 0x5581bd0d8e81 in safe_fork (infd=10, outfd=10, errfd=10) at main.c:1571 #2 0x5581bd0d9393 in run_program (prog=prog@entry=0x5581bd3692a0 "/etc/ppp/ip-up", args=args@entry=0x7ffca0b31bf0, must_exist=must_exist@entry=0, done=done@entry=0x5581bd0e1d10 , arg=arg@entry=0x0, wait=wait@entry=0) at main.c:1798 #3 0x5581bd0dfa4b in ipcp_script (script=0x5581bd3692a0 "/etc/ppp/ip-up", wait=0) at ipcp.c:2140 #4 0x5581bd0daa38 in fsm_rtermack (f=) at fsm.c:658 #5 0x5581bd0daa38 in fsm_input (f=0x5581bd368dc0 , inpacket=0x5581bd327464 "\002\024", l=) at fsm.c:393 #6 0x5581bd0d7563 in get_input () at main.c:1085 #7 0x5581bd0d7563 in main (argc=, argv=) at main.c:537 Proposed fix upstream: https://github.com/paulusmack/ppp/pull/122 ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1831914 Title: pppd crashes when running from the NM 1.10 snap Status in ppp package in Ubuntu: New Bug description: 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 tdb.c:1872 #1 0x5581bd0d8e81 in safe_fork (infd=10, outfd=10, errfd=10) at main.c:1571 #2 0x5581bd0d9393 in run_program (prog=prog@entry=0x5581bd3692a0 "/etc/ppp/ip-up", args=args@entry=0x7ffca0b31bf0, must_exist=must_exist@entry=0, done=done@entry=0x5581bd0e1d10 , arg=arg@entry=0x0, wait=wait@entry=0) at main.c:1798 #3 0x5581bd0dfa4b in ipcp_script (script=0x5581bd3692a0 "/etc/ppp/ip-up", wait=0) at ipcp.c:2140 #4 0x5581bd0daa38 in fsm_rtermack (f=) at fsm.c:658 #5 0x5581bd0daa38 in fsm_input (f=0x5581bd368dc0 , inpacket=0x5581bd327464 "\002\024", l=) at fsm.c:393 #6 0x5581bd0d7563 in get_input () at main.c:1085 #7 0x5581bd0d7563 in main (argc=, argv=) at main.c:537 Proposed fix upstream: https://github.com/paulusmack/ppp/pull/122 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1831914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
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 package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets 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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812507] Re: Typo in description of snap
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 Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1812507 Title: Typo in description of snap Status in network-manager package in Ubuntu: Fix Released Bug description: https://snapcraft.io/network-manager lists the description for NetworkManager as “Network management based on NeworkManager” (sic). NeworkManager should be NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
@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 package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Committed Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets 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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
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: 1.12.4-1ubuntu1.2 Version table: *** 1.12.4-1ubuntu1.2 500 500 http://es.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.12.4-1ubuntu1.1 500 500 http://es.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 1.12.4-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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 package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Committed Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets 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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server
** 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: NetworkManager not able to manage WWAN devices in 18.04 server Status in network-manager package in Ubuntu: Triaged Bug description: 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 problem is that the filter should apply to "gsm" or "cdma" types, not "wwan". E.g.: [keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Before the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu eth0 ethernet unmanaged -- cdc-wdm0 gsm unmanaged -- loloopback unmanaged -- After the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu cdc-wdm0 gsm connected cell eth0 ethernet unmanaged -- loloopback unmanaged -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
** 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 settings are not supported Status in network-manager package in Ubuntu: New Bug description: [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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] [NEW] WoWLAN settings are not supported
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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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: WoWLAN settings are not supported Status in network-manager package in Ubuntu: New Bug description: [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 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** 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 to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Xenial: Fix Committed Status in libqmi source package in Xenial: Fix Committed Status in modemmanager source package in Xenial: Fix Committed Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from -proposed libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
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. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Xenial: Fix Committed Status in libqmi source package in Xenial: Fix Committed Status in modemmanager source package in Xenial: Fix Committed Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from -proposed libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819
** 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 performance). + + Since linux-4.4.0-98, the kernel additionally loads gcserial driver for Dell Wireless DW5818/5819. The reason behind it is to support firmware - switching and upgrading. However, the change makes ModemManager to use - Gobi plugin for this two modules. With Gobi plugin, the modules could + switching and upgrading. However, the change makes ModemManager use Gobi + plugin for this two modules. With Gobi plugin, the modules could establish data links, but it failed to retrieve the signal state. And it caused the mmcli and nm-applet giving wrong signal strength. The modules support the MBIM protocol, so ModemManager should use Dell plugin for these two modules. I have worked out a patch to forbid these two modules in Gobi plugin, and it does work well. + + [Test Case] + + Current MM: + * Create connection with + $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn + * Without the patched package, mmcli shows, with an active connection (see comment #2): + primary port: 'ttyUSB2' + signal quality: '0' (recent) + + Patched MM: + * Create connection with + $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn + * With the patched package, mmcli shows, with an active connection (see comment #7): + primary port: 'cdc-wdm0' + signal quality: '38' (cached) + + [Regression Potential] + + The patch simply adds the Sierra modems VID/PIDs to the list of + forbidden ids in the Gobi plugin, so the possibility of a regression is + very small: only products with said VID/PID will be affected. -- 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/1735134 Title: ModemManager uses a wrong plugin for Dell DW5818/5819 Status in modemmanager package in Ubuntu: New Bug description: [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 performance). Since linux-4.4.0-98, the kernel additionally loads gcserial driver for Dell Wireless DW5818/5819. The reason behind it is to support firmware switching and upgrading. However, the change makes ModemManager use Gobi plugin for this two modules. With Gobi plugin, the modules could establish data links, but it failed to retrieve the signal state. And it caused the mmcli and nm-applet giving wrong signal strength. The modules support the MBIM protocol, so ModemManager should use Dell plugin for these two modules. I have worked out a patch to forbid these two modules in Gobi plugin, and it does work well. [Test Case] Current MM: * Create connection with $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn * Without the patched package, mmcli shows, with an active connection (see comment #2): primary port: 'ttyUSB2' signal quality: '0' (recent) Patched MM: * Create connection with $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn * With the patched package, mmcli shows, with an active connection (see comment #7): primary port: 'cdc-wdm0' signal quality: '38' (cached) [Regression Potential] The patch simply adds the Sierra modems VID/PIDs to the list of forbidden ids in the Gobi plugin, so the possibility of a regression is very small: only products with said VID/PID will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@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 Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@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 prefer, we can go that way and leave out the patches for the moment until I get a response for MM upstream. -- 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/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@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 Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
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 of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** 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 + (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. -- 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/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: 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 (HL8548 and others from HL series, popular in IoT devices). 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
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, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in modemmanager package in Ubuntu: Confirmed Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] [NEW] Please update modemmanager in xenial to the 1.6 series
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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** 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: - xenialin snap - libmbim 1.12.2-2ubuntu1 1.14.0 - libqmi 1.12.6-1 1.16.2 - modemmanager 1.4.12-1ubuntu1 1.6.2 + libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap + libqmi: 1.12.6-1 in xenial, 1.16.2 in snap + modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. -- 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/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in modemmanager package in Ubuntu: New Bug description: 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, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@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 same address, so it seems like network configuration is fine. So all looks good this time. -- 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 reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
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. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
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 reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@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 automatic roaming between APs with same SSID, see https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/devices/wifi /nm-device-wifi.c#n723 (it would be worth to propose a patch with new entries to this list for the cases you mention, adding "iPhone" to the list is probably a good idea). Having "Ubuntu" as default name in all phone devices is actually a bug and I will fill one for indicator-network. IMHO this sort of bugs shows some gaps in the WiFi standards that make it difficult to solve them without side effects. -- 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 reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@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 this works in your case, I am not sure if this is the right thing to do. If you have a network sharing SSID between APs (usual case in campus networks, for instance), you usually have just one DHCP server in the whole network. So in cases where the wireless network is properly configured, we would ask for lease renewals unnecessarily when we roam between APs. Note also that Android actually handles the case of having different DHCP servers in the same way, so maybe this solution is not completely insane. I still need to check in the AOSP code if there is some additional check going on before asking for the new IP. -- 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 reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
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 54 Mbit/s 100 WPA2 * Ubuntu Infra 1154 Mbit/s 91 WPA2 phablet@ubuntu-phablet:~$ ifconfig wlan0 wlan0 Link encap:Ethernet direcciónHW b8:64:91:47:21:b6 Direc. inet:192.168.43.189 Difus.:192.168.43.255 Másc:255.255.255.0 ... Then I removed the AP in channel 11. After waiting for some minutes to make sure we had re-scanned: phablet@ubuntu-phablet:~$ nmcli d wifi * SSID MODE CHAN RATE SIGNAL BARS SECURITY * Ubuntu Infra 1 54 Mbit/s 88 WPA2 It looks like the connection has moved to the other Ubuntu AP, but ping does not work, and the interface address has not changed: phablet@ubuntu-phablet:~$ ifconfig wlan0 wlan0 Link encap:Ethernet direcciónHW b8:64:91:47:21:b6 Direc. inet:192.168.43.189 Difus.:192.168.43.255 Másc:255.255.255.0 ... Apparently the IP configuration has not completed properly. I was able to return to a working state by doing phablet@ubuntu-phablet:~$ nmcli d wifi connect Ubuntu -- 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 reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
** 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. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Branchs linked for telephony-service and unity8, which will solve this in case media-hub restarts. @gtriderxc, thanks for the crash file, but unfortunately it misses the CoreDump field for some reason, not sure why yet. ** Changed in: unity8 (Ubuntu) Status: Confirmed => In Progress ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: In Progress Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in telephony-service package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
** 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 => Confirmed ** Branch linked: lp:~phablet-team/telephony-service/sms-notif-lp1544477 -- 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 System Image: Incomplete Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in telephony-service package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
@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. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Incomplete Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
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. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Incomplete Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
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, telegram notifications and videos/music still sound, but SMS notifications and screenshots do not emit sound anymore. So we have here: * A media-hub-server crash (could somebody please check if they have crash files for media-hub-server in /var/crash?) * An issue with reconnections to media-hub, for: 1. SMS notifications. telephony-service-indicator is the responsible for them 2. Screenshot sound. unity8 is the one emitting it Recently there was an effort to make media-hub *client library* resilient to media-hub-server crashes, but it looks like that has not been enough for this case. However, I am not sure if we can completely restore transparently from the library or we need that indicator/unity8 to be ready for media-hub crashes and be able to re-connect. ** Changed in: media-hub (Ubuntu) Status: Incomplete => Confirmed -- 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 System Image: Incomplete Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
@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 System Image: Incomplete Status in indicator-sound package in Ubuntu: Incomplete Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
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 '> /var/log/syslog' -> reproduce now the bug. Then gather the logs with tar cvzf log.tar.gz ~/.cache/upstart/* /var/log/syslog and upload log.tar.gz to launchpad. -- 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 System Image: In Progress Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
@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 System Image: In Progress Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
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. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: In Progress Status in indicator-sound package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
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 AalMediaPlayerControl::stop() ... [2016-08-16:15:21:09.090] virtual void AalMediaPlayerControl::play() [2016-08-16:15:21:09.091] void AalMediaPlayerService::play() ... [2016-08-16:15:21:09.689] qml: ItemGrabber: Saving image to /home/phablet/Pictures/Screenshots/screenshot20160816_152109689.png While in frieza we have: [2016-08-16:15:46:01.447] virtual void AalMediaPlayerControl::play() [2016-08-16:15:46:01.447] void AalMediaPlayerService::play() [2016-08-16:15:46:01.450] Actually calling m_hubPlayerSession->play() ... [2016-08-16:15:46:02.102] virtual void AalMediaPlayerControl::stop() ... [2016-08-16:15:46:02.378] qml: ItemGrabber: Saving image to /home/phablet/Pictures/Screenshots/screenshot20160816_154602378.png It seems that unity8 is doing something weird here, as it is stopping audio before it has called the "play" method in turbo. Looking at media-hub log, the stop command is received, but there is no play command. ** Attachment added: "screenshot-sound.tar.gz" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4722033/+files/screenshot-sound.tar.gz ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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 System Image: In Progress Status in indicator-sound package in Ubuntu: New Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574729] Re: Audio/Video not in sync on M10/frieza
** 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 Status in The Avila project: In Progress Status in Canonical System Image: In Progress Status in frieza: In Progress Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Watching a video (either with the media player or the browser) shows a lag between audio and video. It's out of sync for some hundred milliseconds, just enough to be very annoying while watching the video. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1574729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574729] Re: 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 M10/frieza Status in The Avila project: In Progress Status in Canonical System Image: In Progress Status in frieza: In Progress Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: Watching a video (either with the media player or the browser) shows a lag between audio and video. It's out of sync for some hundred milliseconds, just enough to be very annoying while watching the video. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1574729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574729] Re: Audio/Video not in sync on M10/frieza
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 delay again while watching a youtube video. There is definitely something wrong with pulseaudio sinks. -- 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 Status in The Avila project: In Progress Status in Canonical System Image: In Progress Status in frieza: In Progress Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: Watching a video (either with the media player or the browser) shows a lag between audio and video. It's out of sync for some hundred milliseconds, just enough to be very annoying while watching the video. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1574729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574729] Re: Audio/Video not in sync on M10/frieza
@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 ! lamemp3enc ! mux. qtmux name=mux ! filesink location=recode.mp4 demux. ! queue ! videoconvert ! x264enc ! mux. The resulting file has correct synchronization, so all points to pulseaudio or android drivers to be the culprit here. -- 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 Status in The Avila project: In Progress Status in Canonical System Image: In Progress Status in frieza: In Progress Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: Watching a video (either with the media player or the browser) shows a lag between audio and video. It's out of sync for some hundred milliseconds, just enough to be very annoying while watching the video. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1574729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588533] Re: Mobile Data Network not working after screen is off for more then 2 min
@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 notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1588533 Title: Mobile Data Network not working after screen is off for more then 2 min Status in Canonical System Image: Incomplete Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Bug description: With OTA-11 the Mobile Network 3G and H do not come back into working mode after MX4 comes back from turning off the screen. Example: I reboot the MX4 and when it powers up all is working I get WiFi and Mobile Network 3G working great. I press the button to turn off the screen and leave it off for 2 or more minutes, when I turn it back on and unlock the device the Data network is not working. I can make calls and SMS but MMS and Data has no connection, at this point i can toggle the Data switch in the mobile configuration or put the phone into airplane mode and back into active and it works until next time. Thank You To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
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.
+
+ * This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
+
+ phablet@ubuntu-phablet:~$ system-image-cli -i
+ current build number: 336
+ device name: krillin
+ channel: ubuntu-touch/rc-proposed/bq-aquaris.en
+ last update: 2016-05-17 09:19:51
+ version version: 336
+ version ubuntu: 20160517
+ version device: 20160329-a9bacdb
+ version custom: 20160505-975-38-9
+
+
+ Originally reported for:
+
NM version:
- network-manager 0.9.10.0-4ubuntu15.1.11
+ network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
-
phablet@ubuntu-phablet:~$ nmcli d
- DEVICE TYPE STATE CONNECTION
- ril_0gsm connecting (prepare) /214050030479893/context1
- wlan0wifi disconnected --
- ril_1gsm unavailable --
- ifb0 ifb unmanaged --
- ifb1 ifb unmanaged --
- lo loopback unmanaged --
- ip6tnl0 unknown unmanaged --
- sit0 unknown unmanaged --
- tunl0unknown unmanaged --
+ DEVICE TYPE STATE CONNECTION
+ ril_0gsm connecting (prepare) /214050030479893/context1
+ wlan0wifi disconnected --
+ ril_1gsm unavailable --
+ ifb0 ifb unmanaged --
+ ifb1 ifb unmanaged --
+ lo loopback unmanaged --
+ ip6tnl0 unknown unmanaged --
+ sit0 unknown unmanaged --
+ tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
- NAME UUID TYPE
DEVICE
- WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
- Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
- Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
- /234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
- /214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
- /214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
- /214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
-
- phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
+ NAME UUID TYPE
DEVICE
+ WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
+ Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
+ Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
+ /234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
+ /214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
+ /214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
+ /214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
+
+ phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
- [ /ril_0/context1 ]
- Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
- Name = Pepephone
- Type = internet
- AccessPointName = gprs.pepephone.com
- Active = 1
- Protocol = ip
- AuthenticationMethod = chap
- Password =
- Preferred = 0
- Username =
- IPv6.Settings = { }
-
- [ /ril_0/context2 ]
- Name = MMS Pepephone
- Type = mms
- Active = 0
- Settings = { }
- MessageCenter = http://www.pepephone.com
- MessageProxy = 10.138.255.43:8080
- Preferred = 0
- Password =
- AccessPointName = gprs.pepephone.com
- Protocol = ip
- AuthenticationMethod = chap
- Username =
- IPv6.Settings = { }
-
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
@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 is no active context).
--
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/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
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
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:308130 (308.1 KB) TX bytes:172906 (172.9
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
** 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. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Released Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535689] Re: Avila tablet is not recognised by libmtp
** 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 Avila project:
Fix Released
Status in Canonical System Image:
Fix Released
Status in libmtp package in Ubuntu:
Confirmed
Bug description:
The Avila tablet (product name is Frieza) is not recognised when in
MTP file mode by Ubuntu.
idVendor=2a47, idProduct=200D
Tested on a trusty/precise/wily laptop and found the device is not
listed in the desktop interface.
The line below will make it work normally just for testing.
ATTR{idVendor}=="2a47", ATTR{idProduct}=="200d", SYMLINK+="libmtp-%k",
MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
# Avila Frieza (MTP+ADB)
Reproduction Proceedure:
- Plug a tarblet into the Ubuntu desktop via a USB cable
- Expect to see a natuilus window pop up, with the option to browse and copy
files to the phone's file system
- Actual result: no response from the Ubuntu host.
Related OEM bug #1531494
To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1535689/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579098] Re: Mobile data connection drops, and doesn't automatically reconnect
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. https://bugs.launchpad.net/bugs/1579098 Title: Mobile data connection drops, and doesn't automatically reconnect Status in network-manager package in Ubuntu: New Bug description: Krillin, rc-proposed, r325 In the last couple of weeks it often happened that the mobile data connection dropped without reconnecting afterwards. I often find my device without mobile data connection without apparent reason. Switching mobile data connection Off and back On from settings restores the connection. I don't have any useful additional info to provide, unfortunately. Please let me know if you need log/cmd output in particular. phablet@ubuntu-phablet:~$ nmcli d status DEVICE TYPE STATE CONNECTION ril_1gsm disconnected -- wlan0wifi disconnected -- ril_0gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- ip6tnl0 ip6tnlunmanaged -- sit0 iptunnel unmanaged -- lo loopback unmanaged -- tunl0unknown unmanaged -- Syslog since last time mobile data was connected: http://pastebin.ubuntu.com/16259803/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
** 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 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
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 connecting (prepare) /214050030479893/context1
...
Which is a valid bug, as this is what would happen in case NM crashes.
--
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/1565717
Title:
No connection after returning from area without coverage
Status in network-manager package in Ubuntu:
New
Bug description:
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
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
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 cannot handle that unexpected connection when starting.
When using the faraday cage, what happened is that NM was notified of a
previous successful connection while in an intermediate state.
--
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/1565717
Title:
No connection after returning from area without coverage
Status in network-manager package in Ubuntu:
New
Bug description:
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
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0
[Desktop-packages] [Bug 1565717] [NEW] No connection after returning from area without coverage
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
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:308130 (308.1 KB) TX bytes:172906 (172.9 KB)
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems
[ /ril_1 ]
Serial = 354142069998062
Features = rat sim
Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
Manufacturer = Fake Manufacturer
Powered = 1
Lockdown = 0
Interfaces = org.ofono.RadioSettings org.ofono.SimManager
org.ofono.MtkSettings org.ofono.CallVolume org.ofono.VoiceCallManager
org.ofono.NetworkTime
Type = hardware
Model = Fake Modem Model
Online = 1
Emergency = 0
[ org.ofono.RadioSettings ]
TechnologyPreference = gsm
AvailableTechnologies = gsm
FastDormancy = 0
[ org.ofono.SimManager ]
Present = 0
[ org.ofono.MtkSettings ]
Has3G = 0
[ org.ofono.CallVolume ]
MicrophoneVolume = 0
SpeakerVolume = 0
Muted = 0
[
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
** 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-image Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato) => (unassigned) -- 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 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
** 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. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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 sent in step 1) 4. A few seconds later, the context is activated. Obviously the modem has registered again, but no event has triggered for that yet. 5. Modem says it is registered, right AFTER it has activated the context (which is maybe not the most correct sequence of events). Ofono detects that there are active context and it assumes it asked these context to close when it set Attached to FALSE. But that is not true as there were no active context when we did that. We do not change Attached property because ofono waits for old contexts to close before setting Attached to TRUE. 6. We stall until the active context is finally closed by some external event, which might happen hours later. While we are in this situation there is an active context, but probably it is not used by NM as it does nothing with ofono until Attached is TRUE. This last thing needs confirmation. -- 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 Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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 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 Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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 Ubuntu. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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 provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap to exec ofonod -d -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap -- 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 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
** 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. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Confirmed Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
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 might be ofono wrongly reporting a detached state, when connection to cellular might be actually possible. ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New -- 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 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: New Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
** 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 send on Tele2 Status in network-manager package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Fix Released Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@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: Can't receive MMS despite ability to send on Tele2 Status in network-manager package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@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/* files after a failed attempt to receive (probably better if performed from another phone: send the MMS and wait for 5 minutes before grabbing the logs)? Many 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/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in network-manager package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@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. https://bugs.launchpad.net/bugs/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in network-manager package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@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 receiving is working or not. -- 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 package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1361864] Re: add Preferred property to ConnectionContext interface
** 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. https://bugs.launchpad.net/bugs/1361864 Title: add Preferred property to ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Status in network-manager package in Ubuntu RTM: In Progress Status in nuntium package in Ubuntu RTM: Fix Released Status in ofono package in Ubuntu RTM: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1471116] [NEW] Get rid of 03mmsproxy script
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) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1471116 Title: Get rid of 03mmsproxy script Status in lxc-android-config package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: 03mmsproxy sets up routes for MMS. It is undocumented and possibly racy. It would be better if NetworkManager's ofono plugin did the job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1471116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1331813] Re: Support ipv6 mobile connections
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 notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1331813
Title:
Support ipv6 mobile connections
Status in network-manager package in Ubuntu:
Confirmed
Status in ofono package in Ubuntu:
Confirmed
Status in ubuntu-download-manager package in Ubuntu:
Confirmed
Bug description:
My new T-Mobile SIM only has Apn contexts using IPv6 so cellular data is not
working
Purchased the SIM a couple weeks ago.
The output of the /usr/share/ofono/list-contexts is:
[ /ril_0 ]
[ /ril_0/context1 ]
MessageProxy =
Type = internet
Password =
Active = 1
MessageCenter = http://mms.msg.eng.t-mobile.com/mms/wapenc
Username =
IPv6.Settings = { Interface=rmnet_usb0 }
AccessPointName = fast.t-mobile.com
Settings = { }
Name = T-Mobile GPRS
Protocol = ipv6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1331813/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
@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 really think that the auto-unlocking change is related, as that would not trigger after a reboot. -- 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/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: In Progress Status in network-manager package in Ubuntu: In Progress Status in network-manager package in Ubuntu RTM: In Progress Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
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 package in Ubuntu: Confirmed Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1361864] Re: add Preferred property to ConnectionContext interface
** 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 ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
** 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 combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1361864] Re: add Preferred property to ConnectionContext interface
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 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 ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: In Progress Status in ofono package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
** 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 combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
New
Status in network-manager package in Ubuntu:
In Progress
Status in ubuntu-download-manager package in Ubuntu:
Incomplete
Bug description:
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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
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 add_ofono_support.patch.
It is probable better to keep the change in MODEM_UID for consistency
inside NM, so I have changed the script to handle this change. See
attached.
** Attachment added: 03mmsproxy
https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1454625/+attachment/4397380/+files/03mmsproxy
--
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 combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
New
Status in network-manager package in Ubuntu:
In Progress
Status in ubuntu-download-manager package in Ubuntu:
Incomplete
Bug description:
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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi enabled
** 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 seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
- [ /ril_0/context1 ]
- Password =
- MessageCenter = http://www.pepephone.com
- Name = MMS Pepephone
- Username =
- Protocol = ip
- Preferred = 0
- IPv6.Settings = { }
- Settings = { }
- MessageProxy = 10.138.255.43:8080
- Type = internet
- AccessPointName = gprs.pepephone.com
- Active = 0
+ [ /ril_0/context1 ]
+ Password =
+ MessageCenter = http://www.pepephone.com
+ Name = MMS Pepephone
+ Username =
+ Protocol = ip
+ Preferred = 0
+ IPv6.Settings = { }
+ Settings = { }
+ MessageProxy = 10.138.255.43:8080
+ Type = internet
+ AccessPointName = gprs.pepephone.com
+ Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
- $ ifconfig
- rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
- inet addr:10.60.155.62 Mask:255.255.255.0
- inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
- UP RUNNING MTU:1500 Metric:1
- RX packets:4 errors:0 dropped:0 overruns:0 frame:0
- TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
+ $ ifconfig
+ rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
+ inet addr:10.60.155.62 Mask:255.255.255.0
+ inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
+ UP RUNNING MTU:1500 Metric:1
+ RX packets:4 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
- wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
- inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
- inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
- RX packets:355 errors:0 dropped:0 overruns:0 frame:0
- TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:100
- RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
+ wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
+ inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
+ inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:355 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:100
+ RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a routing
problem. The MMS proxy has private address 10.138.255.43 so it is not
reachable from WiFi.
- Found in mako vivid-proposed image #195.
+ Reproduced in:
+ mako vivid-proposed image #195
+ arale vivid-proposed image #38
--
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 combined contexts with WiFi connected
Status in network-manager package in Ubuntu:
New
Status in ubuntu-download-manager package in Ubuntu:
New
Bug description:
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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
[Desktop-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
** 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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a routing
problem. The MMS proxy has private address 10.138.255.43 so it is not
reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
+ krillin vivid-proposed image #205
--
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 combined contexts with WiFi connected
Status in network-manager package in Ubuntu:
New
Status in ubuntu-download-manager package in Ubuntu:
New
Bug description:
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:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0
