[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-04-08 Thread Alfonso Sanchez-Beato
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  [SRU] gstreamer fails with "cannot allocate memory in static TLS
  block" error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-04-08 Thread Alfonso Sanchez-Beato
Verified in focal:

ubuntu@host:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

ubuntu@host:~$ apt policy libc6
libc6:
  Installed: 2.31-0ubuntu9.2
  Candidate: 2.31-0ubuntu9.2
  Version table:
 *** 2.31-0ubuntu9.2 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
100 /var/lib/dpkg/status
 2.31-0ubuntu9 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

ubuntu@host:~$ rm .cache/gstreamer-1.0/registry.aarch64.bin 
ubuntu@host:~$ gst-inspect-1.0 >/dev/null
(gst-plugin-scanner:5268): GStreamer-WARNING **: 10:45:38.430: Failed to load 
plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstchromaprint.so': 
/lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
(gst-plugin-scanner:5268): GStreamer-WARNING **: 10:45:38.529: 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



ubuntu@host:~$ apt policy libc6
libc6:
  Installed: 2.31-0ubuntu9.3
  Candidate: 2.31-0ubuntu9.3
  Version table:
 *** 2.31-0ubuntu9.3 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 2.31-0ubuntu9.2 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
 2.31-0ubuntu9 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

ubuntu@host:~$ rm .cache/gstreamer-1.0/registry.aarch64.bin 
ubuntu@host:~$ gst-inspect-1.0 >/dev/null
(no errors now)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  [SRU] gstreamer fails with "cannot allocate memory in static TLS
  block" error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!

2021-03-23 Thread Alfonso Sanchez-Beato
Is this going to be backported to focal (see LP: #1919493)?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912844

Title:
  Bond with OVS bridging RuntimeError: duplicate mac found!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-03-15 Thread Alfonso Sanchez-Beato
On Mon, Mar 15, 2021 at 11:42 AM RussianNeuroMancer <
1914...@bugs.launchpad.net> wrote:

> For me Totem works now, but not totem-video-thumbnailer.
>
> Alfonso, Balint, how totem-video-thumbnailer works for you now?
>

It works for me, but I have just done a quick try. gstlaunch was what was
failing before and now is fine with the focal packages from the PPA.


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1914044
>
> Title:
>   [SRU] gstreamer fails with "cannot allocate memory in static TLS
>   block" error on aarch64
>
> Status in glibc package in Ubuntu:
>   Fix Released
> Status in glibc source package in Focal:
>   Confirmed
> Status in glibc package in Debian:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory
>   exhaustion, so these plugins cannot be used. See LP#1846837 and
>   LP#1914030.
>
>   This is solved apparently on glibc 2.32:
>   https://sourceware.org/bugzilla/show_bug.cgi?id=25051
>   by patch
>
> https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd
>
>   [Test Case]
>
>   Running totem-video-thumbnailer shows these errors:
>
>   (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
>
>   [Where problems could occur]
>
>   This is delicate code in glibc with quite regression potential. Said
>   this, the code is in the next minor release (2.32, while focal has
>   2.31), which has been running groovy for a while.
>
>   Also, apparently there is a 2.31 patch for groovy, before it moved to
>   2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions
>


** Bug watch added: Sourceware.org Bugzilla #25051
   https://sourceware.org/bugzilla/show_bug.cgi?id=25051

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  [SRU] gstreamer fails with "cannot allocate memory in static TLS
  block" error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-03-15 Thread Alfonso Sanchez-Beato
I have given a try to the test PPA and I can confirm it fixes the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  [SRU] gstreamer fails with "cannot allocate memory in static TLS
  block" error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-02-15 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914062

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1383858] Re: expr-simplify optimization slows click/snap policy compilation

2021-02-15 Thread Alfonso Sanchez-Beato
This MR for apparmor_parser:

https://gitlab.com/apparmor/apparmor/-/merge_requests/711

helps quite a bit with accelerating the expression optimization, and
actually makes it worth enabling them back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383858

Title:
  expr-simplify optimization slows click/snap policy compilation

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1383858/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-02-03 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914062

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

2021-02-01 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846837

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

2021-02-01 Thread Alfonso Sanchez-Beato
This is, I think, a glibc bug. See LP:#1914044

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846837

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

2021-02-01 Thread Alfonso Sanchez-Beato
This is, I think, a glib bug. See LP:#1846837.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846837

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914044] Re: gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-02-01 Thread Alfonso Sanchez-Beato
** Description changed:

  [Impact]
  
  gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory
  exhaustion, so these plugins cannot be used. See LP#1846837 and
  LP#1914030.
  
  This is solved apparently on glibc 2.32:
  https://sourceware.org/bugzilla/show_bug.cgi?id=25051
  by patch
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd
  
  [Test Case]
  
  Running totem-video-thumbnailer shows these errors:
  
  (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
  
  [Where problems could occur]
  
  This is delicate code in glibc with quite regression potential. Said
  this, the code is in the next minor release (2.32, while focal has
  2.31), which has been running groovy for a while.
+ 
+ Also, apparently there is a 2.31 patch for groovy, before it moved to
+ 2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  gstreamer fails with "cannot allocate memory in static TLS block"
  error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914044] [NEW] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64

2021-02-01 Thread Alfonso Sanchez-Beato
Public bug reported:

[Impact]

gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory
exhaustion, so these plugins cannot be used. See LP#1846837 and
LP#1914030.

This is solved apparently on glibc 2.32:
https://sourceware.org/bugzilla/show_bug.cgi?id=25051
by patch
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd

[Test Case]

Running totem-video-thumbnailer shows these errors:

(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

[Where problems could occur]

This is delicate code in glibc with quite regression potential. Said
this, the code is in the next minor release (2.32, while focal has
2.31), which has been running groovy for a while.

Also, apparently there is a 2.31 patch for groovy, before it moved to
2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914044

Title:
  gstreamer fails with "cannot allocate memory in static TLS block"
  error on aarch64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862279] Re: arm64 Secure Boot fails w/ "error: cannot load image."

2020-08-28 Thread Alfonso Sanchez-Beato
After working on LP: #1892770, I think that this is the same problem.
grub in focal/arm64 is trying to use EFI boot services to start the
kernel, after having verified the kernel with the shim. EFI does not
have access to the cert in the shim so it refuses to load the kernel.
There is a workaround which is adding Canonical Master key to the EFI
DB, so EFI can actually verify the kernel.

Looking at "loader/arm64/linux.c" in the sources seems to validate this.
In focal [1], grub_arch_efi_linux_boot_image() calls EFI boot services
b->load_image() and b->start_image() which is the same in upstream code.

However, in disco [2] the EFI boot services are not used - the sequence
is grub_armxx_efi_linux_boot_image() -> grub_efi_linux_boot() -> calls
directly an address in the loaded kernel.

The patch that makes the change in disco is
debian/patches/linuxefi_load_arm_with_sb.patch
(https://github.com/rhboot/grub2/commit/2786ab864cf00c15123320671f653e9a36ba12b4).

[1] 
https://git.launchpad.net/ubuntu/+source/grub2/tree/grub-core/loader/arm64/linux.c?h=applied/ubuntu/focal-updates#n122
[2] 
https://git.launchpad.net/ubuntu/+source/grub2/tree/grub-core/loader/arm64/linux.c?h=applied/ubuntu/disco-updates#n157

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279

Title:
  arm64 Secure Boot fails w/ "error: cannot load image."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1862279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command

2020-06-19 Thread Alfonso Sanchez-Beato
I have updated to focal-proposed and checked that now there is no

date: invalid date '  Wed Apr  1 17:23:44 2020'

output anymore in the console and that fixrtc finishes as expected.

$ apt info initramfs-tools
Package: initramfs-tools
Version: 0.136ubuntu6.2
...
$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-5.4.0-1003-bluefield root=LABEL=writable ro 
console=ttyAMA0 earlycon=pl011,0x0100 fixrtc
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal
$ uname -a
Linux ubuntu 5.4.0-1003-bluefield #4-Ubuntu SMP PREEMPT Fri Jun 12 17:02:31 UTC 
2020 aarch64 aarch64 aarch64 GNU/Linux


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880968

Title:
  fixrtc fails due to bad format of input to the date command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882894] [NEW] docker snap does not support custom apparmor profiles per container

2020-06-10 Thread Alfonso Sanchez-Beato
Public bug reported:

docker supports loading custom apparmor profiles that can be different
for each container [1] by using the option "--security-opt
apparmor=".

However, this does not work with the docker snap because the docker
snapd interface only allows sending signals to a profile named "docker-
default" (the default profile for docker containers), so if the name of
the profile is different, you cannot stop the container using the docker
cli. You get denials when trying to send the kill signal to the
container.

Allowing the docker snap to handle custom apparmor profiles for the
containers would allow further confinement of the payloads.

[1] https://docs.docker.com/engine/security/apparmor/

** Affects: docker (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: snapd (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: snapd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882894

Title:
  docker snap does not support custom apparmor profiles per container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1882894/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04

2020-06-09 Thread Alfonso Sanchez-Beato
** 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 Ubuntu
Bugs, which is subscribed to 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command

2020-06-04 Thread Alfonso Sanchez-Beato
** Description changed:

  The fixrtc script is failing with message:
  
  date: invalid date '  Wed Apr  1 17:23:44 2020'
  
  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs -h'
  ouptput, and some clean-up on it happens, but it looks like it is not
  enough for BusyBox' date command, at least for the version in focal.
+ 
+ [Impact]
+ 
+ The system date shown on first boot is incorrect, which can be
+ problematic on first boot if at that point in time there is no network
+ connection. If fixrtc works correctly at least we get the date of the
+ last time the rootfs was mounted, which is modern enough to avoid
+ problems with snap assertions validation, etc.
+ 
+ [Test case]
+ 
+ Boot an image with fixrtc in the kernel command line in a system with no
+ network. snap seeding will fail without the patch.
+ 
+ [Regression Potential]
+ 
+ Quite small, as the fix is small and targeted.

** Description changed:

  The fixrtc script is failing with message:
  
  date: invalid date '  Wed Apr  1 17:23:44 2020'
  
  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs -h'
  ouptput, and some clean-up on it happens, but it looks like it is not
  enough for BusyBox' date command, at least for the version in focal.
+ 
+ Backporting this to focal is needed.
  
  [Impact]
  
  The system date shown on first boot is incorrect, which can be
  problematic on first boot if at that point in time there is no network
  connection. If fixrtc works correctly at least we get the date of the
  last time the rootfs was mounted, which is modern enough to avoid
  problems with snap assertions validation, etc.
  
  [Test case]
  
  Boot an image with fixrtc in the kernel command line in a system with no
  network. snap seeding will fail without the patch.
  
  [Regression Potential]
  
  Quite small, as the fix is small and targeted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880968

Title:
  fixrtc fails due to bad format of input to the date command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881074] Re: Support btrfs when writable is converted to btrfs

2020-05-28 Thread Alfonso Sanchez-Beato
@Woodrow thanks for your changes - you are right the binaries are
already included by hooks from dependencies.

LGTM from my side - although I cannot review formally apparently :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881074

Title:
  Support btrfs when writable is converted to btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881074] Re: Support btrfs when writable is converted to btrfs

2020-05-28 Thread Alfonso Sanchez-Beato
Some comments on the debdiff:

Use
blkid -s TYPE "$writable_part" -o value
instead of
blkid -s TYPE "$writable_part" | awk '{print $2}' | grep -o '".*"' | tr -d '"'

No need to redirect to >>$LOGFILE in resize_filesystem() which is
already redirected when called. Also, you should not redirect to
/dev/kmsg - I guess that was for debugging purposes.

Is it really necessary to mount the partition to find out the filesystem usage?
"btrfs filesystem show" apparently can work on devices according to [1]. But it 
also looks like btrfs commands are mostly used with mounted systems, so it is 
fine if you want to keep things like that.

Finally, you will need to use copy_exec for btrfs and blkid to the
fixtrtc hook to get them included in the initramfs (although maybe blkid
comes from busybox in this case, not sure).

Otherwise, looks good to me.

[1] https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881074

Title:
  Support btrfs when writable is converted to btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command

2020-05-27 Thread Alfonso Sanchez-Beato
See attached debdiff for the fix

** Patch added: "initramfs-tools_debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+attachment/5377425/+files/initramfs-tools_debdiff.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880968

Title:
  fixrtc fails due to bad format of input to the date command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880968] [NEW] fixrtc fails due to bad format of input to the date command

