** Description changed:
Impact:
People are reporting that the green led (the one next to the red power
led) is not working on the RaspberryPi 3B+ board.
After debugging the issue, this is what i found:
- 1) in reality, it's not the green led that is not working, but is the
-
** Changed in: linux-raspi2 (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/1806108
Title:
Ethernet not working on rpi3 b+
To manage notifications about this
Hi Chris!
Thank you for reply. I think we can close this 3D. Graphic card of my
laptop PC died a week after my last update.
Now is repaired (cooling fans too), I've formatted and reinstalled Ubuntu.
Now all goes well.
Thanks.
Paolo
Il giorno ven 21 dic 2018 alle ore 11:41 chris_debian <
1
Hi Chris!
Thank you for reply. I think we can close this 3D. Graphic card of my laptop PC
died a week after my last update.
Now is repaired (cooling fans too), I've formatted and reinstalled Ubuntu. Now
all goes well.
Thanks.
Paolo
--
You received this bug notification because you
** Description changed:
Impact:
People are reporting that the green led (the one next to the red power
led) is not working on the RaspberryPi 3B+ board.
After debugging the issue, this is what i found:
1) in reality, it's not the green led that is not working, but is the
-
** Description changed:
Impact:
People are reporting that the green led (the one next to the red power
led) is not working on the RaspberryPi 3B+ board.
After debugging the issue, this is what i found:
1) in reality, it's not the green led that is not working, but is the
Public bug reported:
Impact:
People are reporting that the green led (the one next to the red power
led) is not working on the RaspberryPi 3B+ board.
After debugging the issue, this is what i found:
1) in reality, it's not the green led that is not working, but is the
power led that "fails":
** Changed in: linux-raspi2 (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/1712598
Title:
Fix OOM errors
To manage notifications about this bug go to:
** Description changed:
+ [Impact]
+
+ Booting this image:
+
+ http://cdimage.ubuntu.com/releases/18.04/beta/ubuntu-18.04-beta-
+ preinstalled-server-arm64+raspi3.img.xz
+
+ on a RaspberryPi 3B+, the ethernet port is not working.
+
+ Moving the EEE enabling into the PHY initialisation
And for the record, the source code for the above kernel is here:
https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=b-raspi2_lp1806108
and this is the actual fix:
Ok, new and final kernel:
http://people.canonical.com/~ppisati/lp1806108/
This the kernel has the hotfix for lp806108, get this tested and if it's
ok, i'll push it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please, test linux-image and linux-modules from
http://people.canonical.com/~ppisati/lp1806108/, after 'dpkg -i' both,
copy vmlinuz and initrd.img from /boot to /boot/firmware.
The image still complains on boot though:
'Failed to connect to https://changelogs.ubuntu.com/meta-release-lts.
Check
Another issue: uboot's 'saveenv' doesn't work - stop at the uboot
prompt, type 'saveenv' and the bootloader will "panic" - so there's no
way to change the bootloader environment.
And a question: why copying vmlinuz and initrd to mmcblk0p1 and then
loading from there, when we can point uboot to
Ok, i can reproduce the issue, and while debugging it i found something
else:
1) flash-kernel is broken
...
ubuntu@ubuntu:~$ sudo dpkg -i
linux-image-4.15.0-1029-raspi2_4.15.0-1029.31~1806108take2_arm64.deb
dpkg: warning: downgrading linux-image-4.15.0-1029-raspi2 from 4.15.0-1029.31
to
ubuntu@raspi64:~$ uname -a
Linux raspi64 4.15.0-1029-raspi2 #31-Ubuntu SMP PREEMPT Sat Nov 17 00:01:10 UTC
2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@raspi64:~$ ifconfig eth0
eth0: flags=4163 mtu 1500
inet 192.168.2.185 netmask 255.255.255.0 broadcast 192.168.2.255
inet6
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797406
Title:
rpi3b+: ethernet not working
To manage notifications about this
Ok so, it's official that with 512MB you have to downgrade the CMA to
128MB:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/xenial/tree/arch/arm/boot/dts/overlays/README?h=raspi2#n1317
so the dtoverlay line should go from:
dtoverlay=vc4-kms-v3d
to:
Here is a pastebin of the above dmesg without the line wrap:
http://paste.ubuntu.com/p/mGfz3St6c9/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805174
Title:
Xenial/raspi2 and RaspberryPi3A+:
** Patch added: "0001-drm-vc4-guard-against-NULL-dsi-pointer.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1805117/+attachment/5216973/+files/0001-drm-vc4-guard-against-NULL-dsi-pointer.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Video is not working on the RaspberryPi3A+, and in dmesg there's this:
ubuntu@raspi3:~$ dmesg | grep cma
[0.00] cma: Region at 0x1000 defined on low/high memory boundary
(0x1c00)
[0.00] cma: Failed to reserve 256 MiB
[0.00] Kernel command
** Summary changed:
- Xenial/raspi and rpi3a+: OOPS during boot
+ Xenial/raspi2 and RaspberryPi3a+: OOPS during boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805117
Title:
Xenial/raspi2 and
Public bug reported:
...
[4.334281] [drm] Initialized drm 1.1.0 20060810
[4.463211] usbcore: registered new interface driver brcmfmac
[4.492438] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[4.492469] vc4_dsi 3f70.dsi: DSI not set up by firmware.
[
** Attachment added: "20181105_151214.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1803122/+attachment/5212257/+files/20181105_151214.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "20181105_151017.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1803122/+attachment/5212256/+files/20181105_151017.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Description:Ubuntu 16.04.5 LTS
Release:16.04
I'm experiencing random dekstop lockup, in particular when maxing out build
jobs.
Sometimes, the desktop freeze for a moment but then it recovers and i was able
to capture some dmesg output (see attached pics).
atch 004).
First the two reverts:
commit 3f25fbb82f00a80e9eb3be0ce60abebfc263c84a
Author: Paolo Pisati
Date: Thu Nov 8 10:35:09 2018 +
Revert "lan78xx: Ignore DT MAC address if already valid"
This reverts commit 17f23a96597810ddd56b0c10584fce77d7c3707f
@alexxcons thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795144
Title:
[xubuntu] thunar is opened when insering usb key even if nautilus is
the preferred file manager
To manage
The bug happens when in the thunar-volman GUI, "Browse removable media
when inserted" is enabled.
Too, on the (applications menu) > Settings Manager > Preferred
Applications > Utilities tab, "File Manager" is set to something other
than Thunar. (I selected Nautilus.)
When a removable volume is
spberry BSP patches that clash with this patch, and then reverting
a SAUCE patch, or in other words, reapply the fix this SAUCE patch was
removing.
First the two reverts:
commit 3f25fbb82f00a80e9eb3be0ce60abebfc263c84a
Author: Paolo Pisati
Date: Thu Nov 8 10:35:09 2018 +
-
** Patch added: "0003-lan78xx-Read-MAC-address-from-DT-if-present.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1802320/+attachment/5210383/+files/0003-lan78xx-Read-MAC-address-from-DT-if-present.patch
--
You received this bug notification because you are a member of
** Patch added: "0002-Revert-lan78xx-Read-MAC-address-from-DT-if-present.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1802320/+attachment/5210382/+files/0002-Revert-lan78xx-Read-MAC-address-from-DT-if-present.patch
--
You received this bug notification because you are a
eam patch from 4.18.y, reverting
two Raspberry BSP patches that clash with this patch, and then reverting
a SAUCE patch, or in other words, reapply the fix this SAUCE patch was
removing.
First the two reverts:
commit 3f25fbb82f00a80e9eb3be0ce60abebfc263c84a
Author: Paolo Pisati
Date: Th
ch, or in other words, reapply the fix this SAUCE patch was
removing.
First the two reverts:
commit 3f25fbb82f00a80e9eb3be0ce60abebfc263c84a
Author: Paolo Pisati
Date: Thu Nov 8 10:35:09 2018 +
Revert "lan78xx: Ignore DT MAC address if already valid"
This reverts commit
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797406
Title:
rpi3b+: ethernet not working
To manage
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797154
Title:
arm64: snapdragon: reduce boot noise
To manage
isn't there an "xfce4-volman" app? That would be the right solution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795144
Title:
[xubuntu] thunar is opened when insering usb key even if nautilus is
Thanks.
Maybe this?
** Attachment added: "ubuntu-xorg.png"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800309/+attachment/5206623/+files/ubuntu-xorg.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
some errors on installing video xorg intel, some corrupted
files/dependencies
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
** Changed in: linux-raspi2 (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux-raspi2 (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783746
Title:
ipmmu is always registered
To manage notifications about this bug go
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
** Patch added: "0001-USB-core-let-USB-device-know-device-node.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1798578/+attachment/5202594/+files/0001-USB-core-let-USB-device-know-device-node.patch
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Invalid
--
You
** Summary changed:
- rpi3b+: can't set mac addrss from device tree
+ RaspberryPi3+: can't set mac address from device tree
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798578
Title:
Public bug reported:
Impact:
The RaspberryPi3+ board came with an usb's to ethernet lan78xx nic
adapter - thhis chip has no external eeprom, nor internal preprogrammed
mac address and as such, after every reboot, it generates a random new
ethernet mac address.
Supposedly, the lan78xx driver is
** Also affects: python3.6 (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/1452115
Title:
Python interpreter binary is not compiled as PIE
To
I do believe pie is explicitly disabled when building Python 3.6. Using
hardening-check on Ubuntu Bionic (from the devscripts package):
$ hardening-check /usr/bin/python3
/usr/bin/python3:
Position Independent Executable: no, normal executable!
Stack protected: yes
Fortify Source functions:
during
upgrades of the Kernel;
I would like to exclude any kind of writing permits to grub2 on the hard
drive MBR; is it possible?
xubuntu 18.04
best regards
Paolo
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Converted to question:
https://answers.launchpad.net/ubu
** Patch added: "0001-lan78xx-Don-t-reset-the-interface-on-open.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1797406/+attachment/5200074/+files/0001-lan78xx-Don-t-reset-the-interface-on-open.patch
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Impact:
Since the release of Ubuntu-raspi2_4.15.0-1022.24, the ethernet port of
the RaspberryPi 3B+ has stopped to work: no phy interrupts are generated
when a cable is inserted, so it's like the ethernet port is always
disconnected.
The problem lies in commit 72eff2505735
I also have the same issue with nautilus in Ubuntu 16.10.
It affects only the list view, grid view works fine.
Also other file browsers like Thunar work fine in both list and grid view.
Additional notes:
- Pressing Ctrl seems to switch off the editing mode.
--
You received this bug
** Description changed:
Impact:
- During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel:
+ During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel,
+ there's some noise like:
...
[3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply
Public bug reported:
Impact:
During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel,
there's some noise like:
...
[3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517
[3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to
init
Ignore the above patch, this is the patch with the correct buglink.
** Patch added:
"0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.patch"
** Patch added:
"0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+attachment/5199517/+files/0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.patch
--
You received this bug notification because you are a
Public bug reported:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
** Patch added:
"0001-arm64-Fix-proc-iomem-for-reserved-but-not-memory-reg.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+attachment/5199511/+files/0001-arm64-Fix-proc-iomem-for-reserved-but-not-memory-reg.patch
--
You received this bug notification because you are a
Public bug reported:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm:
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784025
Title:
Support for the RaspberryPi 3 B Plus board
To manage
We have a kernel dedicated to the RaspberryPi boards (linux-raspi2), why
do you want to use the generic-lpae kernel instead?
Besides, you can't mix dtb and kernels from different arches / branches
- they won't work together.
Someone mentioned that it was able to install the generic arm64 server
Public bug reported:
xubuntu bionic (but it seems to me that xenial had the same issue).
Install nautilus and set as default file manager.
When an usb key is inserted, thunar is used to open it automatically
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
**
I affects me too. Hoping that priority is risen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778069
Title:
[xfce] nautilus don't open files if set as default file manager
To manage
** Description changed:
+ Impact:
+
when using the vc4-kms-v3d devicetree overlay to get accelerated
graphics /dev/fb0 is handled by the vc4 driver.
since this module does not exist in the initrd currently, using the
framebuffer for something like an early splash screen from the
Actually, of the above list, all but one kmod are already included in
the initramfs:
lib/modules/4.4.0-1098-raspi2/kernel/drivers/gpu/drm/drm_kms_helper.ko
lib/modules/4.4.0-1098-raspi2/kernel/drivers/gpu/drm/drm.ko
lib/modules/4.4.0-1098-raspi2/kernel/drivers/gpu/drm/drm_mipi_dsi.ko
And here is a pi2 kernel snap with the above modification applied, can
you test it?
** Attachment added: "pi2-kernel_4.4.0-1098.106_armhf.snap.lp1794279"
Public bug reported:
[Impact]
For raspi2, different target architectures, use diffent image file
format:
$ grep build_image debian.raspi2/rules.d/arm*
debian.raspi2/rules.d/arm64.mk:build_image = Image
debian.raspi2/rules.d/armhf.mk:build_image = zImage
while we always forced a
** Description changed:
+ [Impact]
+
+ The ipmmu-vmsa driver registers itself to the system via an initcall()
+ to ipmmu_init(), and in case it's the first (or the only) iommu driver,
+ it registers its iommu ops to the platform bus - in the tegra2 case,
+ there's no iommu hardware, so all
Public bug reported:
[Impact]
Linux kernel removed the 'firmware_install' step long ago (~4.13), so
invoking it results in a broken kernel snap build:
...
make -j4 CONFIG_PREFIX=/build/pc-kernel/parts/kernel/install modules_install
INSTALL_MOD_PATH=/build/pc-kernel/parts/kernel/install
** Description changed:
[Impact]
- Track: Spectre v4 mitigation (Speculative Store Bypass Disable) support for
arm64 using SMC firmware call to set a hardware chicken bit. Patch now in 4.18
to Bionic.
+ Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64
+ was
what file do you need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787893
Title:
xenial -> bionic upgrade: package python3-aptdaemon.pkcompat prevents
normal ending
To manage notifications
what file precisely?
don Paolo Benvenuto
Il giorno lun 27 ago 2018 alle ore 20:31 Brian Murray ha
scritto:
> Could you provide the screen log which should be in /var/log/dist-
> upgrades? Thanks in advance.
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
>Status: Ne
** Description changed:
- The TANGO platform is enabled by default in the multiplatform ARM
- kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without
- a check whether it actually runs on this hw. This causes an OOPS during
- suspend on my Tegra platform. Please disable this
The patch looks good, but i'll have to wait until it's pulled into Linus
tree.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783746
Title:
ipmmu is always registered
To manage notifications about
Indeed, the platform is not built into the default multi_v7 defconfig,
so that explains why this problem was not found upstream - i think
disabling this ARCH makes sense for generic since it's such a niche
platform.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: "0001-UBUNTU-snapcraft.yaml-fix-kernel-snap-creation.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1788191/+attachment/5178700/+files/0001-UBUNTU-snapcraft.yaml-fix-kernel-snap-creation.patch
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783746
Title:
ipmmu is always registered
To manage notificati
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787945
Title:
Tango platform uses __initcall without furt
Public bug reported:
Impact:
The snapcaft.yaml in the raspi2 branch of the bionic kernel tree is
wrong in many ways:
1) it's referring to generic instead of the raspi2 flavour
2) it's completely missing the firmware files section
3) the target image format is wrong
4) it doesn't build at all
Public bug reported:
I upgraded from xenial to bionic when the system prompted me with the
possibility to do it.
Apparently the upgrade process came to a normal end, but something in
the ui were not ok.
Finally, trying to "apt upgrade", I got a message saying that the
package
Maybe the conflicting package was packagekit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787893
Title:
xenial -> bionic upgrade: package python3-aptdaemon.pkcompat prevents
normal ending
To
Public bug reported:
Impact:
Xenial/snapdragon kernel snap fails to build with latest snapcraft
release (2.42.1):
https://launchpadlibrarian.net/382070508
/buildlog_snap_ubuntu_xenial_arm64_piso-xenial-snapdragon-
dummy_BUILDING.txt.gz
...
Selecting previously unselected package snapcraft.
** Patch added:
"0001-UBUNTU-snapcraft.yaml-convert-prepare-build-and-inst.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1785653/+attachment/5172182/+files/0001-UBUNTU-snapcraft.yaml-convert-prepare-build-and-inst.patch
--
You received this bug notification because
** Patch added:
"0001-UBUNTU-snapcraft.yaml-convert-prepare-build-and-inst.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1785647/+attachment/5172171/+files/0001-UBUNTU-snapcraft.yaml-convert-prepare-build-and-inst.patch
--
You received this bug notification because you
Public bug reported:
Impact:
Xenial/raspi2 kernel snap fails to build with latest snapcraft release
(2.42.1):
https://launchpadlibrarian.net/382070508
/buildlog_snap_ubuntu_xenial_arm64_piso-xenial-snapdragon-
dummy_BUILDING.txt.gz
...
Selecting previously unselected package snapcraft.
** Patch added:
"0001-UBUNTU-snapcraft.yaml-wifi-fw-files-are-now-part-of-.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1785075/+attachment/5170826/+files/0001-UBUNTU-snapcraft.yaml-wifi-fw-files-are-now-part-of-.patch
--
You received this bug notification because you
Public bug reported:
Impact:
the Xenial/raspi2 kernel fails to generate a kernel snap since the wifi
fw files are now part of linux-firmware and were removed from
raspberrypi-wireless-firmware
How test it:
git clone the Xenial tree[1], checkout the raspi2 branch and try to snap
it:
$ git
** Description changed:
Impact:
- The RaspberryPi 3 B Plus is the latest addition in the family of
+ The RaspberryPi 3 B Plus[1] is the latest addition in the family of
RaspberryPi boards, and this patchset includes all the necessary bits
- (dts, lan driver and wifi fixes) to enable this
** Description changed:
Impact:
The RaspberryPi 3 B Plus is the latest addition in the family of
RaspberryPi boards, and this patchset includes all the necessary bits
(dts, lan driver and wifi fixes) to enable this board in our 4.4 Xenial
raspi2 kernel.
How to test:
Build
** Description changed:
Impact:
The RaspberryPi 3 B Plus is the latest addition in the family of
RaspberryPi boards, and this patchset includes all the necessary bits
- (dts, lan driver and wifi fixes - backported from the official
- https://github.com/raspberrypi/linux rpi-4.9.y tree)
** Description changed:
Impact:
- The RaspberryPi 3 B Plus is the latest addition in the Raspberry family
- of boards, and this patchset includes all the necessary bits (dts, lan
- driver and wifi fixes) backported from the official
- https://github.com/raspberrypi/linux rpi-4.9.y tree to
Public bug reported:
Impact:
The RaspberryPi 3 B Plus is the latest addition in the Raspberry family
of boards, and this patchset includes all the necessary bits (dts, lan
driver and wifi fixes) backported from the official
https://github.com/raspberrypi/linux rpi-4.9.y tree to enable that board
** Description changed:
Impact:
The Ubuntu kernel source code depends on the presence of the
retpoline-extract-one file in the script directory during build (see
scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the
debian directory and is copied to scripts during
** Description changed:
Impact:
- On a generic amd64 environment, check out the Xenia/generic or
- Bionic/generic tree, cd into it and execute snapcraft - it should build
- the corresponding kernel snap.
+ The Ubuntu kernel source code depends on the presence of the
+ retpoline-extract-one
** Description changed:
Impact:
The snapcraft.yaml in bionic/master invokes the now obsolete
'firmware_install' target that was removed in
5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel
- firmware"), and by invoking a non existing target, it fails to build.
+
** Description changed:
Impact:
- The snapcraft.yaml in bionic/master still invokes the obsolete
+ The snapcraft.yaml in bionic/master invokes the now obsolete
'firmware_install' target that was removed in
5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel
-
** Patch added:
"0001-UBUNTU-snapcraft.yaml-stop-invoking-the-obsolete-and.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+attachment/5164548/+files/0001-UBUNTU-snapcraft.yaml-stop-invoking-the-obsolete-and.patch
--
You received this bug notification because you are a
Public bug reported:
Impact:
The snapcraft.yaml in bionic/master still invokes the obsolete
'firmware_install' target that was removed in
5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel
firmware"), and by invoking a non existin target, snap build fails.
On a generic amd64
501 - 600 of 4416 matches
Mail list logo
