[Bug 2069860] Re: [needs-packaging] cmocka-extensions

[Loïc Minier]

** Changed in: ubuntu
   Status: Incomplete => Fix Released

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

Title:
  [needs-packaging] cmocka-extensions

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


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

[Bug 2069860] Re: [needs-packaging] cmocka-extensions

[Loïc Minier]

I'll respond at least for the version part since I chose the current
changelog setup

We've started cmocka-extensions from debian/ packaging created upstream
(by an ex-Canonical employee :-), so the copyright is to them, but I
guess we should now extend it to Canonical since we've developed some
changes.

This is also why there is a history of previous changelog entries that I
preserved for clarity to the packagers who worked upstream and on the
Ubuntu version of the package.

I'm ok with dropping the previous changelog entries if you think they
could break some tools.

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

Title:
  [needs-packaging] cmocka-extensions

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


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

[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy

[Loïc Minier]

I also booted the resulting Core image on a Jetson AGX Orin, I had to
try a couple of times, not sure why, perhaps quirks with the BIOS and me
trying to boot from a SD card reader, but eventually I got the installer
prompt from Ubuntu Core, albeit I didn't manage to progress it, I think
it demonstrates a good starting point for the image – might still have
to address the kernel/userspace etc.


  Ubuntu Core   

  Configure the network and setup an administrator account on this all-snap   
  Ubuntu Core system. 

  


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

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

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

Title:
  Support for Ubuntu Core tegra-igx images in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions


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

[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy

[Loïc Minier]

Installed 
https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.44/+build/28611104/+files/livecd-rootfs_2.765.44_arm64.deb
 in a jammy arm64 LXD container and ran commands from the Test plan:
ubuntu@jammy:~/build$ rm -rf auto local config
rm -f livecd.*.model-assertion
mkdir -p auto
for s in config build clean; do ln -s 
/usr/share/livecd-rootfs/live-build/auto/$s auto/; done
lb clean --purge
export PROJECT=ubuntu-core ARCH=arm64 SUBARCH=tegra-igx SUITE=jammy 
IMAGEFORMAT=ubuntu-image CHANNEL=edge
lb config
sudo -E lb build

[2024-06-28 13:46:32] lb_clean --purge
P: Executing auto/clean script.
[2024-06-28 13:46:32] lb_clean noauto --purge
P: Executing auto/clean script.
[2024-06-28 13:46:32] lb_clean noauto --all
P: Cleaning chroot
P: Executing auto/clean script.
[2024-06-28 13:46:32] lb_clean noauto --cache
[2024-06-28 13:46:32] lb_config 
P: Executing auto/config script.
Building on jammy.lxd
Configured ubuntu-image for the following model assertion:
type: model
authority-id: canonical
series: 16
brand-id: canonical
model: ubuntu-core-22-tegra-igx-edge
architecture: arm64
base: core22
grade: signed
snaps:
  -
default-channel: 22-igx/edge
id: 9pjCtYlNoT9Fx6RiHMhhBoIG6ZYXBvJc
name: tegra
type: gadget
  -
default-channel: 22-igx/edge
id: Rjyoy6Zhe9mlkBQqmVzaUdPB2TblFSwV
name: tegra-kernel
type: kernel
  -
default-channel: latest/edge
id: amcUKQILKXHHTlmSa7NMdnXSx02dNeeT
name: core22
type: base
  -
default-channel: latest/edge
id: PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4
name: snapd
type: snapd
timestamp: 2024-04-23T15:12:16+00:00
sign-key-sha3-384: 
9tydnLa6MTJ-jaQTFUXEwHl1yRx7ZS4K5cyFDhYDcPzhS7uyEkDxdUjg9g08BtNn

AcLBXAQAAQoABgUCZipp6AAKCRDgT5vottzAEj6mD/9lINl13Ju5yVBySIxByJVzJ84nxFlpFLAh
Bnb+7cNLAIWKLB57oG49oYx5aXpGaH3RNoQ9rGI/r7axRDgqpYStA0tFO0NM04sBWi4tkc2Cj+xj
v/uX//p+Xwx9IcynnvPG2aavfebA3tzBN3AV+QTjgo4rHhIJNiNNx8Qs7FHYTvFuZh6tYHbMX7wd
N0kE8axVCm8ado+vIbBmkzqE5EYoYtoer4DO90WqkmnGq07w+6Uth5AfUoXQfegl37xeXigAnhGO
sKos/FDw/G7IcAzp24VI4HmCnCj7W0I6iKmuEUr6JiXZoD7eEXr/CNMQpeeO/HD2vXnAmBF3V8W/
9brjFI5wTjHkxgMwzZ3z4RtqpG8Vx1Udcn6w2+cUzB3j5afJlg5mZAuE60StY38AVByaU4+PTSGv
nVP5ZQHiFQzz23VWmc5/blVDHYuvYikXUjbTBWfFszAby/UJIPvfS+dTTRNz0+cIa0qgkCsDma6B
qRDpepOXDw97mu1LwDH+SvLQM2Cnaa+tcO7cjslPiQq+MOjCVAgvOtZFi12lgpqJmwDiX8x4r3MZ
/fu7DO+zfPzjmujhr8p/skjRUmAu1OOwe8lrUzvfKBjm0j+hY02o8mV2NkkqxItnqQ3tyyUwyxlW
wXXWWlvCds7QJgP34C6m0CIhfwV8E2r/gaVvbkjv/Q==
--
[2024-06-28 13:46:32] lb_build 
P: Executing auto/build script.
WARNING: proceeding to download snaps ignoring validations, this default will 
change in the future. For now use --validation=enforce for validations to be 
taken into account, pass instead --validation=ignore to preserve current 
behavior going forward
Fetching snapd
Fetching tegra-kernel
Fetching core22
Fetching tegra

Worked fine, model assertion is correct and manifest is as expected:
ubuntu@jammy:~/build$ ls
auto
config
livecd.ubuntu-core-tegra-igx.img.xz
livecd.ubuntu-core-tegra-igx.manifest
livecd.ubuntu-core-tegra-igx.model-assertion
output
ubuntu@jammy:~/build$ cat livecd.ubuntu-core-tegra-igx.manifest 
core22 1522.snap
snapd 22283.snap
tegra-kernel 3.snap
tegra 1.snap

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

Title:
  Support for Ubuntu Core tegra-igx images in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions


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

[Bug 2069860] Re: [needs-packaging] cmocka-extensions

[Loïc Minier]

** Tags added: needs-packaging pe-archive-admin-request

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

Title:
  [needs-packaging] cmocka-extensions

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


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

[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx

[Loïc Minier]

Removing sponsoring tag as this is in NEW

** Tags removed: pe-sponsoring-request

** Tags added: pe-archive-admin-request

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

Title:
  [needs-packaging] xlnx-platformstats package from Xilinx

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


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

[Bug 2034648] Re: [needs-packaging] optee-os-s32

[Loïc Minier]

Hey, I'm removing the pe-sponsoring-request tag as this is taking a bit
longer, feel free to readd and/or ping me when another review is needed
:)

** Tags removed: pe-sponsoring-request

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

Title:
  [needs-packaging] optee-os-s32

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


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

[Bug 2069875] Re: [needs-packaging] cmocka-mocks

[Loïc Minier]

Package ready for sponsoring review at https://launchpad.net/~nemos-
team/+archive/ubuntu/archive-target/+sourcepub/16241780/+listing-
archive-extra

** Tags added: needs-packaging

** Tags added: pe-sponsoring-request

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

Title:
  [needs-packaging] cmocka-mocks

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


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

[Bug 2048228] Re: [needs-packaging] xmutil from Xilinx

[Loïc Minier]

This has been stalled for some time, let's drop the pe-sponsoring-
request tag and re-add it when ready

** Tags removed: pe-sponsoring-request

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

Title:
  [needs-packaging] xmutil from Xilinx

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


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

[Bug 2069860] Re: [needs-packaging] cmocka-extensions

[Loïc Minier]

Hey Steve,
Thanks for the feedback, just trying to pick a number that is higher than any 
previously used revisions, as Emlix is building their own debs using a Debian 
versioning scheme. Happy to reupload as -0ubuntu1, ignoring the Emlix versions 
entirely if you think that's a better strategy.

(We'll pass feedback to Emlix about not using Debian revisions.)

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

Title:
  [needs-packaging] cmocka-extensions

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


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

[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy

[Loïc Minier]

Uploaded 2.765.44, now in Unapproved
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd-
rootfs

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

Title:
  Support for Ubuntu Core tegra-igx images in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions


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

[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy

[Loïc Minier]

** Merge proposal linked:
   
https://code.launchpad.net/~rmartin013/livecd-rootfs/+git/livecd-rootfs/+merge/466187

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

Title:
  Support for Ubuntu Core tegra-igx images in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions


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

[Bug 2070070] [NEW] Support for Ubuntu Core tegra-igx images in jammy

[Loïc Minier]

Public bug reported:

This bug is to track changes needed to be able to build jammy Ubuntu
Core images for arm64+tegra-igx to support hardware based on NVIDIA
Tegra SoCs. NB some initial support had already been backported; see LP
#2015644.

[ Impact ]

 * This allows building missing image flavors for the NVIDIA Tegra families of 
hardware, notably Ubuntu Core images for the tegra-igx subarch.
 * This should also allow building of classic ISO installer images for 
tegra-igx, albeit that's a lesser priority.


[ Test Plan ]

 * Changes to livecd-rootfs were tested locally and can be tested from the 
-proposed package by building a Core image for tegra-igx as follows:
sudo apt install livecd-rootfs
mkdir build
cd build

rm -rf auto local config
rm -f livecd.*.model-assertion
mkdir -p auto
for s in config build clean; do ln -s 
/usr/share/livecd-rootfs/live-build/auto/$s auto/; done
lb clean --purge
export PROJECT=ubuntu-core ARCH=arm64 SUBARCH=tegra-igx SUITE=jammy 
IMAGEFORMAT=ubuntu-image CHANNEL=edge
lb config
sudo -E lb build


[ Where problems could occur ]

 * Changes are relatively light, but in the case of a regression for
instance due to broken logic, this could break existing image builds, in
which case an older livecd-rootfs could be reuploaded.


[ Other Info ]

 * These images are still being developed and its possible further
changes are needed as we iterate through the maturity of the image.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: livecd-rootfs (Ubuntu Jammy)
 Importance: Medium
 Status: In Progress

** Also affects: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Support for Ubuntu Core tegra-igx images in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

Word of warning, this is a complex topic!

So as you know, flash-kernel gets triggered quite often: when the kernel
gets updated, when packages participating in the contents of the
initramfs get updated (initramfs-tools, packages shipping modules), it
should probably also run  when f-k gets updated but I think it doesn't
right now. This happens through hooks in other packages when they are
doing certain things (kernel post-installation runparts, initramfs post-
generation runparts), and/or dpkg triggers, and/or regular package
maintainer scripts.

I /think/ Breaks should do the right thing in preventing most of these
runs until the new files are in place.

In general, the risks you're trying to manage:
- system is unbootable after attempting an upgrade
- system can't complete its upgrade and requires admin intervention
- windows of time where the system would be unbootable if we pulled the cord

One thing I'm worried about when I see kernel-flavor checks is that a
"strict" f-k flavor check kicks in while in the middle of upgrading
between flavors, resulting in the upgrade being aborted and/or leaving
the system in an unbootable state. This could either be the old f-k
being triggered with the new flavor, or it could also be the new f-k
being triggered while the old flavor is still there. I think it's easy
to kill the second case by listing both flavors in new f-k

There are other things that can happen: both old and new flavors being
on disk, and f-k being called to install the wrong, old one (I haven't
looked at how the two would get sorted; would the highest version win,
or would the name be preponderant?).

In general with updates and upgrades, you can assume:
- system might be updating from older packages in one series to newer packages 
in the same series
- system might be upgrading from one series to the next, or for one LTS to the 
next, but a) latest updates must be installed before upgrading, b) can't jump a 
series or jump an LTS in an upgrade
- system might be half-updated or half-upgraded and lose power, ideally we want 
this system to still boot and later continue with the update/upgrade
- you can only count on enforcing the order of updates/upgrades through 
versioned dependencies such as depends/breaks/conflicts


All of these scenarios are already quite hairy; let's say we have managed all 
of these perfectly in our packaging. We might also want to do backports:
- backport a new kernel to an older Ubuntu (not sure we're planning this), but 
perhaps the f-k in that older Ubuntu doesn't support that flavor
- backport a new f-k to an older Ubuntu (I think this is rare, but might be 
needed when you want to support a new flavor in an older and the f-k version in 
the older series didn't support it) but perhaps the new f-k is not ready to 
support the old kernel flavor

The hardest stretch in backwards compat is when we are backporting a
version of a package from one LTS to the previous LTS, then this package
might be around from old LTS to next LTS, spanning 2 LTSes.

You can probably ignore the backports scenarios for this work, just
wanted to share them for completeness.

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

Alternatively, you can add a versioned conflict on f-k in the kernel
package (Breaks << versions of f-k prior to the change)

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

I'm not sure if f-k supports having multiple device tree options; you
probably also can't have multiple entries for the same machine but
different kernels/device trees.

My recommendation would be to add both transitional packages for
upgrades, and provide the old device tree name in the new kernel.

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

For the CMA change, I guess it's easy enough to release note this in
oracular, but I'm less clear on noble: are we going to reroll existing
images with the change? How will we communicate on the differences
between old and new images with larger and smaller CMA?

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

Actually, sorry, I see that your other change on device tree names might
require the new kernel flavor; are the new and old device tree names
available in both old and new kernel? How do we ensure people don't
upgrade to a broken combination?

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel

[Loïc Minier]

Hi Talha,

This is subjective, but I would suggest not dropping the xilinx-zynqmp flavor 
from the list immediately for two reasons:
- might be useful across upgrades (e.g. I upgrade f-k but not the kernel)
- in the case of a backport of f-k

The f-k kernel flavors are an useful protection in the face of trying to
run the raspi kernel on a xilinx platform, but I don't know if we'd gain
much by enforcing the removal of the old kernel flavor name. We could
drop it after the next LTS though.

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

Title:
  [SRU] flash-kernel to support xilinx kria platforms with noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions


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

[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx

[Loïc Minier]

** Changed in: ubuntu
   Status: In Progress => Fix Committed

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

Title:
  [needs-packaging] xlnx-platformstats package from Xilinx

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


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

[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx

[Loïc Minier]

(I went ahead and uploaded this version after fixing copyright file.)

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

Title:
  [needs-packaging] xlnx-platformstats package from Xilinx

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


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

[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx

[Loïc Minier]

Hi Talha,
Did another pass on this, and I only spotted one area that should be easy to 
fix: debian/copyright says GPL-3+ for debian/, but license grant snippet says 
exactly version 3 is offered:
License: GPL-3+
 This program is free software: you can redistribute it and/or modify it
 under the terms of the GNU General Public License version 3, as
 published by the Free Software Foundation.

it also refers to the Lesser GPL for some reason "See the applicable
version of the GNU Lesser General Public License for more details."

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

Title:
  [needs-packaging] xlnx-platformstats package from Xilinx

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


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

[Bug 2034648] Re: [needs-packaging] optee-os-s32

[Loïc Minier]

I'm starting to take a look at optee-os-s32 (optee-
os-s32_3.18-bsp37.0-0ubuntu1~ppa4.dsc) towards sponsoring it.

0) I think it's worth stating why we want the package. optee-os provides
the "secure world" side of the OPTEE TEE implementation, which is
typically loaded very early in the boot process of Arm platforms such as
the NXP S32x family, and could be needed as part of the boot process.
NXP has forked from https://github.com/OP-TEE/optee_os/ to add support
for their S32x platform. Separately, NXP's OPTEE implementation can
optionally be built with support for NXP's discrete security component
called "HSE". We would like to add this package to Ubuntu as for its
binaries to be included in to-be-created Ubuntu images for S32x
platforms. These images would initially be without HSE support as it
currently depends on a proprietary non-redistributable NXP firmware.

1) First, I thought we had a copy of optee_os in Debian/Ubuntu for some time 
already, but actually we only had optee_client (Source: optee-client) – 
until... oracular since we just imported optee-os_4.2.0-3.dsc from Debian. It 
was failing to build, I've just uploaded a build fix.
  optee-os and optee-os-s32 probably have disjoint development history, but it 
would be in our interest to keep these close as to find some similarities when 
we address one issue in one to carry the fix in the other. Unfortunately, these 
are quite far apart in terms of upstream versions. I'm not sure how much there 
is to align on between the two packages, but at least the way the build is 
called is slightly different since optee-os was failing to build due to taking 
Ubuntu's LDFLAGS while optee-os-s32 builds and seems not pass LDFLAGS through. 
It's not exactly a run of the mill shared ELF file to start with, but it might 
be worth comparing the ways both are built. I think we should at least try to 
align package names/splits and list of files as to imagine a world where S32x 
support for upstream, and optee-os can build a flavor for S32x (much like the 
u-boot package).
  optee-os provides subdirs under usr/lib/optee for each target platform:
/usr/lib/optee/k3-am62x/tee-raw.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-header_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-pageable_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-pager_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-header_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-pageable_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-pager_v2.bin
  while optee-os-dev provides a bunch of development files suc as headers, 
pre-built binaries, assembly files and makefiles. These are also under platform 
specific directories:
/usr/lib/optee-os-dev/PLATFORM/host_include/**/*.{h,ta,a,S}
/usr/lib/optee-os-dev/PLATFORM/host_include/conf.{mk,.h,cmake}
/usr/lib/optee-os-dev/PLATFORM/include/**/*.h
/usr/lib/optee-os-dev/PLATFORM/mk/*.mk
/usr/lib/optee-os-dev/PLATFORM/scripts/*.py
/usr/lib/optee-os-dev/PLATFORM/src/*.{S,c}
/usr/lib/optee-os-dev/PLATFORM/ta/*.ta
  where PLATFORM is in arm-plat-k3, vexpress-qemu_armv8a, 
vexpress-qemu_armv8a-virtualized. (I didn't attempt diffing the headers)

The optee-os-s32 deb follows a similar layout as optee-os:
/usr/lib/optee-os-s32/s32g2/tee-header_v2.bin
/usr/lib/optee-os-s32/s32g2/tee-pager_v2.bin
(not sure why no tee-pageable_v2, I don't know what it does)
  while optee-os-s32-dev install similar headers as optee-os-dev but under a 
slightly different pathes
/usr/share/optee-os-s32/export-ta_arm64/host_include/
/usr/share/optee-os-s32/export-ta_arm64/include/
/usr/share/optee-os-s32/export-ta_arm64/lib/
/usr/share/optee-os-s32/export-ta_arm64/mk/
/usr/share/optee-os-s32/export-ta_arm64/scripts/
/usr/share/optee-os-s32/export-ta_arm64/src/
/usr/share/optee-os-s32/export-ta_arm64/ta/

=> I think this should be "s32g2" instead of "export-ta_arm64" since
optee is built with PLATFORM=s32 PLATFORM_FLAVOR=s32g2

=> I think we should align the build command between optee-os and optee-
os-s32 (config flags)

2) In general, presence of .c/.S/.a files suggest we should use Built-
Using in packages build-depending on optee-* dev packages; this should
be documented in some README.Debian (also missing in Debian's optee-os)

3) optee-os-s32 build-depends on nemos-dev-cert and nemos-dev-key; first, I 
don't think it makes sense to use a project specific key for general purpose 
S32x enablement, so think this should be at least ubuntu-s32-default-key or 
something rather than nemos-xyz, but in optee-os I've spotted files such as:
/usr/lib/optee-os-dev/arm-plat-k3/keys/default.pem
/usr/lib/optee-os-dev/arm-plat-k3/keys/default_ta.pem -> default.pem
  these suggest that there is a strategy to build a default root of trust in 
the optee-os package, so perhaps there is already a solution there.

4) IMO the build-dep on binutils can be dropped; binutils is pulled
through gcc through build-essential, so pretty much no package will list
it explicitly


5) 

[Bug 2056099] Re: [MIR] tree

[Loïc Minier]

[ NB: debdiff from Mate was uploaded to noble by Simon; see also bug
#2060550; thanks Mate and Simon! ]

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

Title:
  [MIR] tree

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


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

[Bug 2043448] Re: [needs-packaging] nemos-dev-key

[Loïc Minier]

Hi, I saw that Laider addressed the last remaining issue called here
(the specific debian/copyright Indicator Weather copy-paste typo);
reviewing only this change compared to 1.7, I sponsored the delta.

Since this is a new package and the first time I am sponsporing it, I took a 
wider look and noted the following opportunities for improvement:
 * the control file lists Isaac as original maintainer with his Canonical 
address; this should be removed
 * I've personally just now subscribed to the nemos-team@LP mailing-list, 
perhaps Laider and others should too
 * description of the package is a bit terse, should mention that it is used to 
sign the boot in generated images for the NemOS project
 * subjective/personal perspective: I suspect this is broken down into too many 
very small packages; could probably be just a single package
 * there is no explanation/documentation for the Provides; this is likely a 
case of someone being able to craft their own key-carrying deb and host that 
privately (would need to think of hosting this so that only CI/CD for image 
generation could get access to the private key!)
 * there is no documentation as to where the pre-built files 
(rsa2048_private.pem, rsa2048_public.pem, u-boot-signature.dtsi) are coming 
from, nor how these were generated; these are fairly obvious (perhaps the 
u-boot device tree source snippet a bit less), but would seem useful

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

Title:
  [needs-packaging] nemos-dev-key

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


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

[Bug 2056099] Re: [MIR] tree

[Loïc Minier]

Uploaded debdiff adding a basic unit test framework from upstream gitlab
merge proposal to noble as tree 2.1.1-2ubuntu1

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

Title:
  [MIR] tree

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


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

[Bug 2058460] Re: Recursion limit too low for jammy universe

[Loïc Minier]

** Changed in: germinate (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Recursion limit too low for jammy universe

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


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

[Bug 2043448] Re: [needs-packaging] nemos-dev-key

[Loïc Minier]

I'm getting all files installed in nemos-dev-key and the two other packages are 
empty:
W: nemos-dev-cert: empty-binary-package
W: nemos-dev-cert-u-boot: empty-binary-package

Did you perhaps not git add newly added debian/*.install files?

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

Title:
  [needs-packaging] nemos-dev-key

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


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

[Bug 2058460] Re: Recursion limit too low for jammy universe

[Loïc Minier]

** Changed in: germinate (Ubuntu)
 Assignee: (unassigned) => Loïc Minier (lool)

** Changed in: germinate (Ubuntu)
   Status: New => In Progress

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

Title:
  Recursion limit too low for jammy universe

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


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

[Bug 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0

[Loïc Minier]

It might cause performance regressions in production though; would you
be able to document the failing tests here?

I wonder if we would simply have to cherry pick more from 3.2 for these
to pass.

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

Title:
  Backport Intel's AVX512 patches on openssl 3.0

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

Thanks John!

I've changed the bug tasks back to lintian as it sounds like the most
reasonable short-term option would be to patch lintian to pick a
predictable directory and update the apparmor profiles; later, we will
have new apparmor to deal with this situation more elegantly

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

@Seth: I was only using /tmp/output to not write to the current dir; the
typical case is lintian creating a safe tmpdir.

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

** Changed in: lintian (Ubuntu)
   Status: New => Confirmed

** No longer affects: groff (Ubuntu)

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

I'm not sure how to properly fix this, we allow the shell to write
anywhere, then file_inherit is triggered because we don't want man to
write anywhere, which seems to be what we typically want to achieve with
the apparmor profile.

Should we teach lintian and perhaps every other tool to use a specific
directory?

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

This is due to the apparmor profile and the man pipeline trying to flush
and stat the output file which can be anywhere in the fs

[Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.791:651): 
apparmor="DENIED" operation="file_inherit" class="file" 
namespace="root//lxd-daily_" profile="man_groff" 
name="/tmp/output" pid=97274 comm="troff" requested_mask="w" denied_mask="w" 
fsuid=1001000 ouid=1001000
[Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.819:652): 
apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - 
disconnected path" error=-13 
namespace="root//lxd-daily_" profile="/usr/bin/man" 
name="apparmor/.null" pid=97274 comm="troff" requested_mask="r" denied_mask="r" 
fsuid=1001000 ouid=0
[Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.819:653): 
apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - 
disconnected path" error=-13 
namespace="root//lxd-daily_" profile="man_groff" 
name="apparmor/.null" pid=97274 comm="troff" requested_mask="r" denied_mask="r" 
fsuid=1001000 ouid=0


** Description changed:

  groff crash when redirecting output to a file
  
  % man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/cat.1.gz >output
  troff::3: fatal error: unable to flush output file: 
Permission denied
  groff: error: troff: Segmentation fault (core dumped)
  man: command exited with status 2: /usr/libexec/man-db/zsoelim | 
/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e 
UTF-8 | tbl | groff -mandoc -Z -rLL=78n -rLT=78n -wmac -Tutf8
+ 
+ This is typically triggered by lintian when scanning man pages

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

** Description changed:

- Hello,
+ groff crash when redirecting output to a file
  
- I was trying to run lintian on some deb packages an run onto some errors
- messages from groff.
- 
- Steps to reproduce:
- 
- 1. Setup a LXD container with mantic or Noble:
- 
- lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic
- 
- 2. After getting connected to the container: Install lintian on it
- 
- apt install lintian
- 
- 3. Run lintian on some package inside the container:
- 
- apt download tree && lintian tree_*.deb
- 
- 4. Enjoy the groff-message logs:
- 
- W: tree: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/tree.1.gz:2]
- W: tree: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/tree.1.gz:1]
- 
- * Container infos:
- 
- lsb_release -rd
- 
- No LSB modules are available.
- Description:Ubuntu Noble Numbat (development branch)
- Release:24.04
- 
- * Packages infos:
- 
- apt-cache policy groff
- groff:
-   Installed: (none)
-   Candidate: 1.23.0-3
-   Version table:
-  1.23.0-3 500
- 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
- 
- apt-cache policy lintian
- lintian:
-   Installed: 2.117.0ubuntu1
-   Candidate: 2.117.0ubuntu1
-   Version table:
-  *** 2.117.0ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
- 100 /var/lib/dpkg/status
- 
- * Expected output (on Jammy): No segfault and no problem on the tested
- package with lintian (tree_2.1.1-2_amd64.deb)
+ % man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/cat.1.gz >output
+ troff::3: fatal error: unable to flush output file: 
Permission denied
+ groff: error: troff: Segmentation fault (core dumped)
+ man: command exited with status 2: /usr/libexec/man-db/zsoelim | 
/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e 
UTF-8 | tbl | groff -mandoc -Z -rLL=78n -rLT=78n -wmac -Tutf8

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Loïc Minier]

** No longer affects: lintian (Ubuntu)

** No longer affects: ubuntu

** Changed in: groff (Ubuntu)
   Status: New => Confirmed

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

Title:
  Though lintian call: error: troff: Segmentation fault

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


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

Re: Requesting autopkgtests

[Loïc Minier]

Hi,

Really nice improvement indeed! Much like Christian, we'd want to give back
autopkgtests from time to time when working on some ports, or on optimized
Ubuntu packages and images. The relevant team would be
https://launchpad.net/~canonical-partner-eng, and we would send explicit
guidance to people in that team or joining that team to work on Ubuntu on
when it's proper to give back an autopkgtest.

Thanks!
- Loïc

On Tue, 18 Jul 2023 at 07:42, Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:

> On Mon, Jul 17, 2023 at 1:54 AM Brian Murray  wrote:
> >
> > The set of people who can trigger autopkgtests at autopkgtest.ubuntu.com
> > has been recently expanded to include a new team[1] in Launchpad. The
> > Canonical Foundations team has been added to the autopkgtest-requestors
> > team and this has made their +1 maintenance shifts and proposed
> > migration work much easier.
>
> Thanks for addressing this issue, it is much appreciated!
> No more length lists of "could you restart that for me" links.
>
> > If you, or a team of which you are an
> > administrator, are interested in having the ability to retry
> > autopkgtests for packages which you do not have upload rights please get
> > in touch with myself or another member of the Ubuntu QA team.
>
> I'd ask for [1] to be added to [2]. That would cover the server team and a
> few closely related friends in CPC and actually QA as well :-) The set of
> People in that group are tightly controlled and I'd not be concerned about
> abuse of the test restart permission by any of the current or future
> members of it.
>
> [1]: https://launchpad.net/~canonical-server
> [2] https://launchpad.net/~autopkgtest-requestors
>
> >
> > Cheers,
> > --
> > Brian Murray
> >
> > --
> > ubuntu-devel mailing list
> > ubuntu-devel@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
>
>
>
> --
> Christian Ehrhardt
> Senior Staff Engineer and acting Director, Ubuntu Server
> Canonical Ltd
>
> --
> ubuntu-devel mailing list
> ubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
>


-- 
Loïc Minier
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

Upload is pending review in focal Unapproved queue:
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

** Changed in: flash-kernel (Ubuntu Focal)
 Assignee: (unassigned) => Loïc Minier (lool)

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

** Also affects: flash-kernel (Ubuntu Focal)
   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/1962289

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

flash-kernel (3.104ubuntu8) jammy; urgency=medium

  * mkimage_fit: subst KERNEL_VERSION in ITS file with actual kernel
version.
  * Add DB entry, bootscript and ITS templates for Mediatek AIoT i500 board.

Date: Sun, 03 Apr 2022 19:33:03 +0200
Changed-By: Ethan Hsieh 
Maintainer: Ubuntu Developers 
Signed-By: Loïc Minier 
https://launchpad.net/ubuntu/+source/flash-kernel/3.104ubuntu8

==

 OK: flash-kernel_3.104ubuntu8.tar.xz
 OK: flash-kernel_3.104ubuntu8.dsc
 -> Component: main Section: utils


** Changed in: flash-kernel (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

I've re-reviewed this, updated README to match the new behavior and
tweaked changelog slightly, and I've uploaded this to jammy - failing to
add the LP: #1962289 in changelog; it's currently in the UNAPPROVED
queue
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=

I agree this should go with Debian along with a bazillion changes we
have in Ubuntu, but such "API" like changes would indeed ideally be
prioritized in our upstreaming efforts.

** Changed in: flash-kernel (Ubuntu)
 Assignee: (unassigned) => Loïc Minier (lool)

** Changed in: flash-kernel (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

@Ethan: sounds good; perhaps one way to think about it could be:
1) the kernel knows which dtbs and dtbos are supported with a particular kernel 
build
2) flash-kernel has a clear and stable interface to pull the right bits into a 
FIT image but does not need to keep track of the list in flash-kernel itself

One way to go would be to agree that all *.dtbo in a particular
subdirectory of the kernel deb should be included, or even better,
having a list of dtbos for a particular board; flash-kernel could keep
the FIT image template, but would iterate over the dtbos listed in the
kernel-provided file to generate the FIT image.

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962289] Re: Mediatek AIoT i500 support

[Loïc Minier]

Hi there,

Thanks for the nice debdiffs; reading through these, I see the following 
changes:
1) a new boot script – fine, albeit flash-kernel seems to collect more and more 
of them and it would be good to avoid having too many
2) support for using the kernel ABI version in substs – why not, albeit it's a 
bit surprising this wasn't needed so far, and it looks like this might be 
breaking an abstraction
3) a new its file as a template for the FIT image; this one seems really wrong 
to me because it has this long list of dtbos which will likely evolve across 
kernel versions

IMO the job of flash-kernel is to keep track of the method with which we
install kernels/initramfses/other boot assets, but once a method is
implemented, it can be used for a long time. Here, the list of dtbos is
very long and seems very platform specific, so it's likely to evolve
with kernel versions, so it will likely result in having to update
flash-kernel for a new kernel, or having to manage versioned
dependencies like "at least this version of flash-kernel to get the its
that installs this list of dtbos".

I'm not sure what the proper solution is, it could be that the its file
should be provided by the kernel rather than flash-kernel, like dtbs, or
perhaps we need to scan for dtbo files.

What would be really useful would be to explain how these dtbos are
being used, what's the scenario in which they are used in the FIT image?

Thanks!

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

Title:
  Mediatek AIoT i500 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions


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

[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline

[Loïc Minier]

Please attach the reproducing pipeline; it's a bit tricky to organise
access to Jetson hardware to the right people, so if you had a
reproducer that we could run without Jetson hardware, that would be
best!

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

Title:
  Intermittent very low fps(sometimes zero) with few specific h264 and
  h265 RTSP input streams sources when used with gst-v4l2 based
  gstreamer-1.0(version gst-1.14.5) decode pipeline

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions


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

[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04

[Loïc Minier]

Hi Kunal,
It might be tricky to organise testing on Jetson platforms for people that will 
prepare the fix.

In any case, could you share instructions to reproduce? If there's a way
to craft a test pipeline that trigger the issue without Jetson hardware,
that would be best.

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

Title:
  Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range:
  assertion 'bufmax >= bufoffs + offset + size' failed" warning on
  gstreamer version 1.16 on ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions


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

[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04

[Loïc Minier]

Would you be able to share a reproducing pipeline? ideally that can be
run on vanilla Ubuntu rather than on specific hardware or with Nvidia
added plugins

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

Title:
  Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range:
  assertion 'bufmax >= bufoffs + offset + size' failed" warning on
  gstreamer version 1.16 on ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions


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

[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04

[Loïc Minier]

This patch landed upstream in 1.17.90, marking only bionic and focal as
possibly affected

** Also affects: gstreamer1.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gstreamer1.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range:
  assertion 'bufmax >= bufoffs + offset + size' failed" warning on
  gstreamer version 1.16 on ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions


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

[Bug 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04

[Loïc Minier]

** Also affects: gstreamer1.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962135/+subscriptions


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

[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline

[Loïc Minier]

The mentioned upstream patch was included in the 1.15.2 release and
jammy and focal are unaffected; bionic does not have this patch in
1.14.5-0ubuntu1~18.04.3

** Package changed: gstreamer1.0 (Ubuntu) => gst-plugins-base1.0
(Ubuntu)

** Also affects: gst-plugins-base1.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Intermittent very low fps(sometimes zero) with few specific h264 and
  h265 RTSP input streams sources when used with gst-v4l2 based
  gstreamer-1.0(version gst-1.14.5) decode pipeline

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions


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

[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline

[Loïc Minier]

Hi Kunal,

thanks for your report; I looked at the upstream bug, and I didn't find
a reproducer to confirm the bug and its resolution with the patch; would
you have one?

This might be a candidate for a SRU update; the process is outlined in
https://wiki.ubuntu.com/StableReleaseUpdates and is largely about
assessing risk of regressions.


** Bug watch added: bugzilla.gnome.org/ #796771
   https://bugzilla.gnome.org/show_bug.cgi?id=796771

** Also affects: gstreamer1.0 via
   https://bugzilla.gnome.org/show_bug.cgi?id=796771
   Importance: Unknown
   Status: Unknown

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

Title:
  Intermittent very low fps(sometimes zero) with few specific h264 and
  h265 RTSP input streams sources when used with gst-v4l2 based
  gstreamer-1.0(version gst-1.14.5) decode pipeline

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions


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

[Bug 1931278] Re: Creating FIT images is not supported

[Loïc Minier]

thanks for the patch!

this might be easier to review as smaller atomic changes, but perhaps I
can still follow around the debdiff :)

1) The its files are data, so they should to /usr/share; I wouldn't
encourage local customizations by dropping them in /etc unless that's an
important function; a way to give control would be to install a local
flash-kernel database entry that overrides the shipped defaults for that
hardware; this should be possible with /etc/flash-kernel/db?

2) would you add the new Boot-FIT-Path and Boot-ITS-Path to README?

3) seems "Boot-ITS-Path: /.../foo.its" should be written "U-Boot-ITS-
Name: foo.its" and should be searched in the default flash-kernel
directory

4) would it be possible to avoid the cp calls for kernel and initrd and
just generate the fit image from their locations? the kernels / initrds
tend to be big, so I suspect this adds non-trivial time to the run on SD
cards

5) mkimage_fit(): why is padding needed? perhaps deserves a comment.
Should this be a config?

6) the full path name in DTB-Id is the first one in the database,
perhaps this suggests the corresponding deb should be in Required-
Packages? would help with d-i usage

6) "cd" looks pretty singular compared to rest of functions; could it be
avoided?

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

Title:
  Creating FIT images is not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions

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

[Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII

[Loïc Minier]

ubuntu-focal.git, focal/raspi2 branch:
debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y

ubuntu-bionic.git, bionic/raspi2 branch:
debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y

So not quite sure where this is coming from

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

Title:
  arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions

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

[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Can confirm 5.4.0-18.22 in proposed fixes iwlwifi for me; thanks!

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

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

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

[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Should also mention I've upgraded all packages to latest in focal
including linux-firmware 1.186.

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

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

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

[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Just to confirm that I still have broken WiFi with linux-
image-5.4.0-14-generic 5.4.0-14.17 (but it works with linux-
image-5.3.0-26-generic 5.3.0-26.28 and worked with iwlwifi backports
when I tried).

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

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

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

[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Dkms module worked with 5.4.0-9-generic and current linux-firmware,
thanks!

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+attachment/5320091/+files/dmesg.txt

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

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

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

[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Tried with:
linux-image-unsigned-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb
linux-modules-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb
(after disabling secure boot)

=> no wifi

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

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

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

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

[Bug 1859287] [NEW] iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Public bug reported:

Hi there,

Laptop: Dell XPS 13 7390 2-in-1
Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz

iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
Firmware crashes after loading and interface doesn't show up.

This is with:
linux-image-5.4.0-9-generic   5.4.0-9.12
linux-firmware 1.184

I've noticed the driver was trying to load a more recent firmware:
Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2

I've downloaded this file from upstream iwlwifi firmware git and tried
unloading/reloading iwlwifi. Driver crashes as well, but with a
different error code.

Best,
- LM

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-9-generic 5.4.0-9.12
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lool   1579 F pulseaudio
 /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 11 15:02:08 2020
InstallationDate: Installed on 2019-12-02 (39 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. XPS 13 7390 2-in-1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic  N/A
 linux-firmware   1.184
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago)
dmi.bios.date: 11/10/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Description changed:

  Hi there,
  
  Laptop: Dell XPS 13 7390 2-in-1
  Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz
  
  iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
  Firmware crashes after loading and interface doesn't show up.
  
  This is with:
  linux-image-5.4.0-9-generic   5.4.0-9.12
  linux-firmware 1.184
  
  I've noticed the driver was trying to load a more recent firmware:
- Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2
+ Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2
  
  I've downloaded this file from upstream iwlwifi firmware git and tried
  unloading/reloading iwlwifi. Driver crashes as well, but with a
  different error code.
  
  Best,
  - LM
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  lool   1579 F pulseaudio
-  /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lool   1579 F pulseaudio
+  /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 15:02:08 2020
  InstallationDate: Installed on 2019-12-02 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-9-generic N/A
-  linux-backports-modules-5.4.0-9-generic  N/A
-  linux-firmware   1.184
+  linux-restricted-modules-5.4.0-9-generic N/A
+  linux-backports-modules-5.4.0-9-generic  N/A
+  linux-firmware   1.184
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft 

[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20 - 5.3

[Loïc Minier]

** Bug watch added: Linux Kernel Bug Tracker #204837
   https://bugzilla.kernel.org/show_bug.cgi?id=204837

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=204837
   Importance: Unknown
   Status: Unknown

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

Title:
  hid-sensor-hub spamming dmesg in 4.20 - 5.3

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

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

[Bug 1851263] Re: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable

[Loïc Minier]

Hi Romain and thanks for your report,

In general, we don't make large upstream updates after release, especially for 
LTS and even more so for a critical piece like glibc. If you've identified the 
single patch that would address your issue, it can be considered for the SRU 
process:
https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable

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

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

[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used

[Loïc Minier]

NB: If you're using an official image and it's missing mkimage, could
you point at the specific image you used?  :-)

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

Title:
  flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no
  uboot is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions

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

[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used

[Loïc Minier]

This is by design, flash-kernel has different dependencies depending on
the target hardware; the piece of software making the system bootable
(e.g. the flash-kernel udeb in d-i/ubiquity) will install flash-kernel
and the hardware-specific deps (such as u-boot-tools).

** Changed in: flash-kernel (Ubuntu)
   Status: New => Invalid

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

Title:
  flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no
  uboot is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions

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

[Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe

[Loïc Minier]

Could you describe the minimal steps to reproduce the issue on top of a
standard 16.04?

NB: /sys is not read-only on official images and deployments, and this
doesn't seem to affect official images.

** Description changed:

  Dear all,
  
- Following up the bug report #1713674, when executing systemd in a
- hardened LXC context, it might not be suitable to reexec systemd daemon,
- that would not be able to perform.
+ Following up the bug #1713674, when executing systemd in a hardened LXC
+ context, it might not be suitable to reexec systemd daemon, that would
+ not be able to perform.
  
  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find its
  cgroups). This means, systemd cannot be reexecuted, it will fail to
  restart and will freeze (properly) at restart making the LXC container
  in frozen state (still working, but no new services startable, no
  interaction with systemd possible anymore).
  
  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in a
  degraded state.
  
  It would likely be appropriate the check whether the reexecute can work
  will before performing it: checking capabilities, sys mount point perms,
  etc. If not applicable, not performing a reexucte and possibly print a
  message to the user.
  
  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.
  
  Cheers

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

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

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

[Bug 1717232] Re: RM: duplicate package

[Loïc Minier]

Seeing source was changed in 2012, I also believe it's long dead; for 
reference, here's the list of targeted platforms:
# configpackage build   install
# targetnametarget  target(s)
#
efikamx efikamx u-boot.imx  u-boot.imx
highbankhighbank-   u-boot.bin
igep0020igep0020-   u-boot.bin
mx51evk mx51evk u-boot.imx  u-boot.imx
mx53ard mx53ard u-boot.imx  u-boot.imx
mx53locomx53locou-boot.imx  u-boot.imx
mx6qarm2mx6qarm2u-boot.imx  u-boot.imx
mx6qsabrelite   mx6qsabrelite   u-boot.imx  u-boot.imx
omap3_overo omap3-overo -   MLO u-boot.img 
u-boot.bin
omap3_beagleomap3-beagle-   MLO u-boot.img 
u-boot.bin
omap4_panda omap4-panda -   MLO u-boot.img 
u-boot.bin
omap4_panda_splusb  omap4-panda-splusb  -   MLO u-boot.img 
u-boot.bin spl/u-boot-spl.bin
omap4_sdp4430   omap4-sdp4430   -   MLO u-boot.img 
u-boot.bin
origen  origen  -   u-boot.bin 
spl/origen-spl.bin
smdk5250smdk5250-   u-boot.bin 
spl/smdk5250-spl.bin
snowballsnowball-   u-boot.bin
vexpress_ca9x4  ca9x4-ct-vxp-   u-boot.bin
vexpress_ca9x4  vexpress-ca9x4  -   u-boot.bin
vexpress_ca5x2  vexpress-ca5x2  -   u-boot.bin

And this is the one from the u-boot package:
# ARCH  subarch platformtarget
# 
armel   -   dockstaru-boot.kwb
armel   -   dreamplug   u-boot.kwb
armel   -   guruplugu-boot.kwb
armel  -   openrd_base u-boot.kwb
armel  -   openrd_client u-boot.kwb
armel  -   openrd_ultimate u-boot.kwb
armel   rpi rpi u-boot.bin
armel   -   sheevaplug  u-boot.kwb
armhf   exynos  arndale u-boot-dtb.bin spl/arndale-spl.bin
armhf   exynos  odroid  u-boot-dtb.bin
armhf   exynos  odroid-xu3  u-boot-dtb.bin
armhf   imx mx53locou-boot.imx
armhf   imx mx6cuboxi   u-boot.img spl/u-boot-spl.bin SPL
armhf   imx nitrogen6q  u-boot.imx
armhf   imx novena  u-boot.img spl/u-boot-spl.bin SPL
armhf   imx udoou-boot.img spl/u-boot-spl.bin SPL
armhf   imx usbarmory   u-boot.imx
armhf   imx wandboard   u-boot.img spl/u-boot-spl.bin SPL
armhf   tegra   jetson-tk1  u-boot-dtb-tegra.bin
armhf   omapam335x_boneblack u-boot.img spl/u-boot-spl.bin MLO
armhf   omapam57xx_evm  u-boot-dtb.img spl/u-boot-spl.bin MLO
armhf   omapdra74_evm   u-boot.img spl/u-boot-spl.bin MLO
armhf   omapigep0020u-boot.img spl/u-boot-spl.bin MLO
armhf   omapnokia_rx51  u-boot.bin
armhf   omapomap3_beagleu-boot.img spl/u-boot-spl.bin MLO
armhf   omapomap4_panda u-boot.img spl/u-boot-spl.bin MLO
armhf   rockchipfirefly-rk3288  u-boot-dtb.img 
spl/u-boot-spl-dtb.bin
armhf   rpi rpi_2   u-boot.bin
armhf   sunxi   A10-OLinuXino-Lime  u-boot-sunxi-with-spl.bin
armhf   sunxi   A10s-OLinuXino-Mu-boot-sunxi-with-spl.bin
armhf   sunxi   A20-Olimex-SOM-EVB  u-boot-sunxi-with-spl.bin
armhf   sunxi   A20-OLinuXino-Lime  u-boot-sunxi-with-spl.bin
armhf   sunxi   A20-OLinuXino-Lime2 u-boot-sunxi-with-spl.bin
armhf  sunxiA20-OLinuXino_MICRO u-boot-sunxi-with-spl.bin
armhf   sunxi   Bananapiu-boot-sunxi-with-spl.bin
armhf   sunxi   Bananapro   u-boot-sunxi-with-spl.bin
armhf   sunxi   Cubieboard  u-boot-sunxi-with-spl.bin
armhf   sunxi   Cubieboard2 u-boot-sunxi-with-spl.bin
armhf   sunxi   Cubietruck  u-boot-sunxi-with-spl.bin
armhf   sunxi   Lamobo_R1   u-boot-sunxi-with-spl.bin
armhf   sunxi   Linksprite_pcDuino  u-boot-sunxi-with-spl.bin
armhf   sunxi   Linksprite_pcDuino3 u-boot-sunxi-with-spl.bin
armhf   sunxi   Mini-X  u-boot-sunxi-with-spl.bin
armhf   sunxi   orangepi_plus   u-boot-sunxi-with-spl.bin
arm64   tegra   p2371-2180  u-boot-dtb.bin
avr32   -   hammerhead  u-boot.img
mips-   qemu_mips   u-boot.bin
sh4 -  

Re: Ubuntu's docker-compose packages are outdated

[Loïc Minier]

Hi there!

On Wed, Jul 5, 2017 at 10:35 PM, Drew DeVault <ddeva...@vistarmedia.com>
wrote:

> Would you consider updating them to 0.13 at least, if not 0.14? I have
> sent a similar email to the maintainer of the original Debian package,
> though the Debian package is more up-to-date than the Ubuntu package.
>

Not sure whether you heard about this, but Docker is now also available as
a snap and directly updated by Docker Inc. This allows for latest CE
releases to make their way to Ubuntu 14.04 (and later) users – and of
course users of other distros, but that's less relevant   :-)

Docker-compose is included and up-to-date in the latest CE snaps  :-)

Best,
- Loïc Minier
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

[Bug 1684521] Re: Ubuntu Core first configuration does not support proxy

[Loïc Minier]

Adding subiquity task as I think this is where console-conf items are
tracked

** Also affects: subiquity (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/1684521

Title:
  Ubuntu Core first configuration does not support proxy

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

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

[Bug 1664368] Re: snap refresh hangs on arm architecture

[Loïc Minier]

This shows RPi kernel for Ubuntu 16.04 versions:
https://launchpad.net/ubuntu/+source/linux-raspi2

Latest in xenial-updates is 4.4.0-1042.49, so you seem to have an older
version.

Could you check that you have xenial-updates in your
/etc/apt/sources.list*?

What's the reported .deb version with dpkg -l linux-image\*|grep ^ii

If you have the latest deb but not the latest kernel installed, this
might indicate a non-working flash-kernel upgrade

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

Title:
  snap refresh hangs on arm architecture

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

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

[Bug 1507505] Re: Unable to install GRUB in /dev/nvme

[Loïc Minier]

Workaround: when installer starts, select manual partitioning and select
/dev/nvme0n1 as the place where to install the bootloader (bottom of the
partitioning window).

(I didn't manage to boot this particular system with UEFI enabled, this
workaround only works in legacy mode for me)

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

Title:
  Unable to install GRUB in /dev/nvme

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub-installer/+bug/1507505/+subscriptions

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

[Bug 1626848] Re: flash-kernel postrm.d script fails on kernel removal

[Loïc Minier]

** Changed in: flash-kernel (Ubuntu)
   Status: New => Invalid

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

Title:
  flash-kernel postrm.d script fails on kernel removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1626848/+subscriptions

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

[Bug 1626848] Re: flash-kernel postrm.d script fails on kernel removal

[Loïc Minier]

The presence of a flash-kernel deb on a system is meant to imply that
kernel installations/removal/upgrades should update the bootloader
state. When using image building tools, flash-kernel's behavior needs to
be entirely disabled, much like daemons shouldn't be started in such a
chroot. To disable flash-kernel's behavior, set FLASH_KERNEL_SKIP=1 in
the environment.

Another approach used commonly by image building tools is to dpkg-divert
binaries (e.g. start-stop-daemon) to avoid services from being started;
a similar approach could be taken to disable flash-kernel.

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

Title:
  flash-kernel postrm.d script fails on kernel removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1626848/+subscriptions

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

[Bug 1551321] Re: Not multiarchified; uses legacy lib32 path

[Loïc Minier]

The issue is that the lib uses the legacy usr/lib32 pathnames which only
work with libc6-i386 installed. The lib would work by default if it was
in the multiarch pathname.

** Summary changed:

- Not multiarchified and no 32-bits version available on 64-bits
+ Not multiarchified; uses legacy lib32 path

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

Title:
  Not multiarchified; uses legacy lib32 path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1551321/+subscriptions

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

[Bug 1551321] Re: Not multiarchified and no 32-bits version available on 64-bits

[Loïc Minier]

Actually the lib is biarch, so it ships a /lib32 variant and ought to
work; not sure what's wrong here.

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

Title:
  Not multiarchified and no 32-bits version available on 64-bits

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1551321/+subscriptions

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

[Bug 1551321] [NEW] Not multiarchified and no 32-bits version available on 64-bits

[Loïc Minier]

Public bug reported:

Hi,

when using libnss-extrausers with 32-bits program doing getpwnam and
such on a 64-bits system, libnss-extrausers is only available for the
current architecture (64-bits) and this results in entries not being
found from the extra users db.

The solution is to install both 32-bits (i386) and 64-bits (amd64)
version of this library package whenever relying on it. However that's
not possible with the current pathnames which arent multiarch friendly.

Cheers,
- Loïc

** Affects: libnss-extrausers (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/1551321

Title:
  Not multiarchified and no 32-bits version available on 64-bits

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1551321/+subscriptions

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

Re: State of systemd-networkd integration for Xenial

[Loïc Minier]

On Mon, Jan 4, 2016 at 8:19 AM, Martin Pitt  wrote:

> networkd is a supported component in Xenial, so you are welcome to use
> it. The server and snappy teams have discussed using it by  default,
> and I'm not entirely sure about the latest word on it, but I believe
> the plan was to stay conservative for 16.04 LTS and keep ifupdown, and
> consider moving to networkd after that. An LTS cycle is not a good
> time to do major changes on the plumbing layer.
>

Yup, that's exactly where we're at!

- LM
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

[Bug 1494719] Re: Support for the RaspberryPi2 platform

[Loïc Minier]

Paolo, see https://wiki.ubuntu.com/ARM/RaspberryPi for the list of PPAs
(stable, staging, nightly)

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

Title:
  Support for the RaspberryPi2 platform

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1494719/+subscriptions

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

[Bug 1494719] Re: Support for the RaspberryPi2 platform

[Loïc Minier]

Hmm two quick things:
- this doesn't seem to match the flash-kernel changes done in the PPA for RPi2 
support which also defines a Kernel-Flavors field in the db (and which is 
missing raspi2, only has rpi2) – not sure that's intentional or not
- do we really want to copy over the DTB from linux? I thought we could only 
use the upstream one?!

Thanks,

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

Title:
  Support for the RaspberryPi2 platform

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1494719/+subscriptions

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

[Bug 1484567] Re: Please add mkenvimage to u-boot-tools

[Loïc Minier]

Hi,

I believe this is already fixed in wily:
https://launchpad.net/ubuntu/+source/u-boot/2015.04+dfsg1-2ubuntu1

Cheers,

** Changed in: u-boot (Ubuntu)
   Status: New = Fix Released

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

Title:
  Please add mkenvimage to u-boot-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1484567/+subscriptions

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

[Bug 1470727] Re: ubuntu-device-flash touch fails with: failed to find user uid/gid

[Loïc Minier]

snappy.install() is failing on generic-amd64: failed to find uid/gid

** Package changed: goget-ubuntu-touch (Ubuntu) = snappy

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

Title:
  ubuntu-device-flash touch fails with: failed to find user uid/gid

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

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

[Bug 1274320] Re: Error: diskfilter writes are not supported

[Loïc Minier]

keeping this as new as to not expire it -- potentially no one has this
issue without LVM/MD, so Mathieu's question might not get an answer but
we still want to fix this

** Changed in: grub2 (Ubuntu)
   Status: Incomplete = New

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

Title:
  Error: diskfilter writes are not supported

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

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

[Bug 1450383] [NEW] doesn't cope with corrupted SSH key files

[Loïc Minier]

Public bug reported:

Hi,

when cloud-init starts on snappy for the first time, it will generate
host SSH keys. If power is removed after this point, fsck might replace
this uncommitted data by zero files, in which case it's impossible to
login to the system.

A workaround would be to flush/sync data to disk after writing the
files, but I guess the root cause fix would be to check on each boot if
the files were successfully written in full or otherwise regenerate
them.

Cheers,

** Affects: cloud-init (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/1450383

Title:
  doesn't cope with corrupted SSH key files

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

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

[Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available

[Loïc Minier]

** Also affects: ubuntu-location-provider-here (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/1415029

Title:
  Not yet available but configured providers should be added as soon as
  they become available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1415029/+subscriptions

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

[Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available

[Loïc Minier]

** Changed in: ubuntu-location-provider-here (Ubuntu)
 Assignee: (unassigned) = Loïc Minier (lool)

** Changed in: ubuntu-location-provider-here (Ubuntu)
   Status: New = In Progress

** Changed in: ubuntu-location-provider-here (Ubuntu)
   Importance: Undecided = High

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

Title:
  Not yet available but configured providers should be added as soon as
  they become available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1415029/+subscriptions

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

[Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Loïc Minier]

** Changed in: location-service
   Status: New = In Progress

** Changed in: location-service (Ubuntu RTM)
   Status: New = In Progress

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

Title:
  dbus daemon spinning with NM AP properties change event

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

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

[Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Loïc Minier]

I've prepared some test binaries with the proposed fix at
http://people.canonical.com/~lool/lp-1394204/

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

Title:
  dbus daemon spinning with NM AP properties change event

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

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

[Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Loïc Minier]

(there are some binaries for rtm in silo 7)

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

Title:
  dbus daemon spinning with NM AP properties change event

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

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

[Bug 1389250] Re: Location updates stop when screen is locked for a bit

[Loïc Minier]

Might be the same bug as https://bugs.launchpad.net/ubuntu/+source
/location-service/+bug/1387643 but  need to debug with Thomas

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

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

Title:
  Location updates stop when screen is locked for a bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389250/+subscriptions

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

[Bug 1328689] Re: ecryptfs-utils does not work with Ubuntu 14.04.1

[Loïc Minier]

** Also affects: ecryptfs-utils (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/1328689

Title:
  ecryptfs-utils does not work with Ubuntu 14.04.1

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

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

[Bug 1389874] Re: Location detection is not working

[Loïc Minier]

** Changed in: location-service (Ubuntu)
   Status: New = Fix Released

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

Title:
  Location detection is not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389874/+subscriptions

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

[Bug 1391863] [NEW] horizontal accuracy meters keeps getting higher

[Loïc Minier]

Public bug reported:

Hi,

in apps and with espoo-cli, I've noticed that the horizontal accuracy
(in meters) keeps climbing; I had seen this on cell in the past, but
it's particularly visible on wifi. Symptom is that your position is very
accurate, but the circle around it is very large, and keeps getting
larger.

I suspect this is due to the timestamps of known wifi / cell getting
older when reported to HERE.

Cheers,

** Affects: location-service (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/1391863

Title:
  horizontal accuracy meters keeps getting higher

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1391863/+subscriptions

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

[Bug 1389874] Re: Location detection is not working

[Loïc Minier]

** Branch linked: lp:~lool/ubuntu-location-provider-here/lp1389874

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

Title:
  Location detection is not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389874/+subscriptions

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

[Bug 1389874] Re: Location detection is not working

[Loïc Minier]

Adding a sleep 15 before slpgwd exec has helped at least Alexander get a
position more reliably.

HERE debug on some affected phones shows a general error being
reported.

I've run a connectivity upstart job with start on started dbus to
start it in similar conditions; it did show a problematic pattern: it
only gets GSM information, and no cell information. As soon as it's
restarted, it correctly gets wifi information too. This might be an
explanation for lack of HERE location.

I'll debug this further, and also try running the HERE debug binaries to
try to find out more about the underlying cause.

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

Title:
  Location detection is not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389874/+subscriptions

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

[Bug 1390490] [NEW] Race between connectivity-api and network-manager

[Loïc Minier]

Public bug reported:

Hi,

https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389874
was a symptom for an issue with connectivity API which doesn't work when
it starts before network-manager is started or when leaving airplane
mode.

To reproduce, create an upstart job like connectivity.conf with:
start on started dbus

console log

respawn
respawn limit unlimited

script
GLOG_logtostderr=1
GLOG_v=200
export GLOG_logtostderr GLOG_v
exec /home/phablet/connectivity
end script

with connectivity from http://people.canonical.com/~lool/connectivity

Then boot with airplane mode enabled, and leave airplane mode: only cell
data is logged, not wifi data.

Cheers,

** Affects: location-service (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/1390490

Title:
  Race between connectivity-api and network-manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1390490/+subscriptions

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

[Bug 1386177] Re: All preinstalled clicks should be moved to custom tarball

[Loïc Minier]

Victor, remove shorts as in remove entirely or just remove from rootfs
and add to custom tarball? (just making sure)

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

Title:
  All preinstalled clicks should be moved to custom tarball

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1386177/+subscriptions

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

[Bug 1389250] [NEW] Location updates stop when screen is locked for a bit

[Loïc Minier]

Public bug reported:

Hi,

1. start one or more location using apps; see that they get location updates as 
you move around
2. lock your screen, wait 30s
3. unlock screen, none of the apps get any location update anymore
4. kill and restart one of the location using apps, all apps now get location 
updates again

Our location-service/platform-api/qt/etc. stack should resume location
updates after locked screen / sleep.

Cheers,

** Affects: location-service (Ubuntu)
 Importance: High
 Status: New

** Changed in: location-service (Ubuntu)
   Importance: Undecided = High

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

Title:
  Location updates stop when screen is locked for a bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389250/+subscriptions

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

[Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Loïc Minier]

To test whether the low-level HERE stack gets a location, put 
http://people.canonical.com/~lool/espoo-cli on your phone (will be included 
along HERE bits in the future) and run with:
chmod a+x espoo-cli
GLOG_logtostderr=1 GLOG_v=100 
LD_LIBRARY_PATH=/custom/vendor/here/location-provider/lib/arm-linux-gnueabihf 
./espoo-cli 5

NB: 5 is the number of location updates after which the tool exits; updates 
should come in at approx 15s interval. Output looks like:
I1101 21:30:01.285964  4403 cli.cpp:117] Requested number of updates is 2
I1101 21:30:01.299002  4403 cli.cpp:133] Starting location updates
I1101 21:30:01.301888  4403 cli.cpp:141] Starting GLib main loop
I1101 21:30:11.304612  4403 cli.cpp:158] Location: tstamp=1414891811 lat=xyz 
long=foo hor. acc.=2569 alt=nan vert. acc.=nan tech=cell
I1101 21:30:11.306061  4403 cli.cpp:170] Remaining updates: 1
I1101 21:30:26.736821  4403 cli.cpp:158] Location: tstamp=1414891826 lat=xyz 
long=foo hor. acc.=2824 alt=nan vert. acc.=nan tech=cell
I1101 21:30:26.738348  4403 cli.cpp:148] Stopping location updates

This worked for me on mako and krillin with respectively latest vivid
and rtm from yesterday (139); however I did manage to get a general
error in one case on krillin, seemingly because I started this when the
device was still booting.

Interestingly, I get tech=cell for krillin and tech=wifi for mako,
despite both being on the same table; this suggests these dont have the
same wifi and/or cell visibility.

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

Title:
  [TOPBLOCKER] Location services not getting location

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Bug 1387708] Re: Location services not getting location

[Loïc Minier]

** Also affects: location-service (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: location-service (Ubuntu)
   Importance: Undecided = Critical

** Changed in: location-service (Ubuntu)
   Status: New = Confirmed

** Also affects: location-service (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: location-service (Ubuntu-rtm 14.09)
   Importance: Undecided
   Status: New

** Changed in: location-service (Ubuntu-rtm 14.09)
   Status: New = Confirmed

** Changed in: location-service (Ubuntu-rtm 14.09)
   Importance: Undecided = Critical

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

Title:
  Location services not getting location

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Bug 1382066] Re: Drop sleep for GPS hardware before launching location-service

[Loïc Minier]

Dropped before landing

** Changed in: location-service (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Drop sleep for GPS hardware before launching location-service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1382066/+subscriptions

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

[Bug 1382066] Re: Drop sleep for GPS hardware before launching location-service

[Loïc Minier]

Dropped before landing

** Changed in: lxc-android-config (Ubuntu)
   Status: New = Fix Released

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

Title:
  Drop sleep for GPS hardware before launching location-service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1382066/+subscriptions

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

[Bug 1383724] Re: In the welcome wizard enable location but not here services and in here maps app you get no location

[Loïc Minier]

Is that still an issue? we've fixed a startup issue in recent images

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

Title:
  In the welcome wizard enable location but not here services and in
  here maps app you get no location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1383724/+subscriptions

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