2020-05-27 Thread Alfonso Sanchez-Beato
Public bug reported:

The fixrtc script is failing with message:

date: invalid date '  Wed Apr  1 17:23:44 2020'

when calling the date command. It looks like it does not like the
leading spaces for the input date. The date is taken from 'dumpe2fs -h'
ouptput, and some clean-up on it happens, but it looks like it is not
enough for BusyBox' date command, at least for the version in focal.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880968

Title:
  fixrtc fails due to bad format of input to the date command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2020-02-11 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855876] [NEW] Backport re-start service fix to xenial

2019-12-10 Thread Alfonso Sanchez-Beato
Public bug reported:

[Impact]
The backport to support netplan as a DBus service (LP: #1842511) is not 
complete without making sure that the network daemons are re-started as 
expected. The fix is included in Bionic, but not in Xenial. The upstream commit 
is 
https://github.com/CanonicalLtd/netplan/commit/0ef790cac1929ddea79d359f38645d8d92928b77
 .

[Test case]
Set NM as default renderer in a server installation with:

network:
  renderer: NetworkManager

Check the PIDs for NM and systemd-networkd. Run

netplan apply

And check that both processes have re-started.

[Regression potential]
The change is well confined and should not be difficult to port it back. 
Attention to the processes re-starting also in the previous use cases should be 
given.

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nplan (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: netplan
   Importance: Undecided
   Status: New

** No longer affects: netplan

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855876

Title:
  Backport re-start service fix to xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1855876/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813463] Re: no bluetooth intel ac 9260

2019-06-12 Thread Alfonso Sanchez-Beato
** Also affects: ubuntu
   Importance: Undecided
   Status: New

** No longer affects: snappy-hwe-snaps

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813463

Title:
  no bluetooth intel ac 9260

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1813463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1831914] [NEW] pppd crashes when running from the NM 1.10 snap

