I understand the logic of the of doing this and don't disagree.
However, as this is an entry level device and I believe the only true
64bit O/S advertised for this device, the fact that it does not not
work out of the box may impact on the perception of potential new
Ubuntu users?
Reading Tony's p
Test case works perfectly on the Pi400.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
To manage notifications about this bug go to:
https
Thanks guys for all the work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
To manage notifications about this bug go to:
https://bugs.la
Is this the same as: #1903286?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
Bluetooth won't activate on the pi 400
To manage notifications about this bug go to:
https://bugs.launchp
I can confirm all of the above. Also looking at the Pi OS the in which
the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the
soft block has no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Sorry If I am wasting people time but I have just been reading bug
#1886154 This is the same issue I had when I started to install a
package (libdvd-pkg) and was only resolved when I followed the
instructions above. Could it be that they are connected?
--
You received this bug notification becaus
Exactly the same thing happened to me and I have no idea how or why the
bpool had been exported.
The one thing I would add to Corey's work around, which worked perfectly
is that the $MYDRIVEID I used was the UUID of the bpool partition (best
found in disks), unless that was just my issue? Thanks C
One additional point I had not enabled focal-proposed and have just
checked it is still not enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885234
Title:
package zsys 0.4.6 failed to install
This is a really annoying bug to have in an LTS. I can confirm that if
you install it from the command line with apt-get it fails to get the
correct upload speed only displaying approx 20% of the correct upload
speed. Installing the Python version via pip works but is not ideal.
--
You received t
Public bug reported:
Following upgrades to OTA 12 the location failed to work on the BQ 4.5
and the Finger print option was missing from the setting menu on the Pro
5. A further reboot of both fixed the problems. I therefore assume that
the upgrade process is not initialising some programs correct
Ok after Marks comment I tried again but without any luck. However I
also have a Pro 5 and the finger print function did not work (was not in
the menu). I rebooted and it appeared so In did the same with the E4.5
and the new location icon started to change colour and within a few
minutes it was all
Confirm Tony's post above BQ 4.5 location still not working. On my pro 5
as soon as the phone is unlocked the new location icon is coloured in
and location is possible. The BQ does not colour in at all and nearby
says please enable location service even when scope pulled down to
refresh. (Both on O
12 matches
Mail list logo
