Merge request for Noble:
https://code.launchpad.net/~xypron/livecd-rootfs/+git/livecd-rootfs/+merge/470012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072956
Title:
[SRU] Build preinstalled
Merge request for Oracular:
https://code.launchpad.net/~xypron/livecd-rootfs/+git/livecd-rootfs/+merge/469845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072956
Title:
[SRU] Build preinstalled
I installed the package on a PIC64GX1000 Curiosity Board running Ubuntu
Noble.
Installation of the package resulted in this message:
Setting up u-boot-pic64gx (2024.06-0ubuntu1~24.04.1) ...
1478+1 records in
1478+1 records out
756824 bytes (757 kB, 739 KiB) copied, 0.199882 s, 3.8 MB/s
U-Boot
** Changed in: 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/2072490
Title:
[needs-packaging] U-Boot for Microchip PIC64GX
To manage notifications about
** Description changed:
[Availability]
- TODO: The package TBDSRC is already in Ubuntu universe.
-
u-boot-pic64gx is available for Oracular in universe.
- TODO: The package TBDSRC build for the architectures it is designed to
- work on.
-
The package is only needed on the riscv64
explained in the MIR report.
TODO: The Package description explains the package well
TODO: Upstream Name is TBD
TODO: Link to upstream project TBD
TODO: TBD (any further background that might be helpful
** Affects: u-boot-pic64gx (Ubuntu)
Importance: Undecided
Assignee: Heinrich Schuchar
Merge request created: https://salsa.debian.org/installer-team/flash-
kernel/-/merge_requests/62
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073835
Title:
Default kernel commandline options on
boot.scr is only relevant when booting via U-Boot. In this case
/boot/firmware/cmdline.txt is not considered.
We still need a place to define the default command line. As you already
described this is /usr/share/flash-kernel/default/flash-kernel when
booting via flash-kernel's boot.scr.
** Summary changed:
- Build preinstalled image for PIC64GX Curiosity Kit
+ [SRU] Build preinstalled image for PIC64GX Curiosity Kit
** Changed in: livecd-rootfs (Ubuntu Oracular)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because
In debian/libllvmX.Y.links.in a line
usr/lib/llvm-@LLVM_VERSION@/lib/libLLVM-@LLVM_VERSION@.so.1
/usr/lib/@DEB_HOST_MULTIARCH@/libLLVM.so.@LLVM_VERSION@.1
seems to be missing.
It was removed in Debian when moving from version 1:18.1.8-2 to
1:18.1.8-3.
--
You received this bug notification
Public bug reported:
In current Oracular file /lib/x86_64-linux-gnu/libLLVM.so.18.1 exists in
package libllvm18.
Many binaries have it as a runtime dependency, e.g. doxygen:
$ ldd /usr/bin/doxygen
libLLVM.so.18.1 => /lib/x86_64-linux-gnu/libLLVM.so.18.1
(0x7a1b1640)
In
Public bug reported:
[ Impact ]
* We want to publish a 24.04.1 preinstalled image for the Microchip PIC64GX
Curiosity Kit.
We need U-Boot to boot the board.
* As upstreaming U-Boot has not been started yet we have created a package
with the vendor U-Boot.
This package will be
I tested flash-kernel 3.107ubuntu9~24.04.1 both on an Icicle Kit and a
PIC64GX 1000 Curiosity kit.
Installing the device specific device-tree worked fine. The correct
device-trees were installed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done
u-boot-pic64gx 2024.06-0ubuntu1~ppa1 is available in ppa:xypron/u-boot-
pic64gx-2024.06 and considers Steve's review remarks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072490
Title:
Public bug reported:
[ Impact ]
* We want to build a preinstalled images for PIC64GX Curiosity Kit for Noble
and Oracular.
These will depend on u-boot-pic64gx and linux-image-pic64gx until
upstreaming is completed.
* These files need to be changed:
live-build/auto/config
https://launchpadlibrarian.net/738964327/buildlog_snap_ubuntu_jammy_riscv64_gnome-42-2204-sdk_BUILDING.txt.gz
shows an error
websocket: close 1006 (abnormal closure): unexpected EOF
This occurred in the build phase while building gtk4.
We know that the network proxy invalidates the access token
File drivers/dma/MCD_tasks.c was dropped in the u-boot source package
due to Debian bug 750912.
See https://lists.gnu.org/archive/html/gnu-linux-
libre/2014-05/msg00014.html.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Steve,
thanks for reviewing.
As mentioned above I have already repackaged as u-boot-
pic64gx_2024.06-0ubuntu0.22.4.1~ppa1 as Microchip created a tag
v2024.06.
v2024.06 is a version number chosen by Microchip which is not related to
the upstream U-Boot version numbering scheme. Actually it
u-boot-pic64gx_2024.06-0ubuntu0.22.4.1~ppa1_all.deb is available in
ppa:xypron/u-boot-pic64gx-2024.06
The orig file was created with from Microchips upstream tag with:
git archive --format=tar --prefix='u-boot-pic64gx-2024.06/' -o
../u-boot-pic64gx_2024.06.orig.tar v2024.06
** Changed in:
Hello Łukasz,
Thanks for reviewing.
Microchip has published https://github.com/pic64gx/pic64gx-uboot, branch
pic64gx.
The last commit 39490770a78d I saw was dated 2024-06-24. By now Microchip has
created a tag v2024.06 for it.
Using the tag seems looks like a better choice.
Best regards
** Changed in: flash-kernel (Ubuntu Oracular)
Importance: Undecided => High
** Changed in: flash-kernel (Ubuntu Noble)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Add the 'Microchip PIC64GX Curiosity Kit' to db/all.db
+
+ [ Impact ]
+
+ * We want to publish a preinstalled server image for the Microchip
+ PIC64GX Curiosity Kit in the 24.04.1 release.
+
+ * flash-kernel is needed for copying the device-tree to the place where
+
** Changed in: flash-kernel (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
** Also affects: flash-kernel (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: flash-kernel (Ubuntu Oracular)
Importance: Undecided
Status: New
** Summary ch
Public bug reported:
Add the 'Microchip PIC64GX Curiosity Kit' to db/all.db
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Assignee: Heinrich Schuchardt (xypron)
Status: New
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Heinrich Schucha
** Changed in: ubuntu
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072490
Title:
[needs-packaging] U-Boot for Microchip PIC6
u-boot-pic64gx - 20240624-0ubuntu1~ppa1 is available in
ppa:xypron/u-boot-pic64gx.
** Summary changed:
- Package U-Boot for Microchip PIC64GX
+ [needs-packaging] U-Boot for Microchip PIC64GX
** Description changed:
We want to support the upcoming Microchip PIC64GX board. Unfortunately
** Changed in: ubuntu
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072490
Title:
Package U-Boot for Microchip PIC64GX
To man
Public bug reported:
We want to support the upcoming Microchip PIC64GX board. Unfortunately
upstreaming of U-Boot has not started yet. Due to the number of
differences between our U-Boot 2024.01 and the vendor U-Boot it not
trivial to add board support to our existing U-Boot. The best interim
Public bug reported:
When running 'snap refresh' I saw this message:
INFO cannot update "cups", will not have required content "foo": snap
has no updates available
I would not expect anything called 'foo' in a stable snap.
$ snap info cups
name: cups
summary: The CUPS Snap - The
For verifications I biited this image on the Nezha D1:
https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/cpc/+build/647731/+files/livecd.ubuntu-
cpc.disk1.img.xz
grub.cfg has this line
linux/boot/vmlinuz-6.8.0-36-generic root=LABEL=cloudimg-rootfs ro
efi=debug earlycon=sbi
I
** Changed in: u-boot (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071846
Title:
U-boot host tools not built with Ubunt
See build in ppa:xypron/u-boot
** Patch added: "u-boot-2024.01+dfsg-1ubuntu5..1ubuntu6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2071846/+attachment/5794456/+files/u-boot-2024.01+dfsg-1ubuntu5..1ubuntu6.debdiff
--
You received this bug notification because you are a
Public bug reported:
U-Boot expects compiler flags for host binaries to be passed via
HOSTCFLAGS but we never fill that variable. This leads for instance to
frame-pointer not being created.
** Affects: u-boot (Ubuntu)
Importance: Undecided
Assignee: Heinrich Schuchardt (xypron
Assignee: Heinrich Schuchardt (xypron)
Status: New
** Tags: foundations-todo
** Tags added: foundations-todo
** Changed in: u-boot (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
** Description changed:
The upcoming version of the HSS firmware the bo
I have installed the packages on a SiFive HiFive Unmatched board running
Jammy. The desktop is usable.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of
We should use
Kernel-Flavors: any
We should further change include_only_flavors() to assume any if no
Kernel-Flavors line is specified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071546
Title:
The problem stems from this line in all.db:
Kernel-Flavors: arm64
Ubuntu does not use a Linux kernel flavor arm64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071546
Title:
flash-kernel cannot
Running flash-kernel manually also hows that the latest kernel version
is not determined correctly:
$ sudo flash-kernel 6.8.0-36-generic
Using DTB: allwinner/sun50i-a64-pine64-lts.dtb
Installing
/lib/firmware/6.8.0-36-generic/device-tree/allwinner/sun50i-a64-pine64-lts.dtb
into
These are device-tree files are available on the system:
/lib/firmware/6.5.0-28-generic/device-tree/allwinner/sun50i-a64-pine64-lts.dtb
/lib/firmware/6.8.0-31-generic/device-tree/allwinner/sun50i-a64-pine64-lts.dtb
/lib/firmware/6.8.0-36-generic/device-tree/allwinner/sun50i-a64-pine64-lts.dtb
--
Public bug reported:
I ran apt-get dist-upgrade on 24.04 on a Pine64 A64 LTS board and saw
the following error:
Setting up linux-image-6.8.0-36-generic (6.8.0-36.36) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-6.8.0-31-generic
I: /boot/initrd.img.old is now a symlink to
Patch sent upstream. Waiting for review.
[PATCH 1/1] mmc: consider cd-gpios in Synopsys DesignWare driver
https://lore.kernel.org/u-boot/20240614142102.123715-1-heinrich.schucha...@canonical.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
of the MMC driver. Other drivers have a
call
gpio_request_by_name(dev, "cd-gpios", 0, >cd_gpio,
GPIOD_IS_IN);
This is missing in drivers/mmc/snps_dw_mmc.c.
** Affects: u-boot (Ubuntu)
Importance: Low
Assignee: Heinrich Schuchardt (xypron)
Status: Confirmed
** Tags
)
Importance: Undecided
Assignee: Heinrich Schuchardt (xypron)
Status: New
** Tags: foundations-todo
** Tags added: foundations-todo
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because
I am not able to reproduce the problem on Oracular with autopkgtest
5.34ubuntu2. So let us close it as invalid.
** Attachment removed: "autopkgtest.log.txt"
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2064584/+attachment/5789026/+files/autopkgtest.log.txt
** Changed in:
Public bug reported:
autopkgtest-build-lxd fails if an image already exists with an error
like
Error: Aliases already exists: autopkgtest/ubuntu/noble/amd64
*after* creating the new image which takes a considerable amount of
time.
This is wasting user time. It would be preferable to have
In salsa.debian.org the problem is already fixed:
tools/autopkgtest-build-lxd:256:
if [ "$COMMAND" = incus ] || dpkg --compare-versions "$(lxc version | awk
'/Client version:/{print$3}')" ge 5.14; then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2069274/+attachment/5789035/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2069274/+attachment/5789036/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069274
Today's error when running 'autopkgtest-build-lxd ubuntu-
daily:noble/amd64' is unrelated but need to be fixed before further
investigation.
Setting up linux-headers-generic (6.8.0-35.35) ...
dpkg: error: --compare-versions takes three arguments:
** Attachment added: "autopkgtest.log.txt"
Public bug reported:
I used autopkgtest 5.34ubuntu2 on Oracular
sh -x /usr/bin/autopkgtest-build-lxd ubuntu-daily:noble/amd64
It fails with
+ REUSE=
+ [ lxc = incus ]
+ lxc version
+ sed -ne s/Client version: // p
+ dpkg --compare-versions 5.21.1 LTS ge 5.14
dpkg: error: --compare-versions
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2069274/+attachment/5789034/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: hart-software-services (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069028
Title:
Package current upstr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068600
Title:
Rebuild with current OpenSBI
To manage notifications about this bug go to:
hart-software-services_2024.02.1-0ubuntu1~ppa1 is available in
ppa:xypron/hart-software-services.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069028
Title:
Package current upstream (v2024.02.1)
** Patch added:
"hart-software-services-2022.10-0ubuntu4..2024.02.1-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hart-software-services/+bug/2069028/+attachment/5788346/+files/hart-software-services-2022.10-0ubuntu4..2024.02.1-0ubuntu1.debdiff
--
You received this bug
** Changed in: hart-software-services (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069028
Title:
Package current upstr
Public bug reported:
v2024.01.1 is the newest release of hart-software-services.
We only package the hart payload generator. Here most changes are purely
cosmetic.
The only change to logic is:
fix(hss-payload-generator): use ELF entry address
When including an ELF file into a
Here is the merge request for 24.04 (Noble):
https://code.launchpad.net/~xypron/livecd-rootfs/+git/livecd-rootfs/+merge/467109
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
[ Impact ]
On RISC-V boards we have specified 'earlycon' on the command line to
provide early kernel log output. This does not work with current
kernels.
We have to specify 'earlycon=sbi' to use the kernel driver for the SBI
debug console extension which is available since
u-boot-nezha - 2024.01~rc1-190-g2e89b706f5-0ubuntu3 is available in
ppa:xypron/u-boot-nezha
** Changed in: u-boot-nezha (Ubuntu Oracular)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Summary changed:
- [SRU] Rebuild with current OpenSBI
+ Rebuild with current OpenSBI
** Patch added:
"u-boot-nezha_2024.01~rc1-190-g2e89b706f5-0ubuntu2_2024.01~rc1-190-g2e89b706f5-0ubuntu3.diff"
** Description changed:
[ Impact ]
OpenSBI 1.4 is already available in Oracular and Noble but u-boot-nezha
still uses OpenSBI 1.3.
+
+ The current FTBFS can be fixed by replacing the python3-distutils build
+ dependency by python3-setuptools.
[ Test Plan ]
Install our
** Description changed:
[ Impact ]
- The current upstream kernel fails to boot on the Nezha D1 with OpenSBI
- 1.3. OpenSBI 1.4 fixes the issue.
-
- OpenSBI 1.4 is already available in Oracular and Noble. Jammy is still
- on 1.3.
+ OpenSBI 1.4 is already available in Oracular and Noble but
** Tags added: foundations-todo
** Description changed:
[ Impact ]
The current upstream kernel fails to boot on the Nezha D1 with OpenSBI
1.3. OpenSBI 1.4 fixes the issue.
OpenSBI 1.4 is already available in Oracular and Noble. Jammy is still
on 1.3.
[ Test Plan ]
-
** Tags added: fr-7904
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068600
Title:
[SRU] Rebuild with current OpenSBI
To manage notifications about this bug go to:
package was already build with OpenSBI 1.4 and worked
fine on all supported RISC-V boards.
A defective OpenSBI may lead to boot failure or failure to reboot.
[ Other Info ]
n.a.
** Affects: u-boot-nezha (Ubuntu)
Importance: Undecided
Assignee: Heinrich Schuchardt (xypron)
Status
EDK II and SCT for riscv64 build just fine without creating a stubs-
lp64.h symlink.
See
https://github.com/xypron/sct_release_test/blob/main/build_sct_riscv64/Dockerfile
Best regards
Heinrich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On 6/4/24 16:44, Paride Legovini wrote:
> I still can't reproduce this, we'll need some more information to help
> figuring out what's happening. Can you please:
>
> 1. git clone https://salsa.debian.org/ci-team/autopkgtest/, or `git pull` if
> you have it already to make sure it's up to date.
>
$ lxc version get
Client version: 5.21.1 LTS
Server version: unreachable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064584
Title:
Timed out waiting for container to boot
To manage
The following commands don't show any error:
lxc launch ubuntu-daily:noble/amd64 foo
lxc exec foo true
$ lxc list --all-projects
+-+--+-+--+--+---+---+
| PROJECT | NAME | STATE | IPV4 | IPV6 | TYPE| SNAPSHOTS |
This is still what I see on an amd64 noble system:
$ autopkgtest-build-lxd ubuntu-daily:noble/amd64
Creating autopkgtest-prepare-i7N
Starting autopkgtest-prepare-i7N
Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null.
Issuing reboot (current boot id:
** Attachment added: "installer-log.tgz"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2066886/+attachment/5781822/+files/installer-log.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When installing a virtual machine with the live-installer it created
/etc/netplan/50-cloud-init.yaml with
network:
ethernets:
enp0s6:
dhcp4: true
version: 2
When I rebooted I had a device enp0s4 and no network.
Wouldn't it be preferable to write
** Changed in: tlog (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059028
Title:
proposed-migration for tlog 14-1bui
Upstream bug created:
LONG_MAX is not the maximum value of 64-bit time_t on 32 bit systems (e.g.
ARMv7)
https://github.com/Scribery/tlog/issues/369
** Bug watch added: github.com/Scribery/tlog/issues #369
https://github.com/Scribery/tlog/issues/369
--
You received this bug notification
** Changed in: tlog (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059028
Title:
proposed-migration for tlog 14-1bui
>> The instructions are for applying when cups-browsed is running and
stuck, not after killing it.
I did not kill any process before attaching gdb.
And top shows 200 % cpu usage by cupsd.
This is what still needs to be solved.
--
You received this bug notification because you are a member of
@Till
There are two processes running:
$ ps aux | grep cups-browsed | grep -v grep
root2912 0.0 0.0 2892 1708 ?Ss 10:13 0:00 /bin/sh
/snap/cups/1047/scripts/run-cups-browsed
root3407 0.0 0.0 2892 892 ?S10:13 0:00 /bin/sh
>> Do you know how to quickly trigger the bug?
Till, unfortunately I would not know how to trigger it on purpose.
Concerning SRU of any fix, I think it would be enough to verify that
printing still works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As the package linux-image-laptop-23.10 deleted in Noble was produced by
linux-meta and linux-meta-laptop this seems to be kernel team issue. So
let us keep it in status new.
** Changed in: linux (Ubuntu Noble)
Status: Invalid => New
** Changed in: linux (Ubuntu)
Status: Invalid =>
$ sudo lxc version get
Client version: 5.21.1 LTS
Server version: unreachable
** Changed in: autopkgtest (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A similar problems occurs with autopkgtest running in QEMU:
autopkgtest -U --apt-pocket=proposed -s *.dsc -- qemu autopkgtest-noble-
amd64.img
autopkgtest [11:28:01]: rebooting testbed after setup commands that affected
boot
autopkgtest [11:28:19]: testbed running kernel: Linux 6.8.0-31-generic
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2064584/+attachment/5774018/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2064584/+attachment/5774020/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064584
Public bug reported:
autopkgtest-build-lxd fails to setup a container on Ubuntu 24.04 amd64:
$ autopkgtest-build-lxd ubuntu-daily:noble/amd64
Creating autopkgtest-prepare-61J
Starting autopkgtest-prepare-61J
Created symlink /etc/systemd/system/serial-getty@getty.service → /dev/null.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2064584/+attachment/5774019/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With ubuntu-x13s-settings installed I can boot into kernel
6.8.0-31-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060868
Title:
Lenovo X13s fails to boot on 6.8.0-20-generic and
I would suggest not to invest in enabling a new feature in Focal now
that we have two newer LTS releases. Setting to won't fix.
** Changed in: zfs-linux (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@glathe
We used to have packate linux-image-laptop-23.10 which provided file
/usr/share/initramfs-tools/modules.d/laptop. This contained
qcom_q6v5_pas. It have recreated this file manually but this does not
resolve my problems.
Which follow up package provided with the X13s installer image
On my LicheeRV Dock it dos not work for me with HDMI plugged in at
start. I just get
[ 67.521944] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[ 67.613930] sun4i-drm display-engine: Couldn't bind all pipelines components
and no output. On the Nezha D1 I did not have this issue.
Public bug reported:
On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.
The desktop does not show up though gdm3 is running.
I see the following error messages which might indicate a dependency
issue:
pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote
When connected before boot the HDMI output works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063309
Title:
RISC-V: nouveau :05:00.0: timer: stalled at
To manage
Public bug reported:
After connecting a monitor to an SiFive HiFive Unmatched board running
kernel 6.8.0-28-generic I saw:
nouveau :05:00.0: timer: stalled at
nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package:
With 6.8.0-31-generic I am not able to get any HDMI output on the Nezha D1
either.
Unplugging and reconnecting did not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038933
Title:
The problem did not occur on every boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063300
Title:
On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
detected
To manage
Public bug reported:
A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
after reconnecting the USB Hub. It should have been detected while
booting.
$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
|__ Port 001: Dev 008, If 0,
With 6.8.0-31-generic I am not able to get any HDMI output on the LicheeRV Dock.
Unplugging and reconnecting did not help.
[0.133313] platform 546.tcon-top: Fixed dependency cycle(s) with
/soc/hdmi@550
[0.141438] platform 546.tcon-top: Fixed dependency cycle(s) with
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+attachment/5768195/+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/2062548
Public bug reported:
On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:
[ +0.000917] [drm] Display Core failed to initialize with v3.2.266!
[ +0.24] Unable to handle kernel access to user memory without uaccess
routines at virtual address 0008
A Radeon R230
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/cd-boot-
images-riscv64/+git/cd-boot-images-riscv64/+merge/464607
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062166
Title:
1 - 100 of 676 matches
Mail list logo