2019-06-06 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831914

Title:
  pppd crashes when running from the NM 1.10 snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1831914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] Re: [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-05-16 Thread Alfonso Sanchez-Beato
I have tested on xenial, the problem is solved with the change.

ubuntu@xenial:~$ apt policy resolvconf
resolvconf:
  Installed: 1.78ubuntu7
  Candidate: 1.78ubuntu7
  Version table:
 *** 1.78ubuntu7 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.78ubuntu6 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 1.78ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
ubuntu@xenial:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  [SRU] resolvconf is racy, which leads to broken resolv.conf in
  parallel calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] Re: [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-05-06 Thread Alfonso Sanchez-Beato
Thanks Robie, good catch. Please find attached the new patch for xenial:
I have moved a bit below the call to flock to ensure the dir was created
- the lines now out of the lock do not change any files so that should
not be a problem.

** Patch added: "xenial-debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+attachment/5261798/+files/xenial-debdiff.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  [SRU] resolvconf is racy, which leads to broken resolv.conf in
  parallel calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-04-22 Thread Alfonso Sanchez-Beato
@vorlon, @tsimonq2, patch for xenial attached, and description changed
for SRU. Sponsors teamm re-subscribed.

** Summary changed:

- resolvconf is racy, which leads to broken resolv.conf in parallel calls
+ [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  [SRU] resolvconf is racy, which leads to broken resolv.conf in
  parallel calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-04-22 Thread Alfonso Sanchez-Beato
Patch for xenial.

** Description changed:

+ [Impact]
+ 
+ The bug can lead to non-working DNS. This is a critical bug that needs
+ to be fixed in the stable release.
+ 
+ The patch fixes the bug by using a file lock via the flock command.
+ 
+ [Test case]
+ 
+ This script should eventually stop with the current version, thing that
+ should not happen after applying the patch:
+ 
+ while true; do
+ printf "\n" | sudo resolvconf -a NetworkManager
+ printf "nameserver 8.8.8.8\n" | sudo resolvconf -a networkd
+ wait
+ printf "nameserver 8.8.8.8\n" |
+ sudo resolvconf -a NetworkManager &
+ printf "\n" | sudo resolvconf -a networkd
+ wait
+ ping -c 1 www.google.com || break
+ done
+ 
+ [Regression Potential]
+ 
+ The patch is small and what it does is straightforward. It has also been
+ thoroughly tested. However, the effect if something is wrong would be
+ not being able to resolve DNS names, which is disastrous, so it needs to
+ be very well tested for the SRU.
+ 
+ [Other Info]
+ 
  It has been found that simultaneous calls to resolvconf can lead to
  inconsistent content in resolv.conf. For instance, no nameservers while
  NetworkManager has one in its record (see LP: #1824395):
  
  $ cat /run/resolvconf/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  
  $ cat /run/resolvconf/interface/NetworkManager
  nameserver 192.168.1.6
  nameserver 192.168.1.2
  
  This can happen easily when calling "netplan apply", which can re-start
  both networkd and NM. resolvconf is called at that point by the
  "systemd-networkd-resolvconf-update.service" service, and also directly
  by NetworkManager, which leads to the situation described above. This is
  not surprising as there is nothing preventing different instances of
  resolvconf to access the same files. This sort of situation can be
  reproduced by running in a loop commands like:
  
  $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo 
resolvconf -a networkd
  $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & 
printf "\n" | sudo resolvconf -a networkd
  
  Eventually, this leads to a resolv.conf that is not consistent with the
  last run command.

** Patch added: "xenial-debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+attachment/5257832/+files/xenial-debdiff.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  [SRU] resolvconf is racy, which leads to broken resolv.conf in
  parallel calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2019-04-22 Thread Alfonso Sanchez-Beato
I would very much like the SRU to happen.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-04-17 Thread Alfonso Sanchez-Beato
** Patch added: "debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+attachment/5256569/+files/debdiff.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  resolvconf is racy, which leads to broken resolv.conf in parallel
  calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825194] [NEW] resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-04-17 Thread Alfonso Sanchez-Beato
Public bug reported:

It has been found that simultaneous calls to resolvconf can lead to
inconsistent content in resolv.conf. For instance, no nameservers while
NetworkManager has one in its record (see LP: #1824395):

$ cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

$ cat /run/resolvconf/interface/NetworkManager
nameserver 192.168.1.6
nameserver 192.168.1.2

This can happen easily when calling "netplan apply", which can re-start
both networkd and NM. resolvconf is called at that point by the
"systemd-networkd-resolvconf-update.service" service, and also directly
by NetworkManager, which leads to the situation described above. This is
not surprising as there is nothing preventing different instances of
resolvconf to access the same files. This sort of situation can be
reproduced by running in a loop commands like:

$ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo 
resolvconf -a networkd
$ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & 
printf "\n" | sudo resolvconf -a networkd

Eventually, this leads to a resolv.conf that is not consistent with the
last run command.

** Affects: resolvconf (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  It has been found that simultaneous calls to resolvconf can lead to
  inconsistent content in resolv.conf. For instance, no nameservers while
  NetworkManager has one in its record (see LP: #1824395):
  
  $ cat /run/resolvconf/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  
  $ cat /run/resolvconf/interface/NetworkManager
  nameserver 192.168.1.6
  nameserver 192.168.1.2
  
- This can happen easily when calling "netplan generate", which can re-
- start both networkd and NM. resolvconf is called at that point by the
+ This can happen easily when calling "netplan apply", which can re-start
+ both networkd and NM. resolvconf is called at that point by the
  "systemd-networkd-resolvconf-update.service" service, and also directly
  by NetworkManager, which leads to the situation described above. This is
  not surprising as there is nothing preventing different instances of
  resolvconf to access the same files. This sort of situation can be
  reproduced by running in a loop commands like:
  
  $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo 
resolvconf -a networkd
  $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & 
printf "\n" | sudo resolvconf -a networkd
  
  Eventually, this leads to a resolv.conf that is not consistent with the
  last run command.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825194

Title:
  resolvconf is racy, which leads to broken resolv.conf in parallel
  calls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed

2019-03-25 Thread Alfonso Sanchez-Beato
Tested in cosmic, same steps as in bionic, all good.

abeato@toledo:~$ apt policy netplan.io
netplan.io:
  Installed: 0.96-0ubuntu0.18.10.1
  Candidate: 0.96-0ubuntu0.18.10.1
  Version table:
 *** 0.96-0ubuntu0.18.10.1 500
500 http://es.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 0.40.2.2 500
500 http://es.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
 0.40.2 500
500 http://es.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
abeato@toledo:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename:   cosmic


** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811868

Title:
  networkd/NetworkManager are not re-started on netplan apply when
  config files are removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed

2019-03-25 Thread Alfonso Sanchez-Beato
Tested in bionic:

Content of /etc/netplan/config.yaml :
https://paste.ubuntu.com/p/dD9sCCn46z/

abeato@numancia:~$ pidof NetworkManager
11173
abeato@numancia:~$ pidof systemd-networkd
10053
abeato@numancia:~$ sudo vi /etc/netplan/config.yaml -> edited to 
https://paste.ubuntu.com/p/PwpqcShfrn/
abeato@numancia:~$ sudo netplan apply
abeato@numancia:~$ pidof NetworkManager
12437
abeato@numancia:~$ pidof systemd-networkd
12428

abeato@numancia:~$ apt policy netplan.io
netplan.io:
  Instalados: 0.96-0ubuntu0.18.04.1
  Candidato:  0.96-0ubuntu0.18.04.1
  Tabla de versión:
 *** 0.96-0ubuntu0.18.04.1 500
500 http://es.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 0.40.1~18.04.4 500
500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 0.36.1 500
500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
abeato@numancia:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811868

Title:
  networkd/NetworkManager are not re-started on netplan apply when
  config files are removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819454] Re: resize does not work if partition is already bigger than fsystem

2019-03-11 Thread Alfonso Sanchez-Beato
** Patch added: "debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1819454/+attachment/5245398/+files/debdiff.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819454

Title:
  resize does not work if partition is already bigger than fsystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1819454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819454] [NEW] resize does not work if partition is already bigger than fsystem

2019-03-11 Thread Alfonso Sanchez-Beato
Public bug reported:

resize does not work if partition is already bigger than filesystem.

** Affects: initramfs-tools-devices (Ubuntu)
 Importance: Undecided
 Assignee: Oliver Grawert (ogra)
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819454

Title:
  resize does not work if partition is already bigger than fsystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1819454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812507] Re: Typo in description of snap

2019-01-22 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812507

Title:
  Typo in description of snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2019-01-07 Thread Alfonso Sanchez-Beato
@sil2100, where can I take a look at those?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2018-12-13 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

2018-12-11 Thread Alfonso Sanchez-Beato
@tytso awesome, thanks for pointing out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645232

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

2018-12-11 Thread Alfonso Sanchez-Beato
I am getting this in bionic, with e2fsprogs 1.44.1-1. In fact, I have
tried with e2fsprogs upstream and happens as well. I have simply
followed the instructions in the bug description to reproduce.

So, somewhat, although part of the patch was included upstream, it did
not fix completely the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645232

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788601] Re: [needs-packaging] It should be possible to use some initramfs-tools-ubuntu-core scripts in classic systems

2018-12-05 Thread Alfonso Sanchez-Beato
FTR, I had to do a small update for initramfs-tools-ubuntu-core, bumping
the version to 0.3.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788601

Title:
  [needs-packaging] It should be possible to use some initramfs-tools-
  ubuntu-core scripts in classic systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1788601/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788601] Re: [needs-packaging] It should be possible to use some initramfs-tools-ubuntu-core scripts in classic systems

