** Summary changed:
- ubuntu_qrt_apparmor:test-apparmor.py:test-aa-notify.py:
test_entries_since_login(_verbose)
+ test-aa-notify.py in test_utils_testsuite(3) from ubuntu_qrt_apparmor failed
with AppArmor denials string unmatch
** Tags added: 6.5 mantic oracle sru-20240108
--
You received
The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black
With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing
a modeset for some reason.
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.
Here's various artifacts if you want
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.
Moving that to zero certainly helps. It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a
videos to compare with Ubuntu and Fedora with this exact
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.
--
You
I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).
"Really long time" might be subjective though? How long?
VT switches (or more accurately virtual console
I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through. There's a really long
time of a black screen. Not sure if this is because it was an upstream
kernel and
Should be fixed by
https://code.launchpad.net/~georgiag/qa-regression-testing/+git/qa-regression-testing/+merge/459835
Thanks!
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
** Also affects: autopkgtest (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: autopkgtest (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: autopkgtest (Ubuntu Jammy)
Status: New => Triaged
** Changed in: autopkgtest (Ubuntu Mantic)
After testing the latest Noble daily build of Xubuntu (Version
20240201), I did not experience this error. Has this been fixed?
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048914
Title
This crash did not occur when testing the daily Noble ISO in build
version 20240201.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016009
Title:
Installer crashes when quitting in Live
Hello!
Thanks for reporting! I fixed this issue upstream, commit
https://gitlab.com/apparmor/apparmor/-/commit/dc73f0fc0b81a70e71899592f9969026f450420c
I'll add it to the QA Regression Tests.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:another-github-jobs-fix into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
** Description changed:
[Impact]
This release contains both bug fixes and new features and we would like
to make sure all of our developers have access to these improvements.
It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with
lots of improvements, but here
Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.
If I haven't changed my mind again on Friday then it will be sent
upstream.
** Patch added: "lp1970069-patchset-20240201a.patch"
Public bug reported:
[Impact]
This release contains both bug fixes and new features and we would like
to make sure all of our developers have access to these improvements.
It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with
lots of improvements, but here are the most
One interesting finding is that if you run the test directly, it will
just print "PASS"
$ sudo
/tmp/testlib_4jpn6z_/source/mantic/apparmor-4.0.0~alpha2/tests/regression/apparmor/unix_fd_server
/tmp/sdtest.346048-11072-CHR92J/file
Public bug reported:
Issue found on Mantic since 6.5.0-11.11
Test failed with:
running attach_disconnected
Fatal Error (unix_fd_server): Unable to run test sub-executable
By hacking the tests/regression/apparmor/prologue.inc:
diff --git a/prologue.inc.orig b/prologue.inc
index
Public bug reported:
Issue found on M-starfive 6.5.0-1005.6 and 6.5.0-1007.8
Test log:
Running 'make run_tests -C efivarfs TEST_PROGS=efivarfs.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1879330
** Tags added: iso-testing
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA,
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2024317
** Tags added: iso-testing
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA,
21 matches
Mail list logo
