Aha! After a little more investigation it appears we're just missing
libtimedate-perl as a runtime dependency (it already has libdatetime-
perl, but libtimedate-perl is required for Date/Parse.pm ... and those
two names aren't *horribly* confusing!). Anyway, that's a trivial change
so I'll patch
Confirmed the issue on jammy, patch looks good, so I'll sponsor this for
jammy. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048906
Title:
[SRU] ngspice-36 crashes in various ways
To
The patches look fine and certainly fix the issue described. One thing
that does concern me slightly is that this only patches one instance of
XMMS_PATH_MAX and there's several more scattered throughout the code
that look like they could potentially be hit by long pathnames. Wouldn't
it be
I've set focal to "invalid", but I'm not sure we can support skipping a
release for a package. I *think* I'm right in saying that upgraders have
to pass through interim releases for as long as they exist, which would
force the removal of this package upon people moving from jammy to noble
(until
** Changed in: linux-firmware-xilinx-ap1302 (Ubuntu Focal)
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/2052575
Title:
[SRU] Update firmware to support autofocus
To
This looks good, thanks -- sponsoring!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946521
Title:
[SRU] motion fails to start after install: Permission denied creating
log file
To manage
I was a little confused as to why the GPL license in d/copyright refers
specifically to "Indicator Weather" which typically isn't in the GPL3
boilerplate (and which doesn't appear related to this package). Still,
the rest of the package looks reasonable, so I'll patch d/copyright to
contain just
I'd generally agree with Sudip that fixing the version issue shouldn't
be a blocker for an SRU fix that moves the package from "completely
broken" to "at least mostly working" (querying the version is certainly
useful functionality, but it's not the core function of the package or
vital to it's
> I am confused with your comment about ipywidgets, thats noble-
proposed, and this is for Mantic.
Argh, getting confused myself between this and trying to get sagemath
migrating in noble! :)
I'll upload this in a bit, thanks!
--
You received this bug notification because you are a member of
I had another look at this and it appears the default for
MAX_TEST_FAILURES in d/tests.mk just needs bumping to match the new
amount specified in d/rules (230). I'm happy to upload this change (it
just matches what we've done in d/rules after all), but it's not going
to migrate yet due to existing
I'll bump the bluetooth firmwares in linux-firmware-
raspi as usual, and add a Conflicts on bluez-firmware to linux-firmware-
raspi to ensure people can't try and install them simultaneously.
** Changed in: linux-firmware-raspi (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: l
> I really appreciated the detailed bug description. However, some
> elements were missing on the MIR template rules and checks, like the
> output of lintian pedantic running as per
> https://github.com/canonical/ubuntu-mir. Also, some information are
> not exact, you state: "* The package
> On 15-03-2024 3:49 p.m., Dave Jones wrote:
> > autopkgtest is "clever" about when it resets the testbed betweens
> > tests, and this is a Bad Thing (tm) when it breaks assumptions
> > about isolation.
>
> Ironically https://bugs.debian.org/1063533 has
Public bug reported:
autopkgtest is "clever" about when it resets the testbed betweens tests,
and this is a Bad Thing (tm) when it breaks assumptions about isolation.
Specifically, in lib/adt_testbed.py under Testbed.reset is found the
following code:
def reset(self, deps_new,
Thanks for the review Ioanna! I'd just updated the form based on
Didier's feedback on LP: #2054480 (I'd been cribbing from an old MIR
rather than using the new template), but I don't think the additions I
made change much that you've pointed out.
The more info URL breakage is ... weird, given
** Description changed:
[ Availability ]
The package is already available in universe.
[ Rationale ]
The intent is to seed the package in the Ubuntu Server & Desktop for
Raspberry Pi images. The purpose of the package is to warn about sub-
standard or deficient power supplies
lintian --pedantic output:
Running lintian...
I: Lintian run was successful.
** Changed in: pemmican (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and apt can no longer find firewalld.
The problem is caused by a file, systemctl.desktop, located at:
/home/dave/.config/autostart/
The file content while causing the problem was:
[Desktop Entry]
Type=Application
Exec=systemctl start firewalld.service
Hidden=false
NoDisplay=false
X-GNOME
Public bug reported:
The current upstream Pi boot firmware has several fixes which should be
incorporated for noble. Specifically, HAT+ support (necessary for the
forthcoming PoE and NVMe boards), support for [pi5] sections in the
config.txt (for earlier boards), and CM5 info strings.
**
: Dave Jones (waveform)
Status: In Progress
** Changed in: pemmican (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: pemmican (Ubuntu)
Milestone: None => ubuntu-24.04
** Changed in: pemmican (Ubuntu)
Importance: Undecided => High
** Changed in:
** Changed in: ubuntu
Status: Fix Committed => 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/2054344
Title:
[needs-packaging] pemmican
To manage notifications about this bug go
This issue affected me as well on Ubuntu 22.04.4, running on a AMD Ryzen
9 7950X3D integrated graphics CPU. Took a late Feb update and it broke.
I tried the various snap yaml modifications + snap try with no success.
Workaround seems to be to run Firefox does work outside of snap:
This looks like it's the same issue as this:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2004532
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055351
Title:
[amdgpu] Firefox and
** Description changed:
URL: https://github.com/waveform80/nobodd
License: GPL-3
Notes:
The nobodd suite provides a TFTP server and associated tooling intended
for netbooting Raspberry Pis. It integrates (fairly loosely) with nbd-
server to provide a block-device based netboot
Public bug reported:
URL: https://github.com/waveform80/nobodd
License: GPL-3
Notes:
The nobodd suite provides a TFTP server and associated tooling intended
for netbooting Raspberry Pis. It integrates (fairly loosely) with nbd-
server to provide a block-device based netboot system as opposed to
I suspect the FFe's going to a little bit more detail, specifically
(from https://wiki.ubuntu.com/FreezeExceptionProcess):
* the diff of the upstream changelog as changelog.diff -- I'm not sure
that's actually necessary here since it's basically the content of your
header e-mail which is
** Merge proposal linked:
https://code.launchpad.net/~xypron/ubuntu/+source/u-boot/+git/u-boot/+merge/461725
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055939
Title:
FFE: enable riscv64
Ran the package through licensecheck and I think there's a missing
BSD-3-Clause entry required in d/copyright. Specifically,
Files:
tee-supplicant/src/hmac_sha2.c
tee-supplicant/src/hmac_sha2.h
tee-supplicant/src/sha2.c
tee-supplicant/src/sha2.h
Copyright:
2005, 2007, Olivier Gay
2005,
Good to see an autopkgtest included, unfortunately it's testing the keys
in the source package when it really needs to be testing those installed
as part of the binary package. This also requires that the verify test
depends on "@" (if Depends is specified, it doesn't implicitly include
the binary
Thank you Sudip -- patch looks perfect, same for test plan in the SRU
template; sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971094
Title:
[SRU] openshot doesn't start Ubuntu 22.04
The debdiffs are unfortunately rather pointless given they just list
"Binary files blah and blah differ", i.e. they can't be used to build
the package for sponsoring. I see there's a jammy build in the test PPA,
but this will need fixing in noble before backporting anywhere else. I
would suggest
** Description changed:
[ Availability ]
The package is already available in universe.
[ Rationale ]
The intent is to seed the package in the Ubuntu Server & Desktop for
Raspberry Pi images. The purpose of the package is to warn about sub-
standard or deficient power supplies
Tweaked the SRU regression section a bit, otherwise looks good;
sponsoring for jammy
** Description changed:
[Impact]
Since the model names in the DTBs have been updated in AMD-Xilinx
kernel, we need to update the machine entries in flash-kernel as well.
-
- As part of this update, we
Public bug reported:
[ Availability ]
The package is already available in universe.
[ Rationale ]
The intent is to seed the package in the Ubuntu Server & Desktop for
Raspberry Pi images. The purpose of the package is to warn about sub-
standard or deficient power supplies on the Raspberry Pi
** Also affects: flash-kernel (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: flash-kernel (Ubuntu)
Status: In Progress => Fix Released
** Changed in: flash-kernel (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because
Looks good to me; sponsoring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053028
Title:
Add Milk-V Mars board to db/all.db
To manage notifications about this bug go to:
In KDE (and for a long time now), you can choose a different desktop
background for each screen.
Anyway, are all your screens exactly the same resolution?
With all best wishes,
Dave
On Sat, Aug 20, 2022 at 5:06 PM Joseph Ronne wrote:
> The problem may be the type of monitors in relat
On Tue, May 10, 2022 at 11:30:34AM -0700, Brian Murray wrote:
[snip]
I don't think byobu is widely installed by default and subsequently
having it moved to universe would not make much difference i.e. users
would still need to install it.
It's widely installed because it's seeded on the
On Tue, Jun 14, 2022 at 06:23:46PM +0200, Julian Andres Klode wrote:
On Tue, Jun 14, 2022 at 03:47:58PM +0100, Dave Jones wrote:
On Fri, Jun 10, 2022 at 08:16:15PM +0200, Sebastien Bacher wrote:
> Le 09/06/2022 à 21:19, Dan Streetman a écrit :
> > Personally, I think this is the corre
to reduce the number of oomd kills noticeably on the more memory
constrained Pis (though just anecdotally; I haven't sat down and
recorded/analyzed this yet).
Dave.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailma
gnome-control-center-printer-renderer produces no output on the raspi.
The debug output from gnome-control-center is:
(gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.015:
_g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
Sure -- I'll try not to drown them in verbiage :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
To manage notifications about this bug
> It could be maybe added to NetworkManager, if somebody sends a
> patch. But it's not actually clear to me that this is really
> NetworkManager's task. Maybe it is, but what are the arguments for
> that?
I could be glib, and say "because the kernel says so [1]". However, I
suspect that's not a
>> it's apparently never worked for me at home or at various friends
>> houses, and only once worked when I travelled to Germany for a
>> sprint.
> is that having a visible impact for users? like was your computer
> not able to connect to some access point?
Personally, I've never encountered
I'll take a shot at responding to @seb128's questions:
Why is this a rls issue in the LTS?
===
Prior to jammy, the crda database was in userland, and the crda package
provided a means (via editing /etc/default/crda) to persist the wireless
region across reboots.
Reported issue with flatpak (under arm64) upstream:
https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1468424 (after
re-testing just to confirm that the issue still occurred).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed up the instructions (forgot to mention that *both* libraspberrypi0
and libraspberrypi0:armhf need installing from -proposed to verify
this!). Verification done on Ubuntu Desktop for Pi and Ubuntu Server
(arm64) for Pi, on a Pi 400, and a Pi 4B. No issues encountered.
** Description changed:
Can you let me know which image you were trying to boot? The regular
ubuntu desktop image is arm64 only which wouldn't boot on a rev1.1 Pi 2B
board, so I'm guessing this *might* be Ubuntu MATE?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I found a way to run psfc.Install windows version with wine.Works
perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967793
Title:
pysolfc no longer works in 22.04 due to python changes
To
I'm attaching the full outputs as a tarball (just in case they're
useful) but here's the pertinent bits too:
$ tail -n 13 /proc/cpuinfo
processor : 3
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU
Added some commentary for each additional commit to the regression
section, with a link to the relevant commits in the upstream repo that
we build from.
** Description changed:
[Impact]
Despite libraspberrypi0 being declared Multi-Arch: same, users cannot
install libraspberrypi0:armhf
> * abs-path-revert.patch: Is there a bug report for it? If no, please
file one. If yes, please reference it.
abs-path-revert.patch first appears in 2016 in version 0.67.0-2ubuntu2
Public bug reported:
We're currently carrying a delta in our sbuild which reverts a commit in
the upstream [1] which purports to fix a bug [2]. There's no bug
associated with this delta, which allegedly fixes a build failure in lp-
buildd. The delta in question is documented under d/p/abs-path-
** Description changed:
[Impact]
Despite libraspberrypi0 being declared Multi-Arch: same, users cannot
install libraspberrypi0:armhf on arm64 systems. This affects the ability
to (attempt to) use libwidevine (the library required to play certain
proprietary streaming services, e.g.
** Description changed:
[Impact]
Despite libraspberrypi0 being declared Multi-Arch: same, users cannot
install libraspberrypi0:armhf on arm64 systems. This affects the ability
to (attempt to) use libwidevine (the library required to play certain
proprietary streaming services, e.g.
** Changed in: raspberrypi-userland (Ubuntu Jammy)
Status: Confirmed => 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/1973285
Title:
[SRU] libraspberrypi0 multi-arch install
** Description changed:
+ [Impact]
+
+ Despite libraspberrypi0 being declared Multi-Arch: same, users cannot
+ install libraspberrypi0:armhf on arm64 systems. This affects the ability
+ to (attempt to) use libwidevine (the library required to play certain
+ proprietary streaming services, e.g.
** Summary changed:
- libraspberrypi0 multi-arch install failing due to lintian override content
difference
+ [SRU] libraspberrypi0 multi-arch install failing due to lintian override
content difference
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: raspberrypi-userland (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: raspberrypi-userland (Ubuntu Kinetic)
Importance: Medium
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: raspberrypi-userland (Ubuntu Jammy
** Changed in: raspberrypi-userland (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: raspberrypi-userland (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also affects my Acer Aspire TravelMate Spin B118 on Ubuntu 22.04. The
i2c-i801 workaround from comment 14 above
(https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.11/+bug/1931001/comments/14) works nicely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Merge proposal linked:
https://code.launchpad.net/~jawn-smith/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/421557
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: fr-2407
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974177
Title:
Please merge sbuild 0.83.1 from Debian unstable
To manage notifications about this bug go to:
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Confirmed
** Changed in: linux-firmware-raspi2 (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sbuild (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/1974177
Title:
Please merge sbuild 0.83.1 from Debian unstable
To manage notifications
Right, let's try this again...
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/sbuild/+git/sbuild
Specifically:
* logical/0.81.2ubuntu6 represents our
Oh damn it, the autopkgtests are going to fail (wasn't testing on the
right arch and hadn't noticed it skipping; just re-tested on amd64 and
of course diffoscope's going to trip up on the stuff that it *thought*
was previously testing and now is *actually* testing...).
Will fix in the morning,
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/sbuild/+git/sbuild
Specifically:
* logical/0.81.2ubuntu6 represents our split-out delta on top of old/debian
@Samuel that fix is for PCs which is a different bug (LP: #1971463);
this bug is about totem on the Pi desktop images (or, I'm beginning to
suspect, arm64 more generally).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please merge sbuild 0.83.1 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/flash-
kernel/+git/flash-kernel
Specifically:
* logical/3.104ubuntu9 represents our split-out delta on top
Public bug reported:
Please merge flash-kernel 3.106 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
> This is how I have it in Raspbian as per the case that I am using for
> RPI4. Regardless - I moved it under [cm4] and now dwc2 doesn't show up
> at all, so I have moved it back to [all]
Ahhh! This is indeed expected. On the CM4, dwc2 is used for the type A
ports on the IO board (and presumably
No, it seems a 4B is happy with dtoverlay=dwc2,dr_mode=host loaded. I
had a suspicion this might be the case as it should only affect the mode
of the dwc2 port, which is the USB-C power socket on the 4B, and I
assume the USB ports you're having trouble with are the type A USB2 and
USB3 ports --
That's a slightly odd config.txt; why is "dtoverlay=dwc2,dr_mode=host"
under [all] instead of [cm4] where it usually sits? I'm not sure this
would disable the USB ports on a 4B (will test this), but it shouldn't
be there normally.
--
You received this bug notification because you are a member of
Sorry, I'd mis-interpreted this bug! I'd gone digging through the
history of debconf and couldn't understand how dpkg-reconfigure was only
restarting things just *now*, but hadn't correctly understood that your
bug was complaining the service was stopped, but *not started* again.
So, my apologies:
Hi Athos -- this is an interesting one.
Forgive my ignorance, but per Colin's comments in
https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/10 "...
dpkg-reconfigure is simulating the process of reinstalling a package
without actually unpacking its files again" (which aligned with my
Public bug reported:
Errors were encountered while processing:
linux-image-5.13.0-40-generic
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
Could not install 'linux-image-5.13.0-40-generic'
The upgrade will continue but the
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589624/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589623/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589622/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589621/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589620/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589619/+files/ProcInterrupts.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/1973357/+attachment/5589618/+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/1973357
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589617/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589616/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589615/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589614/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589613/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1973357/+attachment/5589612/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973357
Title:
apport information
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: apport-collected tessa
** Description changed:
After update and reboot, severe delay occurs to log in due to network
not available. After about 2-3 minutes login worked. No network, no
Public bug reported:
After update and reboot, severe delay occurs to log in due to network
not available. After about 2-3 minutes login worked. No network, no
sound and maybe other items. Upon further troubleshooting, the network
module is not being loaded. Loading it enabled network. Details
An additional data point; I noted in the linked gitlab bug a couple of
messages noting that "it works with the flatpak". Out of curiosity (as
to whether this might be a well and truly arm64 specific problem), I
tried the flatpak on the pi desktop and: it's got exactly the same
problem (same
Unfortunately we've tried "G_DEBUG=fatal_warnings" before (you suggested
it back in comment:4) but I did manage to figure out a couple of things
since last time:
The crash I originally observed (back in comment:6) only occurs on the
very first run of totem. All subsequent runs (even after a
where they won't work.
Will attach a patch shortly (and see if there's anything to merge from
RaspiOS while I'm at it).
** Affects: raspi-config (Ubuntu)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Affects: raspi-config (Ubuntu Jammy)
Importance
Recently updated kernel to 5.13.0-41-generic and the problem remains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969897
Title:
Battery report false in kernel 5.13.0-40-generic
To manage
> Should be part of the 'beacon' info.
https://howiwifi.com/2020/07/13/802-11-frame-types-and-formats/ has a
good overview. I discovered this exchange while observing 'on the wire'
with wireshark.
Thanks for the link; lots of useful stuff there!
> > I wondered if perhaps it this only works on
I'm not entirely convinced NetworkManager is working correctly this
regard? I *was* checking the wifi regulatory domain with "iw reg get"
which consistently shows UNSET both globally and for phy#0 under the
desktop for Pi images:
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @
Closing as won't fix (for focal) for the reasons enumerated in
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/comments/10
(tl;dr: we'll include pi-bluetooth in desktop images, not in server
images).
** Changed in: livecd-rootfs (Ubuntu Focal)
Status: Confirmed => Won't Fix
201 - 300 of 23321 matches
Mail list logo