2018-12-04 Thread Alfonso Sanchez-Beato
@tsimonq2, thanks for the review. I have uploaded to
https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/initramfs-
packages/+packages version 0.2 of initramfs-tools-ubuntu-core, which
resolves the issues that you mention (except not having added much more
headers to debian/copyright, as I do not think the missing ones really
apply).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788601

Title:
  [needs-packaging] It should be possible to use some initramfs-tools-
  ubuntu-core scripts in classic systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1788601/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788601] [NEW] It should be possible to use some initramfs-tools-ubuntu-core scripts in classic systems

2018-08-23 Thread Alfonso Sanchez-Beato
Public bug reported:

Some of the initramfs scripts included in initramfs-tools-ubuntu-core
could be re-used in classic systems. Concretely, the resize script. I
propose to split this package in two parts, one specific for Ubuntu
Core, keeping the name, and another one with scripts that can be useful
also in classic systems, especially on IoT ones.

I have uploaded to a PPA the resulting packages:
https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/initramfs-
packages/+packages

** Affects: ubuntu
 Importance: Undecided
 Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato)
 Status: In Progress


** Tags: needs-packaging

** Tags added: needs-packaging

** Changed in: ubuntu
   Status: New => In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788601

Title:
  It should be possible to use some initramfs-tools-ubuntu-core scripts
  in classic systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1788601/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788600] [NEW] It should be possible to use some initramfs-tools-ubuntu-core scripts in classic systems

