This also affects the linux-generic-5.15 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085082
Title:
Cannot detect audio sinks and sources in proposed kernel
To manage notifications about t
I haven't heard yet what could have changed, but I think something may have
been fixed regarding this AP in the lab in the last day or two. I was hitting
similar problems on another set of devices with a different kernel now, but I'm
not able to reproduce those anymore. So I decided to go back a
A bug was found and fixed with a recent update to the checkbox test for
this that was causing some formatting problems in the netplan yaml.
While we're waiting for the packages to update, we reran these tests on
rpi400 and cm4l with the previous good version of checkbox and all but
the wpa 802.11n
*** This bug is a duplicate of bug 2062667 ***
https://bugs.launchpad.net/bugs/2062667
** This bug has been marked a duplicate of bug 2062667
Fails on (and should be removed from) raspi desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
I noticed from our automated certification tests on raspberry pi Noble
desktop images that the pd-mapper service was failing on boot. It looks
like this is a package only intended for qualcomm desktop system, and
not something that is needed by raspberry pi.
It looks like thi
Public bug reported:
On the noble server release candidate image testing, I noticed that the
automated wifi tests we run for certification were passing, but they
logged some errors from dmesg related to brcmfmac. The log is filled
with lots of these errors:
kern :err : [Wed Apr 24 11:19:12 202
I confirmed today that r1000 in beta fixes this. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970819
Title:
5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file
intel/ibt
Attaching dmesg-boot.txt
** Attachment added: "dmesg-boot.txt"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1973254/+attachment/5589369/+files/dmesg-boot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
None of our wifi tests seem to be working on one of the amd64 systems we use
for testing full disk encryption. The current kernel snap installed is:
pc-kernel 5.15.0-30.31.1 99122/betacanonical✓ kernel
When looking through the dmesg output, I found
Public bug reported:
When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth
was not working. This NUC has worked for bluetooth tests on uc18, 20, and even
on jammy. However on uc22, we see this in dmesg:
[ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 20
@Alfonso, I tried the image last thursday and it appears to be working
correctly now. I think we can close this. Thanks!
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The current uc22 beta image (2022-04-11) shows nothing on the serial
console during boot, nor does it allow console-conf over serial console.
I've double checked with jammy, focal, and uc20 and my serial console is
working fine with all of those images on this same device (an
Here's the dmesg output
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968617/+attachment/5579456/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
I'm using the jammy beta (20220329) image running on an rpi4 8GB
clicking on the "help" app in the dock launches a window with the title "Ubuntu
Desktop Guide". The icons for forward/back, bookmarks, search, etc. are all
visible at the top of the window, but everything else
screenshot showing the gnome-initial-setup icon
** Attachment added: "Screenshot from 2022-03-30 21-20-51.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967198/+attachment/5574978/+files/Screenshot%20from%202022-03-30%2021-20-51.png
--
You received this bug notifica
Public bug reported:
I noticed this while testing the beta jammy image (20220329) on arm64,
but I checked and I see the same issue on amd64 as well. The best way I
can describe it, is that it looks squished, as if it was sized
incorrectly. I'll attach a screenshot showing the problem also.
Proble
Here's a screenshot showing the drives
** Attachment added: "zfs-dock.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+attachment/5574890/+files/zfs-dock.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I installed the ubuntu 20220329 jammy beta with zfs root selected. After
installation, there are drives on the dock for the zfs bpool and rpool
(and in my case also a "1.6GB Encrypted" device since I also selected
disk encryption at install time). These don't do anything usefu
Public bug reported:
This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred. The session has been up 41 minutes but the files
Marking public since this was from a live session in qemu and did not
yet contain anything I'm concerned about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967150
Title:
gnome-shell crashed with
Here's another one with quiet bootsplash turned off and ignore_loglevel
on
** Attachment added: "serial2.log"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1961871/+attachment/5563115/+files/serial2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Here's the serial log with uart_2ndstage=1 in config.txt
** Attachment added: "serial.log"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1961871/+attachment/5563075/+files/serial.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The devices I have at home all seem to work fine, but I noticed on the
pi-zero-2 we have in the lab that it was working fine with the armhf candidate
image from 20220221 but not with arm64. I was eventually able to get serial
console on it and discovered that the device had
Public bug reported:
One of the tests we run for the network manager snap uncovered this
problem on uc18 with network-manager 1.10 snap, but I've also been able
to reproduce it in the previous snap version, as well as with core20 and
with focal.
On a laptop with intel wifi card, we installed a fr
Public bug reported:
On the image tests we normally do, we have some socketcan tests that
make use of the vcan driver. These have been able to run on Raspberry Pi
in the past, but we are no longer able to run them because of a missing
vcan module on impish.
modprobe: FATAL: Module vcan not found
This appears to be fixed in the current beta kernel for 18-pi -
5.4.0-1042.46~18.04.3 r337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
Title:
Bad Linux ARM64 Image magic
To manage notific
That's the image I'm using, and it's reproducible every single time 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/1934548
Title:
RISC-V: Illegal instruction
To manage notifications about thi
I also noticed just now that this kernel from the 20 track does seem to work
fine on uc20 systems:
pi-kernel5.4.0-1042.46 33120/beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
Public bug reported:
on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot: 0
WARNING at
/build/u-boot
I was also able to reproduce this in bionic on a dawson-j. We don't have
serial console on that device, but I was able to get someone with remote
access to grab a screenshot of the partial crash for me (attached)
** Attachment added: "partial-oops.png"
https://bugs.launchpad.net/ubuntu/+source
I've been trying to gather some more data on this, and here's what I have so
far...
I added a config for eth0 in /etc/systemd/network so that the test (which
replaces eth netplan config with wifi config temporarily) doesn't leave us
without the ability to reconnect.
Testing with dawson-uc18-m7-
I'm seeing something very similar to this with current focal images running on
unmatched (5.8.0-29)
It looks like the image on july 24 worked, but ever since the july 25, 2021
image, it fails to boot
https://pastebin.canonical.com/p/c9czkm9x74/
--
You received this bug notification because you
I don't think that driver matching is still happening. Something else
seems to be responsible for conditionally fixing the name to be eth0
when it's one of those well-known built-in ethernet drivers for rpi.
AIUI, this is done because by convention, people like to take an sd card
and move it from o
No, I think part of the problem is that net.ifnames=0 was dropped. So
it's not simply a matter of configuring eth0 anymore. On built-in eth
interfaces, it does some matching to locate the correct interface and
rename it to eth0 as appropriate, but I think this is because there's
some more predicta
it was still broken in the 20210420 image, I'll check the latest 21.1
image today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911050
Title:
AttributeError: 'array.array' object has no attribute '
This also shows up on raspi server images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911050
Title:
AttributeError: 'array.array' object has no attribute 'tostring'
To manage notifications about
I didn't see the log request here. However this also seems to affect
hirsute. I'm posting the cloud-init collect-logs tarball for hirsute on
rpi3a+. The other thing that changed right before this started
happening, is that net.ifnames=0 is (intentionally) no longer used.
AIUI, the intent on rpi dev
Worked on groovy before the update, but also works after updating to
proposed
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Confirmed bionic boots after the update to proposed on rpi400
** 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/1906552
Current uc20 candidate image has the updated uboot - this boots fine on
both cm4-lite and rpi400
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Tested on focal with rpi400. After updating, I'm now able to boot.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19065
I think this one could be due to the newer u-boot - 2020.10+dfsg-1
It's coming into focal dailies because proposed is enabled there, but I also
tried to boot an rpi400 with bionic on an older uboot, then enable proposed and
*only* update u-boot. After updating, I get this boot loop there too.
--
Public bug reported:
I first noticed this on a focal daily image (http://cdimage.ubuntu.com
/ubuntu-server/focal/daily-preinstalled/20201202/ or the current pending
one should be able to reproduce it). On the rpi400 device, it goes into
a reboot loop. I'm also seeing this behavior with the current
Public bug reported:
The image can be found here: http://cdimage.ubuntu.com/ubuntu-core/20
/dangerous-beta/20201202.1/ubuntu-core-20-armhf+raspi.img.xz
This image seems to be booting fine on other RPI devices, including other RPI4
devices with 4/2/1GB
Also, the arm64 image boots fine on this dev
I also tried this on my pi400 and confirmed I can see and connect to
bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy-
proposed
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug
Public bug reported:
When booting an rpi that does not have built-in ethernet (such as cm3,
rpi3a+, etc) with the release candidate images for groovy, no ethernet
interface is configured after starting when a usb ethernet dongle is
used. The interface is detected, but not configured.
In /etc/net
Public bug reported:
When running 'sudo flash-kernel' on an 8GB rpi4, it fails with the
following error:
ubuntu@ubuntu:~$ sudo flash-kernel
Unsupported platform.
This only seems to happen on the 8GB model, not 2GB, 4GB, etc.
This is reproducible on both the armhf and the arm64 kernel
flash-kern
I retested this in the current 20200928 beta image of uc20 and I was
unable to reproduce it with the latest kernel snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881159
Title:
BUG: soft lockup
The output around the soft lockup messages as well as the situation
looks very different, so I'm reluctant to call it a dup. Unfortunately,
I don't believe there's a way to take a kernel from the ppa and replace
the kernel snap used in core20 with it. AFAIK, the only way to try this
would be to g
This also shows up still in the 18.04.5 candidate server images on
raspberry pi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566468
Title:
systemd-modules-load.service: Failing due to missing modu
Public bug reported:
When testing 20.04.1, I noticed some different behavior on rpi3b+ that I
didn't see on rpi3b or rpi4. I have configured the device with
ethernet, added netplan yaml for my wifi network, and rebooted. So both
eth0 and wlan0 have an ip address.
On all other devices (rpi3b, rpi
Apparently it's not just us, this is an upstream change. Dave Jones
found this: https://www.raspberrypi.org/blog/latest-raspberry-pi-os-
update-may-2020/
To select headphones, the recommended process is now to create a file called
.asoundrc in your home dir with these contents:
defaults.pcm.card
Public bug reported:
Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing
that I can no longer select the audio output device with amixer. This used to
be possible by using:
amixer cset numid=3 2 for HDMI0
amixer cset numid=3 3 for HDMI1
amixer cset numid=3 1 for 3.5mm h
I tested 1.20200601+arm64-0ubuntu2~18.04.1 by booting the image from
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-
preinstalled/pending/ which already has proposed enabled, and it boots
on rpi4-8G as well as my other rpi devices.
--
You received this bug notification because you are a mem
Public bug reported:
The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine
on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does
not boot. After it gets to "Starting kernel..." it just stops. Attempting to
power off/on the device after the fail
Seems to work in the latest images imported from the streams.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874279
Title:
failed
** Description changed:
We have at least two systems in our lab that are seeing this problem. Both of
them are able to boot other images (bionic, etc) just fine, and at least one of
them was definitely booting focal earlier this week from the stream import in
maas. But now, whenever we try to
So is it just a config.txt or cmdline.txt change that is needed to
enable/disable this? I would think that should be simple enough for most
people to turn on or off from whatever we decide the default should be,
provided it's made clear in a release note or something.
--
You received this bug not
I tried this on the edge/dangerous build yesterday, the current beta image from
today (20200521) and also the images from
https://people.canonical.com/~xnox/uc20/ but even with removing the cma line, I
can only get to:
Installing the system, please wait for reboot
[ 936.831387] systemd[1]: Star
Unfortunately, I'm not having a lot of success getting this image
working. I've put the arm64 image on a mmc and removed the cma line in
config.txt so that it *should* boot on rpi3a+, but it's never getting
past the "Installing the system, please wait for reboot" phase.
--
You received this bug n
** Tags added: uc20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878271
Title:
rpi: no uboot or kernel boot mesages on console during boot on core20
To manage notifications about this bug go to:
** Tags removed: core20
** Tags added: uc20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878258
Title:
wifi missing on core20 image with rpi
To manage notifications about this bug go to:
https://
** Tags removed: core20
** Tags added: uc20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ does not boot with core20
To manage notifications about this bug go to:
https://bugs.
Since it behaves very differently from this on a+, I filed a new bug for
the issues with pi2/pi3 here:
https://bugs.launchpad.net/snapd/+bug/1878943
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187843
Something that may be related - I tried booting the armhf image on an rpi2 and
kept having a lot of problems with it. It was just extremely slow, but
eventually booted to console-conf, but didn't see the ethernet adapter. I did
notice a line early in the boot that it failed to allocate cma, so I
When I filed this bug, I didn't recognize at first that it was the issue
with that dtoverlay. I'm testing a lot of different devices to try to
get a good picture of what works and doesn't work, and would rather err
on the side of reporting stuff as soon as possible. I did go back later
to see if re
I hadn't realized it at first, but this is actually similar to something
we've seen in the past. There's some contiguous memory that is allocated
and locked if vc4-fkms-v3d is enabled in the config.txt. This is ok for
platforms with more RAM, but the RPI3A+ is too constrained. Removing
that line wi
I disabled quiet and enabled early printk and was able to get a full
capture of the panic. (see attachment)
** Attachment added: "boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878432/+attachment/5371037/+files/boot.log
--
You received this bug notification because yo
Public bug reported:
MMC: mmc@7e202000: 0, mmcnr@7e30: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment
RPI3a+ on core 20 from
http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the
previous - 20200512.3) are not booting. This is for bo
Public bug reported:
I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu-
core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see
uboot prompt on screen, as well as kernel boot messages - as well as on
serial. I see all of this coming over serial, but nothing on th
Public bug reported:
With the rpi images for core20, no wifi interface is detected. I've
tried this on rpi4 for certain, but I believe it is also happening on
all other rpi devices with wifi.
This can be reproduced on this image, as well as others:
http://cdimage.ubuntu.com/ubuntu-core/20/beta/20
I do still get this warning:
ubuntu@ubuntu:~$ sudo netplan apply
Warning: The unit file, source configuration file or drop-ins of
netplan-wpa-wlan0.service changed on disk. Run
'systemctl daemon-reload' to reload units.
But even after doing a daemon-reload and running netplan-apply, I never
get
Public bug reported:
Summary
===
Problem found when focal-preinstalled-server-armhf 20200423.1 image on RPI4
netplan.io version 0.99-0ubuntu2
When testing wifi, I confirmed it worked and was able to connect to the device
with ethernet unplugged. After doing this, I removed the netplan confi
I'm pretty sure it gets links to the artifacts that it needs via streams
at http://images.maas.io/ephemeral-v3/daily/focal/amd64/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874279
Title:
failed
Screenshot 1 with errors at boot
** Attachment added: "20200422_111045.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358002/+files/20200422_111045.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
We have at least two systems in our lab that are seeing this problem. Both of
them are able to boot other images (bionic, etc) just fine, and at least one of
them was definitely booting focal earlier this week from the stream import in
maas. But now, whenever we try to prov
Screenshot 2 with errors at boot
** Attachment added: "20200422_112031.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358003/+files/20200422_112031.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
I've observed this in both armhf and arm64 on:
19.10.1-server
18.04.4-server
core18
It does not seem to happen on rpi3, only on rpi4.
If you want to use Bluetooth on rpi, one must first run:
$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow
On RPI4, this results in a timeo
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done 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/1861292
Title:
flash-kernel fa
I installed 18.04.3 (both armhf and arm64) on an rpi3b+, enabled
proposed, and did a dist-upgrade to try this fix. The flash-kernel
version it updated to is 3.98ubuntu11~18.04.1.
Both updated successfully, and there was no log written to /tmp/flash-
kernel-no-kernel-error.log
--
You received th
I don't have another usb3 one at the moment, I'll see what I can find.
However, I'm also starting to think it may be RF interference from the
usb3 port and or stick. If I grab the rpi4 near the usb/ethernet block
in the right place, the problem seems to go away a bit. possibly
something similar to
** Description changed:
On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
device to one of the 2x usb3 ports (the ones closest to the ethernet
port), wifi will sudden stop working. If you unplug the usb stick while
running a ping, it will usually start working again al
Public bug reported:
On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
device to one of the 2x usb3 ports (the ones closest to the ethernet
port), wifi will sudden stop working. If you unplug the usb stick while
running a ping, it will usually start working again almost
instan
Public bug reported:
Kernel tested:
Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019
armv7l armv7l armv7l GNU/Linux
I've only been able to reproduce this with the armhf kernel and on the
following devices:
RPI3B+
RPI3B
RPI2
At the moment, it does not appear that arm64
reopening. I know it was automatically marked incomplete but there's no
apport on core18. I believe I've already included the relevant
information but I'm happy to provide more, or even get someone access to
this system.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received
Marking invalid - after further investigation it turned out to be an
ordering problem where some network-manager tests ran before the
netplan tests. Deleting a connection in network-manager doesn't seem to
clean up after the wpa-supplicant sockets that it creates, resulting in
two of them existing
Public bug reported:
I was able to successfully configure wifi with NetworkManager, but if I
try to configure it with netplan it doesn't seem to work.
I've also tested this on rpi3b+ with eoan and it worked fine there.
To test this, I ensured all networkmanager connections for wifi were deleted,
Here's a screenshot from the errors I see on the hdmi console
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848075/+attachment/5297127/+files/IMG_1389.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I've tried with both the 20191010.1 and 20191012 image, and it boots
on all other pi devices I have, but not on the rpi3-a+. On the serial
console, it only gets as far as "Starting kernel..." but over hdmi,
there are some more details reported. I'll try to attach a screensh
Public bug reported:
One of the test systems we use for testing snap updates is:
Dell Inspiron 5759
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916
We picked this one, some time ago from a pool of hardware to use for one
of the test s
Ran tests with this on two different systems, results looked good on both:
12:34:12 job passed : BlueZ-Basic RFCOMM Socket - Success
12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Success
12:34:12 job passed : BlueZ-Basic RFCOMM Socket Client - Write Success
12:34:12 job pas
** 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/1796193
Title:
DistUpgradeViewNonInteractive crashes / requires inte
hah, ok that makes more sense then. Looks like this works, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796193
Title:
DistUpgradeViewNonInteractive crashes / requires interaction
To manag
Ok, yeah I see it running:
/usr/bin/python3 /tmp/ubuntu-release-upgrader-n98wh3a9/bionic --mode=server
--frontend=DistUpgradeViewNonInteractive
and
$ sudo cat /tmp/ubuntu-release-upgrader-n98wh3a9/DistUpgradeVersion.py
VERSION = '18.04.33'
after letting it run a while, I did see it seemed to be
Strange, that link seems to suggest it is in proposed already, but when I try
to run 'do-release-upgrade -p -f DistUpgradeViewNonInteractive', I don't seem
to get that. Do I need to do some other manual step to get it first, or do I
need it from xenial instead since that's where I'm coming from?
>From a xenial system, I tried upgrading to bionic with do-release-
upgrade with -f DistUpgradeViewNonInteractive and *not* setting up the
force-confdef option, and it asks for input
Here's where it got stuck waiting for input:
Configuration file '/etc/ntp.conf'
==> Modified (by you or by a scri
For the xenial->bionic question, I had already implemented the
workaround mentioned here to use Dpkg::Options::="--force-confdef"
across all upgrade tests, which has been working fine. I can remove the
workaround and try it if you are specifically interested in finding out
whether it's necessary on
Public bug reported:
I discovered this when running some tests on a core16 image with various rpi3
devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+.
Kernel version:
Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019
armv7l armv7l armv7l GNU/
Public bug reported:
Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
2019 aarch64 aarch64 aarch64 GNU/Linux
I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the
disco release candidate.
After booting, the load average stays quite high, typically over 4
This passes for me on 4.15.0-46.49 - (rev 82) kernel snap that is
currently in candidate
** 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.
1 - 100 of 2027 matches
Mail list logo
