Public bug reported:
repeated crashes when encoding to dvd
** Affects: mplayer (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
--crashed during encoding
https://launchpad.net/bugs/59961
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi
I was able to rip to avi if I use copy as the audio setting.
mplayer still crashes though ( on teh same avi)
There was a clue - escapes at the moment - I'll let you know if I can
get it right
On Tue, 2006-09-12 at 16:59 +, cleentrax wrote:
I am getting crashes every time as well.
It
I'm similarly affected, on a fresh install of 11.10 using the alternate
cd (which has been successfully used to install on another machine) at
boot up I get the same error message.
The machine has various drives:-
1) Sata 80Gb, partitioned as 25Gb ext4 /home, 4Gb swap, balance as ext4 /home
2)
Public bug reported:
Having removed Empathy from my machine, I am still presented with the
status options in the messaging menu - these are all greyed out, and
therefore useless.
They should be removed in the same way that Ubuntu one, Thunderbird, etc
are.
** Affects: indicator-messages
The last 6 lines of mine were at the top, however, commenting out
OnlyShowIn=GNOME;Unity;
And it's all good. Thanks Doug!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881235
Title:
Nautilus
I get the same problem with a HP G72 laptop, Intel HD graphics.
Screen brightness is set to minimum at boot regardless of mains/battery
power.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873731
I've just test this can confirm the bug, same could not connect to
server message after about a minute of attempting to connect.
--
Totem BBC plugin cannot connect
https://bugs.launchpad.net/bugs/528728
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What has been brought up by VinDSL on ubuntuforums is the diff between
/sbin/alsa-utils in lucid and maverick which is this line (385
mute_and_zero_levels $TARGET_CARD || EXITSTATUS=1
Removing the line or changing the 1 to 0 seems to resolve the sound at
boot issue and allow use of alsamixer
Yes, has just happened to me - fully updated 14.04 this morning.
In my case it was an active Citrix remote session that was left
capturing the keyboard when the screen locked itself- the lock screen
could be clicked with the mouse, but the keyboard was typing into my
Citrix session (so my
I think Christopher is onto something... I have Unity on both monitors -
the left (Primary) monitor opens the applications multiple times,
without issues. However, the right hand (secondary) display only opens
an application once, as detailed above.
--
You received this bug notification because
*** This bug is a duplicate of bug 1303325 ***
https://bugs.launchpad.net/bugs/1303325
I also get the same behaviour from a clean install.
** This bug has been marked a duplicate of bug 1303325
clicking on its launcher icon doesn't open it (occured after closing app
before)
--
You
Public bug reported:
After updates on 25/11/14, reboot the following day reported this bug
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules:
I also see this with a fresh install of Ubuntu 15.04 on my netbook
(Toshiba NB550D). Installation was a straight-forward use whole disk
for Ubuntu, and encrypt everything. On boot, screen goes black.
Entering the encryption password blind continues the boot successfully
(login screen appears and
Also encountered this when upgrading a server from 12.04 to 14.04 (for
reference, wound up filing duplicate bug #1579566). Managed to get slapd
restored happily by creating the accesslog directory (then slapadd to
restore).
Unfortunately as I restored the database, rather than apt handling it,
Ah, no worries - finally figured it out. Needed to apply the patch to
/var/lib/dpkg/info/slapd.postinst (rather than slapd.config - was
confused over package's half-configured state) and restore the old-
version backup prior to retrying "dpkg --configure -a". All good now!
--
You received this
Public bug reported:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this
** Attachment added: "apt log from server upgrade"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+attachment/4658826/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a bit of playing around, it appears the root cause was that I'm
using the accesslog overlay which necessitates having another database
under /var/lib/ldap/accesslog. The migration process backed up
everything under /var/lib/ldap to /var/backups then re-created
/var/lib/ldap - but didn't
I should add: I think the accesslog overlay is implicit in replicated
setups (yes, I know, weird enough that a home server's using LDAP, but
replication too?! I originally set it up to learn about LDAP replication
in order to use it at work :). It seems to be used to ease the burden of
change
*** This bug is a duplicate of bug 1003854 ***
https://bugs.launchpad.net/bugs/1003854
Ah, you're absolutely right - that looks like it. Sorry for the
duplicate (don't know why I didn't find that report first)!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that the stick edges toggle on/off made no difference to
on my upgraded 15.10 to 16.04 system.
Sticky edges were off in 15.10 and changing to on/off now in 16.04
doesn't affect the behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My backup was indeed slapcat / slapadd (for both the main directory and
the cn=config stuff). I'd *guess* that if the package state is "ii" you
may not need the patch (incidentally the patch is in bug description at
the top), particularly if the server's starting fine and everything
queries
Hi Andre - I did take a backup of the LDAP directory prior to "do-
release-upgrade" (actually I had nightly backups running so I just
grabbed a copy of the last one of those). That's what I was referring to
when I stated "restore the old-version backup...". It's been a few
months now but I vaguely
Public bug reported:
Attempted installation of Ubuntu 16.04.3 on an Acer Travelmate Spin B1.
It appears to hang during installation of the grub package (it's
difficult to tell due to the lack of a storage indicator light on the
laptop, but after waiting quarter of an hour with no change in the
Fix pushed as PR #47 (https://github.com/CanonicalLtd/landscape-
client/pull/47)
** Changed in: landscape-client
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client
Status: New => In Progress
--
You received this bug notification because you are a
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I suspect this is due to the unusual "simfs" file-system not being in
landscape's whitelist of file-systems that are "safe" to probe. I'll
take a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
approach to me, and hence is what is in the PR
(https://github.com/CanonicalLtd/landscape-client/pull/55).
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
--
You re
Seems like there's two issues here which I'll address in separate PRs to
the landscape-client:
First is the issue that the landscape-client fails to report the
completion (or failure) of the release upgrade process. This turns out
to be due to a delayed import in the version of twisted
> /sbin/shutdown, post upgrade not working, imho is a severe bug
I suspect no-one's bothered to report it because as soon as the machine
is (somehow) rebooted, the issue goes away (and reproduction then
involves the pain of going through a trusty install + xenial upgrade
cycle). Still, I'm not
Had these exact symptoms (lockup, not even sysrq working) on Ubuntu
16.04 with kernel 4.4.0-116 and 4.13.0-37 (booting to the "prior stable"
kernel in each case, 4.4.0-112 and 4.13.0-36, worked successfully).
There's quite a lot in the changelog
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PR for fix: https://github.com/CanonicalLtd/landscape-client/pull/58
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799843
Title:
Failed to register device: landscape.client.broker.registr
** Changed in: landscape-client (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/1799843
Title:
Failed to register device:
** Changed in: landscape-client (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/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable
@xnox Scheduling with /sbin/shutdown normally does work ... however,
what we're dealing with here is the anomalous situation of an instance
which starts off as trusty and is upgraded to xenial. During the upgrade
process, the /sbin/shutdown implementation is changed from the upstart
one to the
Public bug reported:
The json-schema-validator tests break under Python 2, when used with
simplejson 3.16.0. They will also break if/when attempted under Python
3.
The underlying simplejson library subtly changes behaviour from 3.15.0
to 3.16.0. Under Python 2, with simplejson 3.15.0, passing a
Public bug reported:
The ruby-albino package depends on the /usr/bin/pygmentize binary.
Historically this has been provided by the python-pygments package, but
as of disco looks as if it will be in the python3-pygments package.
Fixed package available from
Already taken care of by another upstream submission
** Changed in: ruby-albino (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/1812199
Title:
Ruby albino
This turned out to be a mis-aligned access in the _sha3 module. There's
a NO_MISALIGNED_ACCESSES define that can be used on the relevant
platform (armhf) to fix it. Fixed package uploaded to
https://launchpad.net/~waveform/+archive/ubuntu/pkg
--
You received this bug notification because you are
** Changed in: python3.7 (Ubuntu Disco)
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/1821869
Title:
bus error in test_gil test on armhf with 64bit kernel
To
Verification done for bionic on a Raspberry Pi Compute Module 3 with USB
wifi adapter:
ubuntu@ubuntu:~$ dpkg -l netplan.io | grep ^ii
ii netplan.io 0.96-0ubuntu0.18.04.2 arm64YAML network
configuration abstraction for various backends
ubuntu@ubuntu:~$ ip addr
1: lo: mtu 65536 qdisc
Verification done for bionic on a Pi 3B with both arm64 and armhf
images; no issues encountered.
** 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.
** Description changed:
- The current release of RPi.GPIO (0.63) expects to find hardware revision
- information under /proc/cpuinfo. This exists under armhf kernels, but
- not under arm64 kernels. By contrast, both kernels now provide revision
- information under
SRU: debdiff from current bionic (0.6.3-1ubuntu5) to disco
(0.6.5-1ubuntu1) attached.
** Patch added: "debdiff from rpi.gpio 0.6.3"
https://bugs.launchpad.net/ubuntu/+source/rpi.gpio/+bug/1814118/+attachment/5246208/+files/rpi.gpio_0.6.5.patch
--
You received this bug notification because
Bionic verification done with u-boot-tools
2018.07~rc3+dfsg1-0ubuntu2~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814930
Title:
u-boot-tools missing binutils dependency
To manage
Public bug reported:
The u-boot-tools package, specifically the mkknlimg script within it,
relies upon several external utilities (specifically perl, grep, tr, and
strings). Whilst most are provided by "essential" packages, strings is
provided by binutils which is not. On a fresh install of the
Public bug reported:
flash-kernel is missing db entries for the Raspberry Pi Compute Module 3
and 3+ (which use a separate .dtb to the regular Pi 3B and 3B+). Updated
package uploaded to https://launchpad.net/~waveform/+archive/ubuntu/pkg
** Affects: flash-kernel (Ubuntu)
Importance:
Public bug reported:
The current release of RPi.GPIO (0.63) expects to find hardware revision
information under /proc/cpuinfo. This exists under armhf kernels, but
not under arm64 kernels. By contrast, both kernels now provide revision
information under /proc/device-tree/system/linux,revision.
A
Public bug reported:
On the Raspberry Pi platform, the wiringpi package provides (yet
another, but still a very popular) interface to drive the GPIO pins for
a variety of functions (straight input and output, SPI, I2C, etc). It
also provides the exceedingly useful "gpio" command line utility
) => Dave Jones (waveform)
** Changed in: 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/1824370
Title:
[needs-packaging] wiringpi
To manage notific
For anyone else that encounters this, running "cancel -x -a" to delete
everything from the queue (including historical control files) seems to
have cured the problem. Sorry for not keeping the evidence around, but
I'm afraid after it generated 70Mb of logs in two days I needed to fix
it :)
--
I've put together an update for flash-kernel that handles booting an
uncompressed image (to support existing arm64 installs), a self-
compressed image (to support existing armhf installs), and a gzip'd
image (to support the proposed format). It assumes the kernel is called
"vmlinuz" in all cases
368844
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808056
Title:
vmlinuz is very large in arm64 -raspi2
Public bug reported:
Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last
night the CUPS logs have had a considerable number of messages from
cupsd stating "Removing document files" - about 3 or 4 a second
constantly. Stopping the cups service stops the log-spam, and starting
it
Sorry, we'll be sticking with u-boot for the foreseeable future. Partly
this is because it keeps things (somewhat) consistent between the core
and classic images, but also keeps things consistent between RPi and
Ubuntu images for other embedded platforms. Were we to remove u-boot
from the RPi
Public bug reported:
While the current Ubuntu images for the Raspberry Pi boot on the Compute
Module 3, the firmware (start.elf, fixup.dat, etc.) isn't sufficiently
up to date enough to permit booting the newer Compute Module 3+. An
updated firmware (based on the 2019-02-15 release from
It would be nice to start building compressed arm64 kernels for eoan,
but it may have to wait a bit as the core boot-env won't yet handle this
correctly (that doesn't matter for core-16, but core-18 has arm64
images).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Verification done with Pi 3B, 3B+, CM3, and CM3+. All went smoothly.
** 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/1761483
Title:
Firmware needs updating
Tested Oliver's suggestion and indeed it does work if the overlay is
removed but I assume that the overlay is there for a reason.
Furthermore, extracting the psplash binary from the psplash initrd and
running it after boot has concluded (at which point /dev/fb0 exists)
works successfully which
Thanks Paolo - I can confirm the pre-cooked image displays the boot logo
nicely (couldn't test the snap itself, but I suspect that's due to me
lacking the correction snap incantations rather than anything wrong with
it - snap complained about replacing a signed kernel with an unasserted
one).
--
Indeed - I'd rather not remove overlays without being certain we don't
need them. For now though, let's just get the splash screen working
again (as it's a little un-nerving for new users to be presented with a
straight black screen during boot and have no indication anything's
working other than
@p-pisati: that assumes the overlay isn't required by anyone; as ogra
notes above, the overlay is required for mir-kiosk to work. I don't know
how important mir-kiosk is, but it seems it might be fairly relevant to
core [1]. Either way, it seems less risky to me to add modules to initrd
(which
This is now fixed on eoan and disco (which have firmware versions
20190215) and can boot on 3B+ and CM3+. Hopefully Adam won't mind if I
hijack his bug to SRU the changes back to bionic so it can boot on these
too :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
+ [Impact]
+
+ * The bionic release currently cannot boot on certain pi models (3B+, CM3+)
due to outdated firmware.
+ * This is fixed in the disco and eoan releases with firmware revision
20190215, however it would be nice to enable booting on these platforms for the
** Attachment added: "Build log"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1846329/+attachment/5293624/+files/debuild.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846329
Title:
Public bug reported:
Impact
==
The proposed version supports booting Ubuntu on the Raspberry Pi 4, both
by providing a Pi 4 compatible variant of u-boot (which requires the
version bump to 2019.07), and by detecting and (if required) migrating
the boot configuration to support the Pi 4 (by
** Attachment added: "Output from apt upgrade"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1846329/+attachment/5293623/+files/upgrade-output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- Specific to the Raspberry Pi, when flash-kernel is executed to copy
- things to the boot partition, only the dtb of the Pi that it is being
- executed on is copied. In order to support moving the SD card between Pi
- models, flash-kernel needs to copy *all*
Fixed version of flash-kernel available from ppa:waveform/flash-kernel
at:
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel/
Built from branch at (final commit is the version bump; remove this for
proposed commits):
https://code.launchpad.net/~waveform/ubuntu/+source/flash-
** Changed in: flash-kernel (Ubuntu)
Status: New => In Progress
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can confirm that the test kernel from LP: #1848790 comment #11 fixes
boot on 3A+ (remove vc4-fkms-v3d overlay from config.txt too, and boot
operates correctly with framebuffer working). Tested on arm64 3A+ (and
3B, 3B+, 4B); need to test on armhf too.
--
You received this bug notification
I've now tested the armhf and arm64 variants of Hui's test kernel from
comment #11 on the Pi 2, 3, and 4 (several memory variants) and all
seems good so far. Still need to finish testing on the compute modules,
though.
As regards flash-kernel, the relevant tickets for the missing entries
are LP:
Public bug reported:
Specific to the Raspberry Pi, when flash-kernel is executed to copy
things to the boot partition, only the dtb of the Pi that it is being
executed on is copied. In order to support moving the SD card between Pi
models, flash-kernel needs to copy *all* dtbs provided by the
Some additional notes from testing last night (more or less blindly
after a load of googling for dwc_otg errors and mitigations):
* Adding dwc_otg.speed=1 (limiting the driver speed to Full Speed
USB1.1), fixes the mass-storage issue, but breaks compatibility with
most keyboards. So, not terribly
Tested on 3A+ under armhf and arm64; all working.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841955
Title:
Can't
Tested on 3, 3+, CM3, CM3+, and 4 under armhf and arm64 with eoan-
proposed image. No regressions detected.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Tested the new armhf kernel on RPi3B+; copied 40Mb and 600Mb files
successfully with no issues. Compared performance of the 40Mb copy+sync
to the same machine running Disco (which has dwc_otg) and performance on
eoan with the new kernel was marginally quicker (6.8-7.0s on eoan with
dwc2 vs
On Fri, 15 Nov 2019 at 09:30, Hui Wang wrote:
>
> I did test with VMSPLIT_2G today, the mmc/sd controller will not work
> anymore on rpi4 boards, so enable VMSPLIT_2G is not a solution so far.
Oh well, was worth a try.
> And today I also tested dwc2, it worked well, maybe we could enable dwc2
>
I have an updated patch available from the following branch for focal:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/fix-dupe-ppa
Currently building a test package in the following PPA:
Test package for devel available from PPA (we'll see about SRUing to
bionic and presumably eoan once this has landed):
https://launchpad.net/~waveform/+archive/ubuntu/flash-kernel
Relevant branch:
https://code.launchpad.net/~waveform/ubuntu/+source/flash-
The current version of linux-firmware-raspi2 supports wifi on the Pi3
(and the 3+). The forthcoming version to be released with Eoan also adds
support for wifi on the Pi4, so I think we can (belatedly) mark this as
released!
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: Triaged =>
Public bug reported:
The current Eoan image hits a kernel panic when booting on a Raspberry
Pi 3A+. Unfortunately it does so before the serial console has been
enabled so there's no useful output beyond what scrolls by rapidly on
the framebuffer console.
It is notable that the start.elf
For now, I've adjusted the boot configuration written by the base image
(and migrated by u-boot-rpi) to include the vc4-fkms-v3d overlay on all
models. While this seems to alleviate the problem, it should be
considered temporary workaround only (we should figure out why this
occurs and try and fix
@satmandu thanks for the information! I'd got as far as figuring out the
dram_init call was getting the available RAM info from the mailbox,
which only permitted a single bank to be reported, which was then
getting used in the fdt fixup called by the bootm. As it happens the fdt
/memory node was
The current versions of linux-firmware-raspi2 for bionic and eoan
(1.20190215-0ubuntu0.18.04.1 and 1.20190819-0ubuntu2 respectively)
shouldn't conflict in this manner; neither include the -sdio.bin files,
just the configuration text files and related .clm-blob files. Is anyone
still seeing this
Just had a look at linux-firmware-raspi2 for bionic, and the latest
version (1.20190215-0ubuntu0.18.04.1) no longer contains
/lib/firmware/brcm/brcmfmac43455-sdio.bin; can you confirm you're still
seeing this error with the latest version?
--
You received this bug notification because you are a
Fix released for eoan; needs backport to bionic and disco.
** Changed in: linux-firmware-raspi2 (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/1818286
Title:
The firmware currently included in bionic-updates is from 2019-02-15
(primarily to support booting the CM3+), and in eoan is 2019-08-19; both
of these support .dtbo files.
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
Related to #1847596 - commenting out the vc4-fkms-v3d overlay in
config.txt permits the 3A+ to boot, albeit with corrupted framebuffer.
In other words, solving #1847596 "properly" should also yield a fix for
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
keyboard on either. Booting the arm64 image on a
) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006905
Title:
Case inconsistency in machine field definitions
To manage notifications about this bug go to:
ht
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (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.launchp
Updated python-apt package available in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pkg
Branch from which the package was built:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/focal-entry
--
You received this bug notification
Please note for testing:
add-apt-repository does not operate without the updated package either,
so just download the relevant .debs and install manually with "sudo dpkg
-i" for testing. The package that's really needed is python-apt-common
(which contains the updated template output), but you
I'm at a similar place; currently digging into the simplefb side of
things. My current thoughts are as follows:
1. Ideally I want to ditch the vc4-fkms-v3d overlay; firstly this
resolves the 3A+ booting issue, secondly it's something that should be
an option rather than mandatory to the boot
Public bug reported:
Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
keyboard on either. Booting the arm64 image on a Raspberry Pi 3,
Additional detail from dmesg:
...
[1.390148] usbcore: registered new interface driver lan78xx
[1.391889] usbcore: registered new interface driver smsc95xx
[1.393568] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.395273] ehci-pci: EHCI PCI platform driver
[
> I mean the simplefb driver in the kernel in the #3, I didn't know
there is a simplefb driver in the uboot too.
Ah, I'm afraid my lack of kernel knowledge is showing there: I didn't
realize the was a simplefb in the kernel! I should've thought given the
kernel starts off looking fine, and only
Confirmed the 3A+ entry is missing from flash-kernel; I'll get this
added for Eoan and open an SRU for Bionic (we need to backport flash-
kernel to bionic anyway for Pi4 support).
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: fl
1 - 100 of 955 matches
Mail list logo