2018-08-23 Thread Alfonso Sanchez-Beato
Public bug reported:

Some of the initramfs scripts included in initramfs-tools-ubuntu-core
could be re-used in classic systems. Concretely, the resize script. I
propose to split this package in two parts, one specific for Ubuntu
Core, keeping the name, and another one with scripts that can be useful
also in classic systems, especially on IoT ones.

I have uploaded to a PPA the resulting packages:
https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/initramfs-
packages/+packages

** Affects: initramfs-tools-ubuntu-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: needs-packaging

** Tags added: needs-packaging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788600

Title:
  It should be possible to use some initramfs-tools-ubuntu-core scripts
  in classic systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-core/+bug/1788600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

2018-08-02 Thread Alfonso Sanchez-Beato
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780606

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1692494] Re: klibc does not support reboot arguments

2018-07-16 Thread Alfonso Sanchez-Beato
The patch has been included in Debian klibc package 2.0.4-12:

http://metadata.ftp-
master.debian.org/changelogs/main/k/klibc/klibc_2.0.4-12_changelog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2018-07-13 Thread Alfonso Sanchez-Beato
** Summary changed:

- WoWLAN settings are not supported
+ [SRU] WoWLAN settings are not supported

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781597] [NEW] WoWLAN settings are not supported

2018-07-13 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781597

Title:
  WoWLAN settings are not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737432] Re: missing 'misc' folder

2018-03-02 Thread Alfonso Sanchez-Beato
For reference: https://groups.google.com/forum/#!topic/golang-
nuts/B7sZrDhhWfw

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737432

Title:
  missing 'misc' folder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.9/+bug/1737432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-29 Thread Alfonso Sanchez-Beato
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-26 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

2017-12-12 Thread Alfonso Sanchez-Beato
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735134

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-09 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-03 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-11-02 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-10-30 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-10-23 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-10-20 Thread Alfonso Sanchez-Beato
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2017-10-20 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693756

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725190] [NEW] Please update modemmanager in xenial to the 1.6 series

2017-10-20 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1725190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1692494] Re: klibc does not support reboot arguments

2017-09-12 Thread Alfonso Sanchez-Beato
It looks like both upstream and debian are not being responsive, looks
like klibc has no maintainer in neither of those. Should we add this
patch to the Ubuntu package?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-06 Thread Alfonso Sanchez-Beato
*** This bug is a duplicate of bug 1623125 ***
https://bugs.launchpad.net/bugs/1623125

@smb, actually, there is no create time field in the fs header, see

http://paste.ubuntu.com/25478756/

(this comes from a file with the mount time already corrected). This is
a partition created with android tools, as the ones from mkfs.ext4 do
not work for this device (for unknown reasons). I understand this is
sort of a special case though.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-05 Thread Alfonso Sanchez-Beato
@smb the concrete problem this was solving was happening with an armhf
device running Ubuntu Core. UC assertions were not validated and a
system user could not be created if there was no network (no date
update). Not sure if this was breaking the system even if later you
connected the device.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-09-05 Thread Alfonso Sanchez-Beato
@smb what I have seen is that devices lacking RTC battery tend to never
had a good date in the "last mount day" date of the root filesystem, as
when root is mounted the date is always near the epoch. The patch can
correct this, otherwise we would be getting the date systemd was built.

Of course this is not terribly accurate, but solves issues with
certificates/assertions that were deemed as not yet valid on first boot
if there was no network.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-06-09 Thread Alfonso Sanchez-Beato
New patch version, which includes now a patch from ogra (LP: #1623125)

** Patch added: "fixrtc-changes.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+attachment/4893078/+files/fixrtc-changes.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-06-09 Thread Alfonso Sanchez-Beato
This is the output of dumpe2fs:

http://paste.ubuntu.com/24815516/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC

2017-06-09 Thread Alfonso Sanchez-Beato
This debdiff adds a fixrtc-mount that helps with this issue by looking
at dates from files, once root has been mounted.

** Patch added: "add-fixrtc-mount.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+attachment/4893067/+files/add-fixrtc-mount.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1696981] [NEW] fixrtc is ineffective when there is no battery for the RTC

2017-06-09 Thread Alfonso Sanchez-Beato
Public bug reported:

When there is no battery for the RTC, fixrtc is not able to find a good
enough date. To fix the clock, this script is using the last time the
root filesystem was mounted, but as that is done before there is any
network, and as after a reboot/poweroff the RTC time is always reset
(because time is not kept due to lack of battery), the mount time will
never be good.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696981

Title:
  fixrtc is ineffective when there is no battery for the RTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1692494] Re: klibc does not support reboot arguments

2017-05-31 Thread Alfonso Sanchez-Beato
Reported to debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=863761

** Bug watch added: Debian Bug tracker #863761
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863761

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1692494] Re: klibc does not support reboot arguments

2017-05-25 Thread Alfonso Sanchez-Beato
Add a slightly modified version of the patch.

** Patch added: "add-reboot-argument-support.patch"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4883202/+files/add-reboot-argument-support.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1692494] [NEW] klibc does not support reboot arguments

2017-05-22 Thread Alfonso Sanchez-Beato
Public bug reported:

... so we cannot do things like "reboot recovery" in devices that follow
the Android partitions conventions.

** Affects: klibc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1692494] Re: klibc does not support reboot arguments

2017-05-22 Thread Alfonso Sanchez-Beato
** Patch added: "add-reboot-argument-support.patch"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4881283/+files/add-reboot-argument-support.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692494

Title:
  klibc does not support reboot arguments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

2017-04-04 Thread Alfonso Sanchez-Beato
I have tested the package in yakkety and fixed the issue for me too. In
my case it appeared when switching wifi connection between two APs which
shared the DHCP server.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1664994] Re: Black screen when trying to log in into unity8 session

2017-02-15 Thread Alfonso Sanchez-Beato
** Attachment added: "unity-system-compositor.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1664994/+attachment/4819575/+files/unity-system-compositor.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664994

Title:
  Black screen when trying to log in into unity8 session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1664994/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1664994] [NEW] Black screen when trying to log in into unity8 session

2017-02-15 Thread Alfonso Sanchez-Beato
Public bug reported:

When I log in into unity8 I get a black screen.

This is happening on xenial+overlay, using the unity8 snap. It seems to
have started to happen after doing a dist-upgrade which installed
packages from the overlay (15 Feb).

Installed snaps:

$ snap list
NameVersion Rev   Developer  
Notes
address-book-app0.2+17.04.20161219-0ubuntu1 21canonical  
devmode
camera-app  3.0.0+17.04.20170106-0ubuntu1   11canonical  
devmode
core16.04.1 1079  canonical  -
gallery-app 0.0.67+17.04.20161213-0ubuntu1  13canonical  
devmode
inkscape0.92.0  1880  inkscape   -
mediaplayer-app 0.20.5+17.04.20161201-0ubuntu1  x1   
devmode
ubuntu-app-platform 1   37canonical  
devmode
ubuntu-calculator-app   2.3.1   26ubuntucoredev  
devmode
ubuntu-calendar-app 0.1.1   22canonical  
devmode
ubuntu-clock-app3.8.480 29ubuntucoredev  
devmode
ubuntu-filemanager-app  0.4 10canonical  
devmode
ubuntu-terminal-app 0.1142canonical  
devmode
unity8-session  16.04   439   canonical  
devmode
webbrowser-app  20170119~staging10canonical  
devmode

See also attached unity-system-compositor.log and ~/user/.xsession-
errors

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "xsession-errors"
   
https://bugs.launchpad.net/bugs/1664994/+attachment/4819574/+files/xsession-errors

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664994

Title:
  Black screen when trying to log in into unity8 session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1664994/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1577641] Re: Unity8 creates a blank black window for windowless apps

2017-02-13 Thread Alfonso Sanchez-Beato
This is an issue for me too. The use case is media-hub on desktop. We
render into a framebuffer object and pass the textures to other process
(mediaplayer-app usually) that renders them in a window. We obviously do
not want a window shown by media-hub-server, but we need to connect to
mir to access the GPU and render into the fbo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577641

Title:
  Unity8 creates a blank black window for windowless apps

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577641/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1653373] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView color format.

2017-01-11 Thread Alfonso Sanchez-Beato
PR proposed with the patch:
https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/gst-
plugins-bad1.0/+git/gst-plugins-bad1.0/+merge/314513

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653373

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView
  color format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1653373/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1646144] Re: ACLs to devices need to be supported in core

2016-12-05 Thread Alfonso Sanchez-Beato
@ogra, I just tested edge and things work as expected (i.e. I can play
music as a normal user by adding it to ACLs for files in /dev/snd/*).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646144

Title:
  ACLs to devices need to be supported in core

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1639754] Re: Ethernet devices have higher metric than wlan or wwan ones

2016-11-11 Thread Alfonso Sanchez-Beato
@brian-murray, verified on xenial/kvm machine with configuration:

$ cat /etc/netplan/00-snapd-config.yaml 
network:
  ethernets:
eth0:
  dhcp4: true
  version: 2

With nplan 0.13~16.04:
$ ip route
default via 10.0.3.1 dev eth0 
default via 10.0.3.1 dev eth0  proto dhcp  src 10.0.3.223  metric 1024 
10.0.3.0/24 dev eth0  proto kernel  scope link  src 10.0.3.223 
10.0.3.1 dev eth0  proto dhcp  scope link  src 10.0.3.223  metric 1024

With nplan 0.14~16.04:
$ ip route
default via 10.0.3.1 dev eth0 
default via 10.0.3.1 dev eth0  proto dhcp  src 10.0.3.223  metric 100 
10.0.3.0/24 dev eth0  proto kernel  scope link  src 10.0.3.223 
10.0.3.1 dev eth0  proto dhcp  scope link  src 10.0.3.223  metric 100

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639754

Title:
  Ethernet devices have higher metric than wlan or wwan ones

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy-hwe-snaps/+bug/1639754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Alfonso Sanchez-Beato
@d.filoni, you can find gstreamer0.10 and qtmultimedia packages in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2147

Please give the silo a try and let us know if things work as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Alfonso Sanchez-Beato
@d.filoni oh, I see, there is some glue code missing in qtmultimedia in
all versions. That needs landing in xenial too indeed :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Alfonso Sanchez-Beato
Another note: playing opus works just fine because the code path in that
case goes through qtmultimedia -> qtubuntu-media -> media-hub ->
gstreamer 1.0.

So the missing thing is opus encoding in vivid for
qtmultimedia/gstreamer 0.10, and that is what Devid's patches fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Alfonso Sanchez-Beato
@timo-jyrinki regarding whether this is fixed in xenial or newer:

1. xenial uses qtmultimedia 5.5.1, which depends on gstreamer1.0
2. gstreamer1.0 moved the opus[dec|enc] codecs to plugins-base in version 1.8, 
which is included by default in phone images

So yes, this should be solved in xenial and newer.

Note also that this issue is happening because qtmultimedia 5.4.1 uses
old gstreamer 0.10. In fact you can already use opus in OTA13 by using
directly gstreamer1.0 instead of via Qt.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Alfonso Sanchez-Beato
** Changed in: canonical-devices-system-image
 Assignee: Jim Hodapp (jhodapp) => Alfonso Sanchez-Beato 
(alfonsosanchezbeato)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1516696] Re: SMS notifications are received only when the phone is unlocked

2016-11-02 Thread Alfonso Sanchez-Beato
** Changed in: ofono (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516696

Title:
  SMS notifications are received only when the phone is unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-10-28 Thread Alfonso Sanchez-Beato
@Pat, would you mind giving a try to this new one? The older one was
engineering build, which maybe was affecting performance.

** Attachment added: "boot.img"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1598584/+attachment/4768768/+files/boot.img

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598584

Title:
  wifi slows to a crawl when bluetooth is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/arale/+bug/1598584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-10-27 Thread Alfonso Sanchez-Beato
Attached there is the kernel with CONFIG_MTK_COMBO_BT enabled. For those
wanting to give it a try, it can be flashed with

$ fastboot flash boot boot.img

** Attachment added: "boot.img"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1598584/+attachment/4768276/+files/boot.img

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598584

Title:
  wifi slows to a crawl when bluetooth is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/arale/+bug/1598584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-27 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-27 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-27 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1637100] [NEW] Default hotspot SSID name should be customized per device

2016-10-27 Thread Alfonso Sanchez-Beato
Public bug reported:

Hotspot SSID name should be customized per device and not always use
"Ubuntu" as default. The reason is that APs with the same name and
authentication method are considered by the WiFi standards to belong to
the same network.

This makes that when we have two Ubuntu phones with hotspot activated,
clients try to roam between them. Having an unique identifier should be
easy to do, maybe by mangling some MAC bytes.

See related comments 11 and 12 in bug LP: #1478319.

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637100

Title:
  Default hotspot SSID name should be customized per device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1637100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-27 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-26 Thread Alfonso Sanchez-Beato
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-24 Thread Alfonso Sanchez-Beato
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-24 Thread Alfonso Sanchez-Beato
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1287267] Re: "Data usage statistics" not shown

2016-09-27 Thread Alfonso Sanchez-Beato
@Jonas, this is the spec:

https://developer.gnome.org/NetworkManager/unstable/gdbus-
org.freedesktop.NetworkManager.Device.Statistics.html

(we already upstreamed it, and backported to vivid).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287267

Title:
  "Data usage statistics" not shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1287267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1287267] Re: "Data usage statistics" not shown

2016-09-27 Thread Alfonso Sanchez-Beato
We have already implemented a data usage information DBus interface in
network-manager, which includes cellular radio interfaces. indicator-
network will eventually use it to show when there is data being
transmitted. It probably should also log the number of tx/rx bytes so
this information can be shown later by u-s-s.

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287267

Title:
  "Data usage statistics" not shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1287267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1612175] Re: All the available cellular networks are not searched and displayed

2016-09-16 Thread Alfonso Sanchez-Beato
@Ren, could you please also try /usr/share/ofono/scripts/scan-for-
operators ? Note that it might take a bit to complete.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612175

Title:
  All the available cellular networks are not searched and displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612175/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


  1   2   3   4   5   6   7   8   >